Error 18483 'distributor_admin'

I'm trying to publish a database and when I get to the end of the wizard, I
am greeted by this message:
SQL Server Enterprise Manager could not configure 'SERVERNAME' as the
Distributor for 'SERVERNAME'.
Error 18483: Could not connect to server 'SERVERNAME' because
'distributor_admin' is not defined as a remote login at the server.
The MS articles did not help me. Can someone, please?
Wack
This message will self destruct.
try to drop the server and then recreate it
sp_dropserver @.@.servername
GO
sp_addserver @.@.servername, 'local'
GO
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Ray Lewis" <dav5489@.hotmail.com> wrote in message
news:uO9gjUYJFHA.4060@.TK2MSFTNGP14.phx.gbl...
> I'm trying to publish a database and when I get to the end of the wizard,
I
> am greeted by this message:
> SQL Server Enterprise Manager could not configure 'SERVERNAME' as the
> Distributor for 'SERVERNAME'.
> Error 18483: Could not connect to server 'SERVERNAME' because
> 'distributor_admin' is not defined as a remote login at the server.
> The MS articles did not help me. Can someone, please?
> --
> Wack
> --
> This message will self destruct.
>
|||I tried this, and used MS article 818334. I found that the SQL Server Name
was not the same as the Computer Name. However, when I try and drop the SQL
server name, I get a message stating that the SQL server does not exist.
So, I cannot rename my SQL Server 2000 server. What now?
Wack
This message will self destruct.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uZUqNwaJFHA.1392@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> try to drop the server and then recreate it
> sp_dropserver @.@.servername
> GO
> sp_addserver @.@.servername, 'local'
> GO
>
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Ray Lewis" <dav5489@.hotmail.com> wrote in message
> news:uO9gjUYJFHA.4060@.TK2MSFTNGP14.phx.gbl...
wizard,
> I
>
|||Hi,
is the login used to configure the publication a member of the 'system administrators'? I had a similar problem when creating a pull subscription and this solved it!
Bruno

Quote:

Originally posted by Ray Lewis
I'm trying to publish a database and when I get to the end of the wizard, I
am greeted by this message:
SQL Server Enterprise Manager could not configure 'SERVERNAME' as the
Distributor for 'SERVERNAME'.
Error 18483: Could not connect to server 'SERVERNAME' because
'distributor_admin' is not defined as a remote login at the server.
The MS articles did not help me. Can someone, please?
Wack
This message will self destruct.

sql

Error 17883 in SQL error log

Hello,
We have a SQL server 2000 enterprise edition on SP4 on windows NT, and got
the following error recently:
Sleeping until external dump process completes.
Resuming after waiting on external debug process for 12 seconds.
Stack Signature for the dump is 0x00000000
Error: 17883, Severity: 1, State: 0
Process 1:0 (9d4) UMS Context 0x002977F8 appears to be non-yielding on
Scheduler 0.
We also get error like below daily:
SQL Server has encountered 5359 occurrence(s) of IO requests taking longer
than 15 seconds to complete on file [E:\Microsoft SQL
Server\Data\DBAUtility.mdf] in database [DBAUtility] (14). The OS file
handle is 0x0000053C. The offset of the latest long IO is: 0x00000000010000
The SQL server is used as data warhouse server, so there are a lots of IO.
I appreciate any suggestions or comments.
Thanks!
Sugarhigh,
For 17883 here is a whitepaper
http://www.microsoft.com/technet/prodtechnol/sql/2005/diagandcorrecterrs.mspx#ELDAC
For your IO issues:
http://support.microsoft.com/kb/897284
http://blogs.msdn.com/sqlserverstorageengine/archive/2006/06/21/642314.aspx
Basically, you need to investigate your hardware utilization, particularly
(as you might expect) measuring your IO subsystem which sounds like it is
strained. Most likely you will need to do some upgrades to your equipment.
RLF
"Sugarhigh" <sugarhigh@.community.nospam> wrote in message
news:EBD8AFCC-B391-4E6C-A341-0BD5A4D62903@.microsoft.com...
> Hello,
> We have a SQL server 2000 enterprise edition on SP4 on windows NT, and got
> the following error recently:
> Sleeping until external dump process completes.
> Resuming after waiting on external debug process for 12 seconds.
> Stack Signature for the dump is 0x00000000
> Error: 17883, Severity: 1, State: 0
> Process 1:0 (9d4) UMS Context 0x002977F8 appears to be non-yielding on
> Scheduler 0.
> We also get error like below daily:
> SQL Server has encountered 5359 occurrence(s) of IO requests taking longer
> than 15 seconds to complete on file [E:\Microsoft SQL
> Server\Data\DBAUtility.mdf] in database [DBAUtility] (14). The OS file
> handle is 0x0000053C. The offset of the latest long IO is:
> 0x00000000010000
> The SQL server is used as data warhouse server, so there are a lots of IO.
> I appreciate any suggestions or comments.
> Thanks!
|||Hello,
Thank you for posting here.
To better understand the error message, you must first understand how SQL
Server uses a User Mode Scheduling (UMS) Ums.dll helper file.
Microsoft SQL Server 2000 use logical schedulers. These schedulers help to
make sure that SQL Server maximizes operating system resource usage in
relation to key database action paths. The UMS layer makes sure that SQL
Server correctly uses Win32 events to strictly control thread and fiber (or
both) scheduling visibility to the operating system. By strictly
controlling the threads or fibers that can run, SQL Server can maximize CPU
usage as it relates to database primitives such as locking.
For example, logical scheduling permits lock waiters to sleep
(WaitForSingleObject on a Win32 event) until the lock owner releases the
lock and signals (SetEvent) them to wake up.
For more information, please refer to the following article:
New concurrency and scheduling diagnostics added to SQL Server (319892)
http://support.microsoft.com/default.aspx?scid=KB;EN-US;319892
Note: The format of the 17833 message is different for separate versions of
the SQL Server product; however, the meaning is the same.
However, to find out the root cause of this issue we may need to analyze
memory dumps, this work has to be done by contacting Microsoft Product
Support Services. Therefore, we probably will not be able to resolve the
issue through the newsgroups. If the issue is urgent, I recommend that you
open a Support incident with Microsoft Product Support Services so that a
dedicated Support Professional can assist with this case. If you need any
help in this regard, please let me know.
For a complete list of Microsoft Product Support Services phone numbers,
please go to the following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp
At the same time, please also ensure that latest update for SQL Server 2000
Service Pack 4 has been installed. We can download it from the following
website:
Cumulative Hotfix for SQL Server 2000 Service Pack 4 - Build 2187 for x86
and x64 Based Systems
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=9c9a
b140-bdee-44df-b7a3-e6849297754a
More related information:
=======================
892840FIX: 17883 errors may be written to the SQL Server error log when
you run a query that generates many floating point exception errors in SQL
Server 2000
http://support.microsoft.com/default.aspx?scid=kb;EN-US;892840
810885High-end disk subsystems may experience error 17883
http://support.microsoft.com/default.aspx?scid=kb;EN-US;810885
888666You may receive a 17883 error message when you run full-text queries
in SQL Server 7.0 or SQL Server 2000
http://support.microsoft.com/default.aspx?scid=kb;EN-US;888666
890730FIX: You receive a 17883 error message when you perform large
in-memory sort operations in SQL Server 2000
http://support.microsoft.com/default.aspx?scid=kb;EN-US;890730
Have a nice day!
Best regards,
Adams Qu, MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
| Thread-Topic: Error 17883 in SQL error log
| thread-index: AcfVM7K5Tj5qumliSs2GiuzWV3+hMQ==
| X-WBNR-Posting-Host: 207.46.19.168
| From: =?Utf-8?B?U3VnYXJoaWdo?= <sugarhigh@.community.nospam>
| Subject: Error 17883 in SQL error log
| Date: Thu, 2 Aug 2007 11:34:02 -0700
| Lines: 23
| Message-ID: <EBD8AFCC-B391-4E6C-A341-0BD5A4D62903@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
| Newsgroups: microsoft.public.sqlserver.server
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:21828
| NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| Hello,
|
| We have a SQL server 2000 enterprise edition on SP4 on windows NT, and
got
| the following error recently:
|
| Sleeping until external dump process completes.
| Resuming after waiting on external debug process for 12 seconds.
| Stack Signature for the dump is 0x00000000
| Error: 17883, Severity: 1, State: 0
| Process 1:0 (9d4) UMS Context 0x002977F8 appears to be non-yielding on
| Scheduler 0.
|
| We also get error like below daily:
| SQL Server has encountered 5359 occurrence(s) of IO requests taking
longer
| than 15 seconds to complete on file [E:\Microsoft SQL
| Server\Data\DBAUtility.mdf] in database [DBAUtility] (14). The OS file
| handle is 0x0000053C. The offset of the latest long IO is:
0x00000000010000
|
| The SQL server is used as data warhouse server, so there are a lots of
IO.
|
| I appreciate any suggestions or comments.
|
| Thanks!
|

Error 17883 in SQL error log

Hello,
We have a SQL server 2000 enterprise edition on SP4 on windows NT, and got
the following error recently:
Sleeping until external dump process completes.
Resuming after waiting on external debug process for 12 seconds.
Stack Signature for the dump is 0x00000000
Error: 17883, Severity: 1, State: 0
Process 1:0 (9d4) UMS Context 0x002977F8 appears to be non-yielding on
Scheduler 0.
We also get error like below daily:
SQL Server has encountered 5359 occurrence(s) of IO requests taking longer
than 15 seconds to complete on file [E:\Microsoft SQL
Server\Data\DBAUtility.mdf] in database [DBAUtility] (14). The OS file
handle is 0x0000053C. The offset of the latest long IO is: 0x00000000010000
The SQL server is used as data warhouse server, so there are a lots of IO.
I appreciate any suggestions or comments.
Thanks!Sugarhigh,
For 17883 here is a whitepaper
http://www.microsoft.com/technet/prodtechnol/sql/2005/diagandcorrecterrs.mspx#ELDAC
For your IO issues:
http://support.microsoft.com/kb/897284
http://blogs.msdn.com/sqlserverstorageengine/archive/2006/06/21/642314.aspx
Basically, you need to investigate your hardware utilization, particularly
(as you might expect) measuring your IO subsystem which sounds like it is
strained. Most likely you will need to do some upgrades to your equipment.
RLF
"Sugarhigh" <sugarhigh@.community.nospam> wrote in message
news:EBD8AFCC-B391-4E6C-A341-0BD5A4D62903@.microsoft.com...
> Hello,
> We have a SQL server 2000 enterprise edition on SP4 on windows NT, and got
> the following error recently:
> Sleeping until external dump process completes.
> Resuming after waiting on external debug process for 12 seconds.
> Stack Signature for the dump is 0x00000000
> Error: 17883, Severity: 1, State: 0
> Process 1:0 (9d4) UMS Context 0x002977F8 appears to be non-yielding on
> Scheduler 0.
> We also get error like below daily:
> SQL Server has encountered 5359 occurrence(s) of IO requests taking longer
> than 15 seconds to complete on file [E:\Microsoft SQL
> Server\Data\DBAUtility.mdf] in database [DBAUtility] (14). The OS file
> handle is 0x0000053C. The offset of the latest long IO is:
> 0x00000000010000
> The SQL server is used as data warhouse server, so there are a lots of IO.
> I appreciate any suggestions or comments.
> Thanks!|||Hello,
Thank you for posting here.
To better understand the error message, you must first understand how SQL
Server uses a User Mode Scheduling (UMS) Ums.dll helper file.
Microsoft SQL Server 2000 use logical schedulers. These schedulers help to
make sure that SQL Server maximizes operating system resource usage in
relation to key database action paths. The UMS layer makes sure that SQL
Server correctly uses Win32 events to strictly control thread and fiber (or
both) scheduling visibility to the operating system. By strictly
controlling the threads or fibers that can run, SQL Server can maximize CPU
usage as it relates to database primitives such as locking.
For example, logical scheduling permits lock waiters to sleep
(WaitForSingleObject on a Win32 event) until the lock owner releases the
lock and signals (SetEvent) them to wake up.
For more information, please refer to the following article:
New concurrency and scheduling diagnostics added to SQL Server (319892)
http://support.microsoft.com/default.aspx?scid=KB;EN-US;319892
Note: The format of the 17833 message is different for separate versions of
the SQL Server product; however, the meaning is the same.
However, to find out the root cause of this issue we may need to analyze
memory dumps, this work has to be done by contacting Microsoft Product
Support Services. Therefore, we probably will not be able to resolve the
issue through the newsgroups. If the issue is urgent, I recommend that you
open a Support incident with Microsoft Product Support Services so that a
dedicated Support Professional can assist with this case. If you need any
help in this regard, please let me know.
For a complete list of Microsoft Product Support Services phone numbers,
please go to the following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp
At the same time, please also ensure that latest update for SQL Server 2000
Service Pack 4 has been installed. We can download it from the following
website:
Cumulative Hotfix for SQL Server 2000 Service Pack 4 - Build 2187 for x86
and x64 Based Systems
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=9c9a
b140-bdee-44df-b7a3-e6849297754a
More related information:
=======================892840 FIX: 17883 errors may be written to the SQL Server error log when
you run a query that generates many floating point exception errors in SQL
Server 2000
http://support.microsoft.com/default.aspx?scid=kb;EN-US;892840
810885 High-end disk subsystems may experience error 17883
http://support.microsoft.com/default.aspx?scid=kb;EN-US;810885
888666 You may receive a 17883 error message when you run full-text queries
in SQL Server 7.0 or SQL Server 2000
http://support.microsoft.com/default.aspx?scid=kb;EN-US;888666
890730 FIX: You receive a 17883 error message when you perform large
in-memory sort operations in SQL Server 2000
http://support.microsoft.com/default.aspx?scid=kb;EN-US;890730
Have a nice day!
Best regards,
Adams Qu, MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
--
| Thread-Topic: Error 17883 in SQL error log
| thread-index: AcfVM7K5Tj5qumliSs2GiuzWV3+hMQ==| X-WBNR-Posting-Host: 207.46.19.168
| From: =?Utf-8?B?U3VnYXJoaWdo?= <sugarhigh@.community.nospam>
| Subject: Error 17883 in SQL error log
| Date: Thu, 2 Aug 2007 11:34:02 -0700
| Lines: 23
| Message-ID: <EBD8AFCC-B391-4E6C-A341-0BD5A4D62903@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
| Newsgroups: microsoft.public.sqlserver.server
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:21828
| NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| Hello,
|
| We have a SQL server 2000 enterprise edition on SP4 on windows NT, and
got
| the following error recently:
|
| Sleeping until external dump process completes.
| Resuming after waiting on external debug process for 12 seconds.
| Stack Signature for the dump is 0x00000000
| Error: 17883, Severity: 1, State: 0
| Process 1:0 (9d4) UMS Context 0x002977F8 appears to be non-yielding on
| Scheduler 0.
|
| We also get error like below daily:
| SQL Server has encountered 5359 occurrence(s) of IO requests taking
longer
| than 15 seconds to complete on file [E:\Microsoft SQL
| Server\Data\DBAUtility.mdf] in database [DBAUtility] (14). The OS file
| handle is 0x0000053C. The offset of the latest long IO is:
0x00000000010000
|
| The SQL server is used as data warhouse server, so there are a lots of
IO.
|
| I appreciate any suggestions or comments.
|
| Thanks!
|

Error 17883 in SQL error log

Hello,
We have a SQL server 2000 enterprise edition on SP4 on windows NT, and got
the following error recently:
Sleeping until external dump process completes.
Resuming after waiting on external debug process for 12 seconds.
Stack Signature for the dump is 0x00000000
Error: 17883, Severity: 1, State: 0
Process 1:0 (9d4) UMS Context 0x002977F8 appears to be non-yielding on
Scheduler 0.
We also get error like below daily:
SQL Server has encountered 5359 occurrence(s) of IO requests taking longer
than 15 seconds to complete on file [E:\Microsoft SQL
Server\Data\DBAUtility.mdf] in database [DBAUtility] (14). The OS file
handle is 0x0000053C. The offset of the latest long IO is: 0x00000000010000
The SQL server is used as data warhouse server, so there are a lots of IO.
I appreciate any suggestions or comments.
Thanks!Sugarhigh,
For 17883 here is a whitepaper
C" target="_blank">http://www.microsoft.com/technet/pr...x#ELDA
C
For your IO issues:
http://support.microsoft.com/kb/897284
http://blogs.msdn.com/sqlserverstor.../21/642314.aspx
Basically, you need to investigate your hardware utilization, particularly
(as you might expect) measuring your IO subsystem which sounds like it is
strained. Most likely you will need to do some upgrades to your equipment.
RLF
"Sugarhigh" <sugarhigh@.community.nospam> wrote in message
news:EBD8AFCC-B391-4E6C-A341-0BD5A4D62903@.microsoft.com...
> Hello,
> We have a SQL server 2000 enterprise edition on SP4 on windows NT, and got
> the following error recently:
> Sleeping until external dump process completes.
> Resuming after waiting on external debug process for 12 seconds.
> Stack Signature for the dump is 0x00000000
> Error: 17883, Severity: 1, State: 0
> Process 1:0 (9d4) UMS Context 0x002977F8 appears to be non-yielding on
> Scheduler 0.
> We also get error like below daily:
> SQL Server has encountered 5359 occurrence(s) of IO requests taking longer
> than 15 seconds to complete on file [E:\Microsoft SQL
> Server\Data\DBAUtility.mdf] in database [DBAUtility] (14). The OS fil
e
> handle is 0x0000053C. The offset of the latest long IO is:
> 0x00000000010000
> The SQL server is used as data warhouse server, so there are a lots of IO.
> I appreciate any suggestions or comments.
> Thanks!|||Hello,
Thank you for posting here.
To better understand the error message, you must first understand how SQL
Server uses a User Mode Scheduling (UMS) Ums.dll helper file.
Microsoft SQL Server 2000 use logical schedulers. These schedulers help to
make sure that SQL Server maximizes operating system resource usage in
relation to key database action paths. The UMS layer makes sure that SQL
Server correctly uses Win32 events to strictly control thread and fiber (or
both) scheduling visibility to the operating system. By strictly
controlling the threads or fibers that can run, SQL Server can maximize CPU
usage as it relates to database primitives such as locking.
For example, logical scheduling permits lock waiters to sleep
(WaitForSingleObject on a Win32 event) until the lock owner releases the
lock and signals (SetEvent) them to wake up.
For more information, please refer to the following article:
New concurrency and scheduling diagnostics added to SQL Server (319892)
http://support.microsoft.com/defaul...KB;EN-US;319892
Note: The format of the 17833 message is different for separate versions of
the SQL Server product; however, the meaning is the same.
However, to find out the root cause of this issue we may need to analyze
memory dumps, this work has to be done by contacting Microsoft Product
Support Services. Therefore, we probably will not be able to resolve the
issue through the newsgroups. If the issue is urgent, I recommend that you
open a Support incident with Microsoft Product Support Services so that a
dedicated Support Professional can assist with this case. If you need any
help in this regard, please let me know.
For a complete list of Microsoft Product Support Services phone numbers,
please go to the following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp
At the same time, please also ensure that latest update for SQL Server 2000
Service Pack 4 has been installed. We can download it from the following
website:
Cumulative Hotfix for SQL Server 2000 Service Pack 4 - Build 2187 for x86
and x64 Based Systems
http://www.microsoft.com/downloads/...n&FamilyID=9c9a
b140-bdee-44df-b7a3-e6849297754a
More related information:
=======================
892840 FIX: 17883 errors may be written to the SQL Server error log when
you run a query that generates many floating point exception errors in SQL
Server 2000
http://support.microsoft.com/defaul...kb;EN-US;892840
810885 High-end disk subsystems may experience error 17883
http://support.microsoft.com/defaul...kb;EN-US;810885
888666 You may receive a 17883 error message when you run full-text queries
in SQL Server 7.0 or SQL Server 2000
http://support.microsoft.com/defaul...kb;EN-US;888666
890730 FIX: You receive a 17883 error message when you perform large
in-memory sort operations in SQL Server 2000
http://support.microsoft.com/defaul...kb;EN-US;890730
Have a nice day!
Best regards,
Adams Qu, MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
--
| Thread-Topic: Error 17883 in SQL error log
| thread-index: AcfVM7K5Tj5qumliSs2GiuzWV3+hMQ==
| X-WBNR-Posting-Host: 207.46.19.168
| From: examnotes <sugarhigh@.community.nospam>
| Subject: Error 17883 in SQL error log
| Date: Thu, 2 Aug 2007 11:34:02 -0700
| Lines: 23
| Message-ID: <EBD8AFCC-B391-4E6C-A341-0BD5A4D62903@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
| Newsgroups: microsoft.public.sqlserver.server
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:21828
| NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| Hello,
|
| We have a SQL server 2000 enterprise edition on SP4 on windows NT, and
got
| the following error recently:
|
| Sleeping until external dump process completes.
| Resuming after waiting on external debug process for 12 seconds.
| Stack Signature for the dump is 0x00000000
| Error: 17883, Severity: 1, State: 0
| Process 1:0 (9d4) UMS Context 0x002977F8 appears to be non-yielding on
| Scheduler 0.
|
| We also get error like below daily:
| SQL Server has encountered 5359 occurrence(s) of IO requests taking
longer
| than 15 seconds to complete on file [E:\Microsoft SQL
| Server\Data\DBAUtility.mdf] in database [DBAUtility] (14). The OS fil
e
| handle is 0x0000053C. The offset of the latest long IO is:
0x00000000010000
|
| The SQL server is used as data warhouse server, so there are a lots of
IO.
|
| I appreciate any suggestions or comments.
|
| Thanks!
|sql

Error 17883

Hi,
We have a SQL server 2000 enterprise edition on SP3 on windows NT, and got
the following error recently:
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x0233C8D8.
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x0233B4F0.
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x0233B8E0.
Error: 17883, Severity: 1, State: 0
The Scheduler 1 appears to be hung. SPID 0, ECID 0, UMS Context 0x023339C0.
SQL server contains databases that are used by Crystal Reports which in turn
is used by an application.
Any suggestions or comments are welcome.
Thanks!Hello Sharman!
This is a known issue by Microsoft and they have a Fix document about this.
You may want to read it from the following address:
http://support.microsoft.com/default.aspx/kb/815056
Ekrem Ã?nsoy
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:03F33925-3ED7-4BDF-9502-7953C4C11857@.microsoft.com...
> Hi,
> We have a SQL server 2000 enterprise edition on SP3 on windows NT, and got
> the following error recently:
> Error: 17883, Severity: 1, State: 0
> The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context
> 0x0233C8D8.
> Error: 17883, Severity: 1, State: 0
> The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context
> 0x0233B4F0.
> Error: 17883, Severity: 1, State: 0
> The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context
> 0x0233B8E0.
> Error: 17883, Severity: 1, State: 0
> The Scheduler 1 appears to be hung. SPID 0, ECID 0, UMS Context
> 0x023339C0.
> SQL server contains databases that are used by Crystal Reports which in
> turn
> is used by an application.
> Any suggestions or comments are welcome.
> Thanks!
>sql

Error 1603 During Installation

I'm encountering an error 1603 durring installation of Reporting Services
Enterprise Edition. I've read the knowledge base article about installing
without creating virtual directories but during that install, I get another
error. This error states 'This installation package could not be opened.
Verify that the package exists and that you can access it or contact the
application vendor to verify that this is a valid windows installer package.'
I'm pretty sure that I've specified the path to setup.exe and the .msi file
correctly in the command line. I've tried installing as me, a user with
administrative priveleges, and as Administrator and I receive the same error.
There are no log files written that I can see. Can anyone help me with this?
TIA
ErnieErnie,
I had same problem. I did this:
1. copied the the RS setup files to a folder named "ENT" root to the c
drive. This is the same drive as sql is installed.
2. from the command line in the "ENT" folder typed this EXACTLY:
setup /i "C:\ent\setup\rsrun.msi" RSDONOTCREATEVIRTUALDIRECTORIES=True
It worked. Before, I tried several different cominations of paths and
starting locations that did not work. I don't know why but this did the
trick. Hope it helps.
pepe
"ebferro" wrote:
> I'm encountering an error 1603 durring installation of Reporting Services
> Enterprise Edition. I've read the knowledge base article about installing
> without creating virtual directories but during that install, I get another
> error. This error states 'This installation package could not be opened.
> Verify that the package exists and that you can access it or contact the
> application vendor to verify that this is a valid windows installer package.'
> I'm pretty sure that I've specified the path to setup.exe and the .msi file
> correctly in the command line. I've tried installing as me, a user with
> administrative priveleges, and as Administrator and I receive the same error.
> There are no log files written that I can see. Can anyone help me with this?
> TIA
> Ernie|||Pepe:
Thanks for the suggestion but it still crashes with the same error message.
I guess I'm hosed.
Ernie
"pepe" wrote:
> Ernie,
> I had same problem. I did this:
> 1. copied the the RS setup files to a folder named "ENT" root to the c
> drive. This is the same drive as sql is installed.
> 2. from the command line in the "ENT" folder typed this EXACTLY:
> setup /i "C:\ent\setup\rsrun.msi" RSDONOTCREATEVIRTUALDIRECTORIES=True
> It worked. Before, I tried several different cominations of paths and
> starting locations that did not work. I don't know why but this did the
> trick. Hope it helps.
> pepe
>
> "ebferro" wrote:
> > I'm encountering an error 1603 durring installation of Reporting Services
> > Enterprise Edition. I've read the knowledge base article about installing
> > without creating virtual directories but during that install, I get another
> > error. This error states 'This installation package could not be opened.
> > Verify that the package exists and that you can access it or contact the
> > application vendor to verify that this is a valid windows installer package.'
> > I'm pretty sure that I've specified the path to setup.exe and the .msi file
> > correctly in the command line. I've tried installing as me, a user with
> > administrative priveleges, and as Administrator and I receive the same error.
> > There are no log files written that I can see. Can anyone help me with this?
> > TIA
> > Ernie|||Don't quit trying. I must have tried 25 times before it worked.
"ebferro" wrote:
> Pepe:
> Thanks for the suggestion but it still crashes with the same error message.
> I guess I'm hosed.
> Ernie
> "pepe" wrote:
> > Ernie,
> >
> > I had same problem. I did this:
> > 1. copied the the RS setup files to a folder named "ENT" root to the c
> > drive. This is the same drive as sql is installed.
> > 2. from the command line in the "ENT" folder typed this EXACTLY:
> >
> > setup /i "C:\ent\setup\rsrun.msi" RSDONOTCREATEVIRTUALDIRECTORIES=True
> >
> > It worked. Before, I tried several different cominations of paths and
> > starting locations that did not work. I don't know why but this did the
> > trick. Hope it helps.
> >
> > pepe
> >
> >
> > "ebferro" wrote:
> >
> > > I'm encountering an error 1603 durring installation of Reporting Services
> > > Enterprise Edition. I've read the knowledge base article about installing
> > > without creating virtual directories but during that install, I get another
> > > error. This error states 'This installation package could not be opened.
> > > Verify that the package exists and that you can access it or contact the
> > > application vendor to verify that this is a valid windows installer package.'
> > > I'm pretty sure that I've specified the path to setup.exe and the .msi file
> > > correctly in the command line. I've tried installing as me, a user with
> > > administrative priveleges, and as Administrator and I receive the same error.
> > > There are no log files written that I can see. Can anyone help me with this?
> > > TIA
> > > Erniesql

Error 15401

Hi folks,
When using the "Enterprise Manager" to add logins to a SQL Server
instance, I'm running into an error 15401. Before I get too far, let me
describe the environment I'm doing this in:
We have two domains:
Domain A is an old NT 4 style domain.
Domain B is a new Active Directory domain powered by Windows Server 2003
running in the "Windows Server 2003" domain functional level.
We're in the process of transitioning from Domain A (with the hopes of
retiring the domain soon), to Domain B. As such, currently, there is a
two trusts between Domain A and Domain B (going in each direction).
On Windows Server 2003 machine on Domain B, I've installed SQL Server
2000, and have it patched to SP4. I've set up a new database on this
SQL server (running as a standard domain B user), and was in the process
of adding logins for it when I encountered the error 15401. Precisely
what I was doing was using the Enterprise Manager on the server directly
to add logins, specifically I was trying to add a few groups from Domain
A to the databse. This is where the error crops up.
(I should note, adding users of Domain B is not a problem, that
functions correctly.)
So, I started troubleshooting, and in doing so, looked over this document:
http://support.microsoft.com/default...b;en-us;324321
None of the situations described in that document apply. There is no
possability of duplicate logins, as this is a new install of SQL Server,
and a freshly created database (just to be sure tho, I manually examined
the syslogin tables in the master db).
There is no problem with the Domain Trust, as the Enterprise Manager on
the same machine as SQL Server is on, can display a list of groups and
accounts from both Domain A and Domain B, not to mention people can from
Domain A can connect to shares offered on the Window Server without trouble.
I've also read that its possible that SQL Server internally caches SIDs,
so I rebooted both the server, and the PDC for Domain A, as well as the
domain controllers for Domain B, with no success.
One additional symptom (not knowing how else to describe it). When an
ASP page, running as a user from Domain A, attempts to connect to the
database in Domain B, it gets a "Login failed for user 'derek'.", even
though the page is running as "A\scott". So where it gets "derek" from,
I haven't even a slightest clue.
If anyone has any ideas or help, it would be greatly appreciated.
Thanks
Scott
It looks to me like you have covered all of the likely problems... Perhaps
a call to PSS is your next step.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Scott Peron" <scott@.infolytica.com> wrote in message
news:%23VTQ%23HuYFHA.3488@.tk2msftngp13.phx.gbl...
> Hi folks,
> When using the "Enterprise Manager" to add logins to a SQL Server
> instance, I'm running into an error 15401. Before I get too far, let me
> describe the environment I'm doing this in:
> We have two domains:
> Domain A is an old NT 4 style domain.
> Domain B is a new Active Directory domain powered by Windows Server 2003
> running in the "Windows Server 2003" domain functional level.
> We're in the process of transitioning from Domain A (with the hopes of
> retiring the domain soon), to Domain B. As such, currently, there is a
> two trusts between Domain A and Domain B (going in each direction).
> On Windows Server 2003 machine on Domain B, I've installed SQL Server
> 2000, and have it patched to SP4. I've set up a new database on this SQL
> server (running as a standard domain B user), and was in the process of
> adding logins for it when I encountered the error 15401. Precisely what I
> was doing was using the Enterprise Manager on the server directly to add
> logins, specifically I was trying to add a few groups from Domain A to the
> databse. This is where the error crops up.
> (I should note, adding users of Domain B is not a problem, that functions
> correctly.)
> So, I started troubleshooting, and in doing so, looked over this document:
> http://support.microsoft.com/default...b;en-us;324321
> None of the situations described in that document apply. There is no
> possability of duplicate logins, as this is a new install of SQL Server,
> and a freshly created database (just to be sure tho, I manually examined
> the syslogin tables in the master db).
> There is no problem with the Domain Trust, as the Enterprise Manager on
> the same machine as SQL Server is on, can display a list of groups and
> accounts from both Domain A and Domain B, not to mention people can from
> Domain A can connect to shares offered on the Window Server without
> trouble.
> I've also read that its possible that SQL Server internally caches SIDs,
> so I rebooted both the server, and the PDC for Domain A, as well as the
> domain controllers for Domain B, with no success.
> One additional symptom (not knowing how else to describe it). When an ASP
> page, running as a user from Domain A, attempts to connect to the database
> in Domain B, it gets a "Login failed for user 'derek'.", even though the
> page is running as "A\scott". So where it gets "derek" from, I haven't
> even a slightest clue.
> If anyone has any ideas or help, it would be greatly appreciated.
> Thanks
> Scott

Error 15401

Hi folks,
When using the "Enterprise Manager" to add logins to a SQL Server
instance, I'm running into an error 15401. Before I get too far, let me
describe the environment I'm doing this in:
We have two domains:
Domain A is an old NT 4 style domain.
Domain B is a new Active Directory domain powered by Windows Server 2003
running in the "Windows Server 2003" domain functional level.
We're in the process of transitioning from Domain A (with the hopes of
retiring the domain soon), to Domain B. As such, currently, there is a
two trusts between Domain A and Domain B (going in each direction).
On Windows Server 2003 machine on Domain B, I've installed SQL Server
2000, and have it patched to SP4. I've set up a new database on this
SQL server (running as a standard domain B user), and was in the process
of adding logins for it when I encountered the error 15401. Precisely
what I was doing was using the Enterprise Manager on the server directly
to add logins, specifically I was trying to add a few groups from Domain
A to the databse. This is where the error crops up.
(I should note, adding users of Domain B is not a problem, that
functions correctly.)
So, I started troubleshooting, and in doing so, looked over this document:
http://support.microsoft.com/default.aspx?scid=kb;en-us;324321
None of the situations described in that document apply. There is no
possability of duplicate logins, as this is a new install of SQL Server,
and a freshly created database (just to be sure tho, I manually examined
the syslogin tables in the master db).
There is no problem with the Domain Trust, as the Enterprise Manager on
the same machine as SQL Server is on, can display a list of groups and
accounts from both Domain A and Domain B, not to mention people can from
Domain A can connect to shares offered on the Window Server without trouble.
I've also read that its possible that SQL Server internally caches SIDs,
so I rebooted both the server, and the PDC for Domain A, as well as the
domain controllers for Domain B, with no success.
One additional symptom (not knowing how else to describe it). When an
ASP page, running as a user from Domain A, attempts to connect to the
database in Domain B, it gets a "Login failed for user 'derek'.", even
though the page is running as "A\scott". So where it gets "derek" from,
I haven't even a slightest clue.
If anyone has any ideas or help, it would be greatly appreciated.
Thanks
ScottIt looks to me like you have covered all of the likely problems... Perhaps
a call to PSS is your next step.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Scott Peron" <scott@.infolytica.com> wrote in message
news:%23VTQ%23HuYFHA.3488@.tk2msftngp13.phx.gbl...
> Hi folks,
> When using the "Enterprise Manager" to add logins to a SQL Server
> instance, I'm running into an error 15401. Before I get too far, let me
> describe the environment I'm doing this in:
> We have two domains:
> Domain A is an old NT 4 style domain.
> Domain B is a new Active Directory domain powered by Windows Server 2003
> running in the "Windows Server 2003" domain functional level.
> We're in the process of transitioning from Domain A (with the hopes of
> retiring the domain soon), to Domain B. As such, currently, there is a
> two trusts between Domain A and Domain B (going in each direction).
> On Windows Server 2003 machine on Domain B, I've installed SQL Server
> 2000, and have it patched to SP4. I've set up a new database on this SQL
> server (running as a standard domain B user), and was in the process of
> adding logins for it when I encountered the error 15401. Precisely what I
> was doing was using the Enterprise Manager on the server directly to add
> logins, specifically I was trying to add a few groups from Domain A to the
> databse. This is where the error crops up.
> (I should note, adding users of Domain B is not a problem, that functions
> correctly.)
> So, I started troubleshooting, and in doing so, looked over this document:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;324321
> None of the situations described in that document apply. There is no
> possability of duplicate logins, as this is a new install of SQL Server,
> and a freshly created database (just to be sure tho, I manually examined
> the syslogin tables in the master db).
> There is no problem with the Domain Trust, as the Enterprise Manager on
> the same machine as SQL Server is on, can display a list of groups and
> accounts from both Domain A and Domain B, not to mention people can from
> Domain A can connect to shares offered on the Window Server without
> trouble.
> I've also read that its possible that SQL Server internally caches SIDs,
> so I rebooted both the server, and the PDC for Domain A, as well as the
> domain controllers for Domain B, with no success.
> One additional symptom (not knowing how else to describe it). When an ASP
> page, running as a user from Domain A, attempts to connect to the database
> in Domain B, it gets a "Login failed for user 'derek'.", even though the
> page is running as "A\scott". So where it gets "derek" from, I haven't
> even a slightest clue.
> If anyone has any ideas or help, it would be greatly appreciated.
> Thanks
> Scott

Error 15401

Hi folks,
When using the "Enterprise Manager" to add logins to a SQL Server
instance, I'm running into an error 15401. Before I get too far, let me
describe the environment I'm doing this in:
We have two domains:
Domain A is an old NT 4 style domain.
Domain B is a new Active Directory domain powered by Windows Server 2003
running in the "Windows Server 2003" domain functional level.
We're in the process of transitioning from Domain A (with the hopes of
retiring the domain soon), to Domain B. As such, currently, there is a
two trusts between Domain A and Domain B (going in each direction).
On Windows Server 2003 machine on Domain B, I've installed SQL Server
2000, and have it patched to SP4. I've set up a new database on this
SQL server (running as a standard domain B user), and was in the process
of adding logins for it when I encountered the error 15401. Precisely
what I was doing was using the Enterprise Manager on the server directly
to add logins, specifically I was trying to add a few groups from Domain
A to the databse. This is where the error crops up.
(I should note, adding users of Domain B is not a problem, that
functions correctly.)
So, I started troubleshooting, and in doing so, looked over this document:
http://support.microsoft.com/defaul...kb;en-us;324321
None of the situations described in that document apply. There is no
possability of duplicate logins, as this is a new install of SQL Server,
and a freshly created database (just to be sure tho, I manually examined
the syslogin tables in the master db).
There is no problem with the Domain Trust, as the Enterprise Manager on
the same machine as SQL Server is on, can display a list of groups and
accounts from both Domain A and Domain B, not to mention people can from
Domain A can connect to shares offered on the Window Server without trouble.
I've also read that its possible that SQL Server internally caches SIDs,
so I rebooted both the server, and the PDC for Domain A, as well as the
domain controllers for Domain B, with no success.
One additional symptom (not knowing how else to describe it). When an
ASP page, running as a user from Domain A, attempts to connect to the
database in Domain B, it gets a "Login failed for user 'derek'.", even
though the page is running as "A\scott". So where it gets "derek" from,
I haven't even a slightest clue.
If anyone has any ideas or help, it would be greatly appreciated.
Thanks
ScottIt looks to me like you have covered all of the likely problems... Perhaps
a call to PSS is your next step.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Scott Peron" <scott@.infolytica.com> wrote in message
news:%23VTQ%23HuYFHA.3488@.tk2msftngp13.phx.gbl...
> Hi folks,
> When using the "Enterprise Manager" to add logins to a SQL Server
> instance, I'm running into an error 15401. Before I get too far, let me
> describe the environment I'm doing this in:
> We have two domains:
> Domain A is an old NT 4 style domain.
> Domain B is a new Active Directory domain powered by Windows Server 2003
> running in the "Windows Server 2003" domain functional level.
> We're in the process of transitioning from Domain A (with the hopes of
> retiring the domain soon), to Domain B. As such, currently, there is a
> two trusts between Domain A and Domain B (going in each direction).
> On Windows Server 2003 machine on Domain B, I've installed SQL Server
> 2000, and have it patched to SP4. I've set up a new database on this SQL
> server (running as a standard domain B user), and was in the process of
> adding logins for it when I encountered the error 15401. Precisely what I
> was doing was using the Enterprise Manager on the server directly to add
> logins, specifically I was trying to add a few groups from Domain A to the
> databse. This is where the error crops up.
> (I should note, adding users of Domain B is not a problem, that functions
> correctly.)
> So, I started troubleshooting, and in doing so, looked over this document:
> http://support.microsoft.com/defaul...kb;en-us;324321
> None of the situations described in that document apply. There is no
> possability of duplicate logins, as this is a new install of SQL Server,
> and a freshly created database (just to be sure tho, I manually examined
> the syslogin tables in the master db).
> There is no problem with the Domain Trust, as the Enterprise Manager on
> the same machine as SQL Server is on, can display a list of groups and
> accounts from both Domain A and Domain B, not to mention people can from
> Domain A can connect to shares offered on the Window Server without
> trouble.
> I've also read that its possible that SQL Server internally caches SIDs,
> so I rebooted both the server, and the PDC for Domain A, as well as the
> domain controllers for Domain B, with no success.
> One additional symptom (not knowing how else to describe it). When an ASP
> page, running as a user from Domain A, attempts to connect to the database
> in Domain B, it gets a "Login failed for user 'derek'.", even though the
> page is running as "A\scott". So where it gets "derek" from, I haven't
> even a slightest clue.
> If anyone has any ideas or help, it would be greatly appreciated.
> Thanks
> Scott

error 15007: The login'anything' does not exist.

This error makes no sense to me whatsoever.
I'm using Enterprise Manager to create a new user for a new dbase and
regardless of anything I put in there, it gives me that 15007 message.Make sure the user that you are adding to the database has corresponding
login created.
Ex:
--To create login
use master
go
sp_addlogin 'user1', 'password'
go
--To add the user to the current database(here im picking up northwind).
use northwind
go
sp_grantdbaccess 'user1'
go
--
-Vishal
"Robert Blackwell" <robbie@.NOspamwowcentral.com> wrote in message
news:enYIIRVVDHA.2328@.TK2MSFTNGP12.phx.gbl...
> This error makes no sense to me whatsoever.
> I'm using Enterprise Manager to create a new user for a new dbase and
> regardless of anything I put in there, it gives me that 15007 message.
>|||Okay thanks, I was able to copy your instructions exactly. However, isn't
there a way to do all of that in Enterprise Manager?|||Hmm, maybe I should try clicking the new login button on the tool bar? ;o)
Thanks again.

Error 14262: specified @job_id... does not exist

Got a client who is getting this error when trying "Start synchronizing" on
a subscription in Enterprise Manager. When the subscription is run using the
Administrator account which originally created it, it runs OK. But when a
different account is being used, this error is thrown. Do subscriptions have
to be synchronized by the account which created them?
--
Mark
Is this a push or pull subscription? How is the subscription run?
The account should be in the PAL and the job owner should be the sa account.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Mark Rendle" <markdotrendleatcomputersoftwaredotcom> wrote in message
news:OKJGoHeFGHA.516@.TK2MSFTNGP15.phx.gbl...
> Got a client who is getting this error when trying "Start synchronizing"
> on a subscription in Enterprise Manager. When the subscription is run
> using the Administrator account which originally created it, it runs OK.
> But when a different account is being used, this error is thrown. Do
> subscriptions have to be synchronized by the account which created them?
> --
> --
> Mark
>
|||It's a pull subscription to a merge replication.
--
Mark
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:ukMaDdeFGHA.3056@.TK2MSFTNGP09.phx.gbl...
> Is this a push or pull subscription? How is the subscription run?
> The account should be in the PAL and the job owner should be the sa
> account.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Mark Rendle" <markdotrendleatcomputersoftwaredotcom> wrote in message
> news:OKJGoHeFGHA.516@.TK2MSFTNGP15.phx.gbl...
>
|||I've seen this error when the subscription has been running, was deleted,
and then recreated. EM has cached the old job's information. Can you try a
refresh before trying to run the job again?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Mark Rendle" <markdotrendleatcomputersoftwaredotcom> wrote in message
news:%23mzaXIpFGHA.2012@.TK2MSFTNGP14.phx.gbl...
> It's a pull subscription to a merge replication.
> --
> --
> Mark
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:ukMaDdeFGHA.3056@.TK2MSFTNGP09.phx.gbl...
>

Error 14258

For the last two days I've been getting this error whenever I click on a Job
in Enterprise Manager:
Error 14258: Cannot perform this operation while SQLServerAgent is starting.
Try again later.
Any idea what is causing this? Agent appears to be running - it is
performing the assigned tasks on schedule.
I am also have a ongoing issue with this problem. Where you able to find
the root cause of this issue? Please let me know, as we are in bad need
of a solution to this problem.
Reply to thovorka@.quickutz.com
Thanks,
Todd
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

Error 14258

For the last two days I've been getting this error whenever I click on a Job
in Enterprise Manager:
Error 14258: Cannot perform this operation while SQLServerAgent is starting.
Try again later.
Any idea what is causing this? Agent appears to be running - it is
performing the assigned tasks on schedule.I am also have a ongoing issue with this problem. Where you able to find
the root cause of this issue? Please let me know, as we are in bad need
of a solution to this problem.
Reply to thovorka@.quickutz.com
Thanks,
Todd
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

Error 14258

For the last two days I've been getting this error whenever I click on a Job
in Enterprise Manager:
Error 14258: Cannot perform this operation while SQLServerAgent is starting.
Try again later.
Any idea what is causing this? Agent appears to be running - it is
performing the assigned tasks on schedule.Hi,
The SQLServerAgent has NOT started properly after a
shutdown/reboot two days ago. If you look at the service
manager, the service appears to have started, but its
really not.
Here is what you have to do:
Stop the SQLServerAgent (Not SQL Server)
Restart the service (make no errors are recorded)
Here is something else you may have not noticed, since
this error has been occurring, your scheduled jobs have
not run. You might want to backup your databases and run
any other jobs you may have.
hth
DeeJay
>--Original Message--
>For the last two days I've been getting this error
whenever I click on a Job
>in Enterprise Manager:
>Error 14258: Cannot perform this operation while
SQLServerAgent is starting.
>Try again later.
>Any idea what is causing this? Agent appears to be
running - it is
>performing the assigned tasks on schedule.
>
>.
>|||OK I've stopped and restarted the service several times. Event Viewer claims
the service started succesfully. Where else can I look for errors? The SQL
Server logs show no errors with the Agent. But you are correct - the jobs
are NOT running! Any other sugggestions on where to look for the problem?
"DeeJay Puar" <deejaypuar@.Yahoo.com> wrote in message
news:393601c48f89$d0181ff0$a501280a@.phx.gbl...
> Hi,
> The SQLServerAgent has NOT started properly after a
> shutdown/reboot two days ago. If you look at the service
> manager, the service appears to have started, but its
> really not.
> Here is what you have to do:
> Stop the SQLServerAgent (Not SQL Server)
> Restart the service (make no errors are recorded)
> Here is something else you may have not noticed, since
> this error has been occurring, your scheduled jobs have
> not run. You might want to backup your databases and run
> any other jobs you may have.
> hth
> DeeJay
> >--Original Message--
> >For the last two days I've been getting this error
> whenever I click on a Job
> >in Enterprise Manager:
> >
> >Error 14258: Cannot perform this operation while
> SQLServerAgent is starting.
> >Try again later.
> >
> >Any idea what is causing this? Agent appears to be
> running - it is
> >performing the assigned tasks on schedule.
> >
> >
> >.
> >|||I am also have a ongoing issue with this problem. Where you able to find
the root cause of this issue? Please let me know, as we are in bad need
of a solution to this problem.
Reply to thovorka@.quickutz.com
Thanks,
Todd
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Error 14053 and Push Replication

SQL Server Enterprise Manager encountered errors creating push subscriptions
for the following Subscribers:
[Subscriber Server Name]: Error 14053: Cannot load the DLL replincrementlsn
extended procedure, or one of the DLLs it references. Reason: 126(error not
found).
The subscription could not be updated at this time.
The subscription could not be created.
The publisher and distributor are running SQL Server 2000 SP3a, the
subscriber is RTM (no SP applied expect for the criticial release update).
The subscriber has a new server just released into production, hence why no
SP yet.
The publisher and subscriber are on non trusting domains, but on the
internal network.
I have checked the SP log file (C:\Windows\) and have been advised that both
sp_replincrementlsn and sp_replincrementlsn_internal exist in the master
table on both servers. I also reattempted to install SP3a on the publisher
server to no avail.
All work has been carried out in Ent Mgr.
I thank anyone in advance for their assistance, as I am totally lost for
ideas.
Betty,
can you run this on the distributor, just to confirm that the stored
procedure was created correctly:
sp_helptext sp_replincrementlsn
Please check that xprepl.dll is in your sql bin directory (eg C:\Program
Files\Microsoft SQL Server\MSSQL\Binn).
Please check the sql server error log for any issues recorded there.
Have a look at sqlsp.log file from the c:\windows directory this might shed
some light on any failed actions during the sp installation
If any of this returns something interesting then please post it up,
otherwise I'd reinstall sp3a.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul,
I ran the steps you requested on our distribution server (which is also the
publication server)
- sp_helptext sp_replincrementlsn returned no issue, the sp does exist, but
only in the master table.
- xprepl.dll DOES exist in the BINN directory of the SQL Server
- The SQL Server reports no error, and even reports that it is using
xprepl.dll for replication
- SQLsp.log appears to contain no critical errors (the only error of sort is
the one that indicates that some data files could not be modified - the
reason being that those databases are in the offline state.
- I am still yet to reinstall SP3a, awaiting for authorisation from the
server controller, but previous attempts have not worked.
Anyother ideas?
Thanks,
Betty.
"Paul Ibison" wrote:

> Betty,
> can you run this on the distributor, just to confirm that the stored
> procedure was created correctly:
> sp_helptext sp_replincrementlsn
> Please check that xprepl.dll is in your sql bin directory (eg C:\Program
> Files\Microsoft SQL Server\MSSQL\Binn).
> Please check the sql server error log for any issues recorded there.
> Have a look at sqlsp.log file from the c:\windows directory this might shed
> some light on any failed actions during the sp installation
> If any of this returns something interesting then please post it up,
> otherwise I'd reinstall sp3a.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||With this type of installation error, I'd apply the
service pack, reinstall completely and ring PSS in this
order assuming the error is repeated at each step.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul,
one interesting thing is that the SP3Readme.htm states that this error can
be safely ignored.
Regards,
Betty.
"Paul Ibison" wrote:

> With this type of installation error, I'd apply the
> service pack, reinstall completely and ring PSS in this
> order assuming the error is repeated at each step.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Paul,
after applying SP3 it appears that the replication works, it states, that it
said the replication was created successfully.
I think what happens, is if you attempt to create your first publication,
distributor, or subscriber, after SP3 has been applied, you need to reapply
SP3 to update the replication system files.
Thank you for your assitance,
Betty.

Error 126 , SQL 2K

I am getting the following error when I launch Enterprise Manager
Error 126 : General Error
I am using SQL 2000 on Windows XP. I have uninstalled and reinstalled SQL but Im still getting the error.

Please help.

Thanks
GDon't use XP?

Error 1222 Lock Request time out period exceed

Hi, I'm getting this error when I tried to click on the Current Activity in
the Enterprise Manager. This is a SQL2000 running on Windows2000. Does
anyone know what causes this and how to fix it? I also get this error
sometimes when I run a crystal report in my C# application.
Thanks,
AlphaA transaction is being blocked to acquire a lock because another transaction
already locked the resource.
See "Customizing the Lock Time-out" in BOL.
AMB
"Alpha" wrote:
> Hi, I'm getting this error when I tried to click on the Current Activity in
> the Enterprise Manager. This is a SQL2000 running on Windows2000. Does
> anyone know what causes this and how to fix it? I also get this error
> sometimes when I run a crystal report in my C# application.
> Thanks,
> Alpha|||Do not use the GUI. Instead, get used to sp_who, sp_who2 or sp_who1 in Query
Analyzer.
"Alpha" <Alpha@.discussions.microsoft.com> wrote in message
news:16FC85B9-57C8-4906-AC47-3B9E826D9A79@.microsoft.com...
> Hi, I'm getting this error when I tried to click on the Current Activity
> in
> the Enterprise Manager. This is a SQL2000 running on Windows2000. Does
> anyone know what causes this and how to fix it? I also get this error
> sometimes when I run a crystal report in my C# application.
> Thanks,
> Alpha|||Thank you. That was very helpful.
"Alejandro Mesa" wrote:
> A transaction is being blocked to acquire a lock because another transaction
> already locked the resource.
> See "Customizing the Lock Time-out" in BOL.
>
> AMB
> "Alpha" wrote:
> > Hi, I'm getting this error when I tried to click on the Current Activity in
> > the Enterprise Manager. This is a SQL2000 running on Windows2000. Does
> > anyone know what causes this and how to fix it? I also get this error
> > sometimes when I run a crystal report in my C# application.
> >
> > Thanks,
> > Alpha

Error 0: Cannot load the DLL xpstar.dll, or one of the DLLs it references. Reason: 5(Acces

Hi,
When I run Microsoft SQL Server Enterprise Manager and click on the
Properties of the SQL Server Registration, I get this error. Error 0: Cannot
load the DLL xpstar.dll, or one of the DLLs it references. Reason: 5(Access
is denied.). The SQL Server has the latest service pack SP3a. How can I
solve this problem? I used Google but didn't found a solution. Thanks in
advance.
Kind regards,
Sven Aeyels.Sven,
1. Does the SQLServer account has relevant privilege on the /Binn folder
where most of the DLLs reside?
2.Any more info in the event viewer?
3.Did you install any software after SQLServer which might have messed up
the DLLs? Even otherwise try to Run Component Checker tool to check any
discrepancies in the MDAC.More info:
'INFO: Component Checker: Diagnose Problems and Reconfigure MDAC
Installations'
http://support.microsoft.com/?id=307255
4.See if a MDAC reinstall solves the issue.
--
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Sven Aeyels" <sven_aeyels@.hotmail.com> wrote in message
news:eJBfsqgSEHA.1732@.TK2MSFTNGP09.phx.gbl...
> Hi,
> When I run Microsoft SQL Server Enterprise Manager and click on the
> Properties of the SQL Server Registration, I get this error. Error 0:
Cannot
> load the DLL xpstar.dll, or one of the DLLs it references. Reason:
5(Access
> is denied.). The SQL Server has the latest service pack SP3a. How can I
> solve this problem? I used Google but didn't found a solution. Thanks in
> advance.
> Kind regards,
> Sven Aeyels.
>|||Hi,
Thanks for the info. I reinstalled the MDAC and the problem is gone.
I think the problem started when I installed the Security Update for
Microsoft Data Access Components (KB832483). Are there any known issues with
this update? Thanks in advance.
Kind Regards,
Sven Aeyels.
"Sven Aeyels" <sven_aeyels@.hotmail.com> wrote in message
news:eJBfsqgSEHA.1732@.TK2MSFTNGP09.phx.gbl...
> Hi,
> When I run Microsoft SQL Server Enterprise Manager and click on the
> Properties of the SQL Server Registration, I get this error. Error 0:
Cannot
> load the DLL xpstar.dll, or one of the DLLs it references. Reason:
5(Access
> is denied.). The SQL Server has the latest service pack SP3a. How can I
> solve this problem? I used Google but didn't found a solution. Thanks in
> advance.
> Kind regards,
> Sven Aeyels.
>

Error (rsInternalError) after installation

I have installed Reporting Services 2005 64bit Enterprise Edition on WIN 2003 64bit SP1 Enterprise Edition.

Reporting Services Configuration Manager indicate that everything is ok, green checks except Encryption Keys and Execution Account.

Reporting Services databases, ReportServer and ReportServerTempDB, is not "installed" at the same server. Tha DB's runs at a SQL 2005 Server 64bit in the same domain.

I get following error:

http://localhost/reportserver:

An internal error occurred on the report server. See the error log for more details. (rsInternalError) Get Online Help
Object reference not set to an instance of an object.

Event Viewer:

Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date: 2006-02-24
Time: 10:11:35
User: N/A
Computer: PRD128ASAL
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 2006-02-24 10:11:35
Event time (UTC): 2006-02-24 09:00:25
Event ID: ac7dc3e0abc2412aab9566d56f81859e
Event sequence: 12
Event occurrence: 7
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1/root/ReportServer-1-127851854434156417
Trust level: RosettaSrv
Application Virtual Path: /ReportServer
Application Path: C:\Program Files\Microsoft SQL Server\MSSQL.1\Reporting Services\ReportServer\
Machine name: XXXXXXXXXX
Process information:
Process ID: 1900
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Exception information:
Exception type: NullReferenceException
Exception message: Object reference not set to an instance of an object.
Request information:
Request URL: http://localhost/reportserver
Request path: /reportserver
User host address: 127.0.0.1
User: DOMAIN\USERID
Is authenticated: True
Authentication Type: Negotiate
Thread account name: NT AUTHORITY\NETWORK SERVICE
Thread information:
Thread ID: 1
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: True
Stack trace: at Microsoft.ReportingServices.Diagnostics.Globals.EndRequestContext()
at Microsoft.ReportingServices.WebServer.Global.Application_EndRequest(Object sender, EventArgs e)
at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Custom event details:

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Reporting Services LogFiles:

w3wp!library!8!02/24/2006-10:11:35:: e ERROR: Connection close failed. Exception thrown: System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.ReportingServices.Library.ConnectionManager.DisconnectStorage()
w3wp!library!1!2006-02-24-10:11:35:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailableException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailableException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. > System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.ReportingServices.Library.ConnectionManager.OpenConnection()
at Microsoft.ReportingServices.Library.ConnectionManager.ConnectStorage()
at Microsoft.ReportingServices.Library.RunningJobsDb.GetMyRunningJobs()
End of inner exception stack trace
w3wp!library!1!2006-02-24-10:11:35:: e ERROR: Connection close failed. Exception thrown: System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.ReportingServices.Library.ConnectionManager.DisconnectStorage()
w3wp!runningjobs!1!2006-02-24-10:11:35:: e ERROR: Error in timer Running Requests DB : System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.ReportingServices.Library.ConnectionManager.DisconnectStorage()
at Microsoft.ReportingServices.Library.RunningJobsDb.GetMyRunningJobs()
at Microsoft.ReportingServices.Library.RunningJobDbTimer.DoTimerAction()
at Microsoft.ReportingServices.Diagnostics.TimerActionBase.TimerAction(Object unused)

Thankful for solution or any idea!

Regards, Jonas

Take a look at this thread.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=250225&SiteID=1

|||

Thanks Trish!

If I stop Reporting Services service, restarts the IIS and starts the Reporting Services service again I get following error.

http://localhost/reportserver:

The event source "Report Server" does not exist. (rsEventLogSourceNotFound)

Reporting Services LogFiles:

w3wp!library!1!2006-02-24-16:08:09:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.EventLogSourceNotFound: The event source "Report Server" does not exist., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.EventLogSourceNotFound: The event source "Report Server" does not exist.

After some minute I refresh the browser and now I get rsInternalError again.

(This behaviour is repeatable.)

It's possible that I have edit (no change!) the ASP.NET tab under properties for the ReportServer website in IIS 6. Why? Some of my first actions after discovering that the installation didn't work was to look in the IIS 6 MMC...

Any suggestions?

Regards, Jonas

|||

The only way we could fix the problem was to uninstall SQL Server and reinstall it.

We tried everything we could think of but it still didn't help. Now we know not to touch those settings!

|||

After hours of thinking, testing, googleing and head scratching I found a workaround.
I tried to change the Reporting Services application pool identity to a windows account. And it worked. This window account is a member of local administrators. Haven't tried more restricted rights yet.
But documentation from Microsoft recommends to use Network Service as application pool identity for Reporting Services.

I found this url interesting, http://support.microsoft.com/kb/896861/.
But I tried both workaround descibed whitout success.

Any idea? Anyone?
I really would like to use the Network Service account as recommended by Microsoft.

Regards, Jonas

|||

Try my solution on the following thread:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1985313&SiteID=1

Regards

Denis

Error (rsInternalError) after installation

I have installed Reporting Services 2005 64bit Enterprise Edition on WIN 2003 64bit SP1 Enterprise Edition.

Reporting Services Configuration Manager indicate that everything is ok, green checks except Encryption Keys and Execution Account.

Reporting Services databases, ReportServer and ReportServerTempDB, is not "installed" at the same server. Tha DB's runs at a SQL 2005 Server 64bit in the same domain.

I get following error:

http://localhost/reportserver:

An internal error occurred on the report server. See the error log for more details. (rsInternalError) Get Online Help
Object reference not set to an instance of an object.

Event Viewer:

Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date: 2006-02-24
Time: 10:11:35
User: N/A
Computer: PRD128ASAL
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 2006-02-24 10:11:35
Event time (UTC): 2006-02-24 09:00:25
Event ID: ac7dc3e0abc2412aab9566d56f81859e
Event sequence: 12
Event occurrence: 7
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1/root/ReportServer-1-127851854434156417
Trust level: RosettaSrv
Application Virtual Path: /ReportServer
Application Path: C:\Program Files\Microsoft SQL Server\MSSQL.1\Reporting Services\ReportServer\
Machine name: XXXXXXXXXX
Process information:
Process ID: 1900
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Exception information:
Exception type: NullReferenceException
Exception message: Object reference not set to an instance of an object.
Request information:
Request URL: http://localhost/reportserver
Request path: /reportserver
User host address: 127.0.0.1
User: DOMAIN\USERID
Is authenticated: True
Authentication Type: Negotiate
Thread account name: NT AUTHORITY\NETWORK SERVICE
Thread information:
Thread ID: 1
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: True
Stack trace: at Microsoft.ReportingServices.Diagnostics.Globals.EndRequestContext()
at Microsoft.ReportingServices.WebServer.Global.Application_EndRequest(Object sender, EventArgs e)
at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Custom event details:

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Reporting Services LogFiles:

w3wp!library!8!02/24/2006-10:11:35:: e ERROR: Connection close failed. Exception thrown: System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.ReportingServices.Library.ConnectionManager.DisconnectStorage()
w3wp!library!1!2006-02-24-10:11:35:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailableException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailableException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. > System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.ReportingServices.Library.ConnectionManager.OpenConnection()
at Microsoft.ReportingServices.Library.ConnectionManager.ConnectStorage()
at Microsoft.ReportingServices.Library.RunningJobsDb.GetMyRunningJobs()
End of inner exception stack trace
w3wp!library!1!2006-02-24-10:11:35:: e ERROR: Connection close failed. Exception thrown: System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.ReportingServices.Library.ConnectionManager.DisconnectStorage()
w3wp!runningjobs!1!2006-02-24-10:11:35:: e ERROR: Error in timer Running Requests DB : System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.ReportingServices.Library.ConnectionManager.DisconnectStorage()
at Microsoft.ReportingServices.Library.RunningJobsDb.GetMyRunningJobs()
at Microsoft.ReportingServices.Library.RunningJobDbTimer.DoTimerAction()
at Microsoft.ReportingServices.Diagnostics.TimerActionBase.TimerAction(Object unused)

Thankful for solution or any idea!

Regards, Jonas

Take a look at this thread.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=250225&SiteID=1

|||

Thanks Trish!

If I stop Reporting Services service, restarts the IIS and starts the Reporting Services service again I get following error.

http://localhost/reportserver:

The event source "Report Server" does not exist. (rsEventLogSourceNotFound)

Reporting Services LogFiles:

w3wp!library!1!2006-02-24-16:08:09:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.EventLogSourceNotFound: The event source "Report Server" does not exist., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.EventLogSourceNotFound: The event source "Report Server" does not exist.

After some minute I refresh the browser and now I get rsInternalError again.

(This behaviour is repeatable.)

It's possible that I have edit (no change!) the ASP.NET tab under properties for the ReportServer website in IIS 6. Why? Some of my first actions after discovering that the installation didn't work was to look in the IIS 6 MMC...

Any suggestions?

Regards, Jonas

|||

The only way we could fix the problem was to uninstall SQL Server and reinstall it.

We tried everything we could think of but it still didn't help. Now we know not to touch those settings!

|||

After hours of thinking, testing, googleing and head scratching I found a workaround.
I tried to change the Reporting Services application pool identity to a windows account. And it worked. This window account is a member of local administrators. Haven't tried more restricted rights yet.
But documentation from Microsoft recommends to use Network Service as application pool identity for Reporting Services.

I found this url interesting, http://support.microsoft.com/kb/896861/.
But I tried both workaround descibed whitout success.

Any idea? Anyone?
I really would like to use the Network Service account as recommended by Microsoft.

Regards, Jonas

|||

Try my solution on the following thread:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1985313&SiteID=1

Regards

Denis