Error encountered while starting the SSIS service

I installed SQL Server 2005 Integration services on Windows XP machine. Then I went to the SQL Server Configuration Manager and tried to Start the SSIS service. The "Log On As" value is "NT AUTHORITY\NetworkService". But I get the follwoing error:

The request failed or the service did not respond in a timely fashion. COnsult the event log or other applicable error logs for details.

Event Log details:
The SQL Server Integration Services service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

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

I tried running the service using the "Local Service" and the "Local System" accounts also, but am still encountering the same error. What do I do...

Are you using SP1? There was a bug in SP1 that stopped the SSIS service from starting under certain conditions.

-Jamie

|||

I dont have any SP installed.

I installed SSIS on another machine and here the service runs successfully under NT AUTHORITY\Network Service. As for the first machine, as of now, I am only able to run it under the current domain account- Is this fine or will it lead to some problems/threats in future.

Error during installation of reporting services

Hi,
I've stuck with an error message and I can't sort it out. I am trying to
install a standard reporting service on a server separated from database
server.
Web server (report services): no domain
Databasebase server: a member of a domain.
I can install RS with domain authentication mode but I can't with SQL
authentication such as sa.
Errror message:
login failed for user '(null)'. reason: not associated with a trusted sql
server connection.
Anyone have an workaround for this error?
ThanksI found that using setup /i command lines and I did without any problem.
"Oliver" <dummy@.hotmail.com> wrote in message
news:eRbesy9EFHA.1936@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I've stuck with an error message and I can't sort it out. I am trying to
> install a standard reporting service on a server separated from database
> server.
> Web server (report services): no domain
> Databasebase server: a member of a domain.
> I can install RS with domain authentication mode but I can't with SQL
> authentication such as sa.
> Errror message:
> login failed for user '(null)'. reason: not associated with a trusted sql
> server connection.
> Anyone have an workaround for this error?
> Thanks
>|||Running setup with the /i command line did not have any impact on this issue
for me.
"Oliver" wrote:
> I found that using setup /i command lines and I did without any problem.
> "Oliver" <dummy@.hotmail.com> wrote in message
> news:eRbesy9EFHA.1936@.TK2MSFTNGP14.phx.gbl...
> > Hi,
> >
> > I've stuck with an error message and I can't sort it out. I am trying to
> > install a standard reporting service on a server separated from database
> > server.
> > Web server (report services): no domain
> > Databasebase server: a member of a domain.
> >
> > I can install RS with domain authentication mode but I can't with SQL
> > authentication such as sa.
> >
> > Errror message:
> > login failed for user '(null)'. reason: not associated with a trusted sql
> > server connection.
> >
> > Anyone have an workaround for this error?
> >
> > Thanks
> >
> >
>
>

Error during browsing the cube

Hi,

I have migrated the anaysis service 2000 cubes to 2005.

In the database i have two cubes say A and B and one virtual cube say C.While migrating the virtual cube C got migrated as a real cube with two linked measure groups for the cubes A and B. I have not processed the cube B.But i have processed the cube A.It succeded and i could browse it once .But when i tried browsing the virual cube C (which migrated as real cube with linked measure group) is not available for browsing .This is because i didnt process the cube B whose measure is also present in C.

But the problem is when i tried to browse cube A which i could browse earlier is giving me error when i try to browse it again.

The error which i found is somethinf like this:Error in the OLAP storage engine:The version of the linked measure group with the name of 'A',on the remote instance has changed.Repeat the operation the resolve the issue.

Please help me to solve this issue ASAP.

Thanks in advance

Regards

Latha

Hi Latha. I have received the same error in the same situation from the SQL Manager when writing my own MDX query. I try the query again (as suggested) and it works. You should try a simple MDX query from SQL Manager and see if the same scenario occurs.

Hope this helps.

PGoldy

|||

Hi,

Since it is a migration from AS 2000 to AS 2005 .

I dont want to make any changes in the query and my AS 2000 cube works fine.

Please tell me, is the error because of the unprocessed cube 'C'(virtual cube migrated with linked measures).

Is it enough if i process the cube C along with Cube A?

Regards

Latha

|||

Hi Latha. Yes, processing the cubes should take care of the error you received.

PGoldy

Error disconnecting clients with ODBC Error

I keep getting an ODBC error (varies) I have SQL 7 on windows 2000 server
with all the updated service packs and patches for the OS and SQL. I also
updated MDAC to 2.8 sp2. We use a third party software program that connects
to the SQL database to store all our data. Every so often we get
disconnected with an ODBC error and have to close the client then reconnect
to the server. The frequency is pretty sparatic sometimes it can occur 5
times and hour or as little as 1 time an hour. Attached is a copy of one of
the error we get if anyone has any ideas as to what could be causing this I
would greatly appreciate it.
ConnectionWrite (WrapperWrite()).
Last SQL String:
select MRecordID from HEATMsg where MTo='Frank' and MStatus='U' and
MType='M' and MDateTime<=1124822591
Last ODBC Command:
Function: SQLPrepare('select MRecordID from HEATMsg where MTo='Frank' and
MStatus='U' and MType='M' and MDateTime<=1124822591'
It's pretty hard to say from what's posted. This looks like
it's a HEAT database. If that's the case, Tracing their
sporadic errors with ODBC tracing will slow things down
quite a bit. You can but it's pretty bad on performance. Try
contacting the vendor, Front Range Solutions. That's
generally quicker.
-Sue
On Tue, 23 Aug 2005 12:33:04 -0700, "Anthony"
<Anthony@.discussions.microsoft.com> wrote:

>I keep getting an ODBC error (varies) I have SQL 7 on windows 2000 server
>with all the updated service packs and patches for the OS and SQL. I also
>updated MDAC to 2.8 sp2. We use a third party software program that connects
>to the SQL database to store all our data. Every so often we get
>disconnected with an ODBC error and have to close the client then reconnect
>to the server. The frequency is pretty sparatic sometimes it can occur 5
>times and hour or as little as 1 time an hour. Attached is a copy of one of
>the error we get if anyone has any ideas as to what could be causing this I
>would greatly appreciate it.
>ConnectionWrite (WrapperWrite()).
>Last SQL String:
>select MRecordID from HEATMsg where MTo='Frank' and MStatus='U' and
>MType='M' and MDateTime<=1124822591
>Last ODBC Command:
>Function: SQLPrepare('select MRecordID from HEATMsg where MTo='Frank' and
>MStatus='U' and MType='M' and MDateTime<=1124822591'
>
|||Anthony,
Try using another ODBC tool like WinSQL
(http://www.synametrics.com/winsql) and see if you get the same behavior.
How far is your database from your client? This could also be a network
issue.
Anthony wrote:
> I keep getting an ODBC error (varies) I have SQL 7 on windows 2000 server
> with all the updated service packs and patches for the OS and SQL. I also
> updated MDAC to 2.8 sp2. We use a third party software program that connects
> to the SQL database to store all our data. Every so often we get
> disconnected with an ODBC error and have to close the client then reconnect
> to the server. The frequency is pretty sparatic sometimes it can occur 5
> times and hour or as little as 1 time an hour. Attached is a copy of one of
> the error we get if anyone has any ideas as to what could be causing this I
> would greatly appreciate it.
> ConnectionWrite (WrapperWrite()).
> Last SQL String:
> select MRecordID from HEATMsg where MTo='Frank' and MStatus='U' and
> MType='M' and MDateTime<=1124822591
> Last ODBC Command:
> Function: SQLPrepare('select MRecordID from HEATMsg where MTo='Frank' and
> MStatus='U' and MType='M' and MDateTime<=1124822591'
>
|||I will look into winsql, thanks. As far as the nework goes everything is in
the same physical location. I have checked network performance and nothing
indicates that it could be a performance problem.
"Dennis Black" wrote:

> Anthony,
> Try using another ODBC tool like WinSQL
> (http://www.synametrics.com/winsql) and see if you get the same behavior.
> How far is your database from your client? This could also be a network
> issue.
>
> Anthony wrote:
>

Error disconnecting clients with ODBC Error

I keep getting an ODBC error (varies) I have SQL 7 on Windows 2000 server
with all the updated service packs and patches for the OS and SQL. I also
updated MDAC to 2.8 sp2. We use a third party software program that connect
s
to the SQL database to store all our data. Every so often we get
disconnected with an ODBC error and have to close the client then reconnect
to the server. The frequency is pretty sparatic sometimes it can occur 5
times and hour or as little as 1 time an hour. Attached is a copy of one of
the error we get if anyone has any ideas as to what could be causing this I
would greatly appreciate it.
ConnectionWrite (WrapperWrite()).
Last SQL String:
select MRecordID from HEATMsg where MTo='Frank' and MStatus='U' and
MType='M' and MDateTime<=1124822591
Last ODBC Command:
Function: SQLPrepare('select MRecordID from HEATMsg where MTo='Frank' and
MStatus='U' and MType='M' and MDateTime<=1124822591'It's pretty hard to say from what's posted. This looks like
it's a HEAT database. If that's the case, Tracing their
sporadic errors with ODBC tracing will slow things down
quite a bit. You can but it's pretty bad on performance. Try
contacting the vendor, Front Range Solutions. That's
generally quicker.
-Sue
On Tue, 23 Aug 2005 12:33:04 -0700, "Anthony"
<Anthony@.discussions.microsoft.com> wrote:

>I keep getting an ODBC error (varies) I have SQL 7 on Windows 2000 server
>with all the updated service packs and patches for the OS and SQL. I also
>updated MDAC to 2.8 sp2. We use a third party software program that connec
ts
>to the SQL database to store all our data. Every so often we get
>disconnected with an ODBC error and have to close the client then reconnect
>to the server. The frequency is pretty sparatic sometimes it can occur 5
>times and hour or as little as 1 time an hour. Attached is a copy of one o
f
>the error we get if anyone has any ideas as to what could be causing this I
>would greatly appreciate it.
>ConnectionWrite (WrapperWrite()).
>Last SQL String:
>select MRecordID from HEATMsg where MTo='Frank' and MStatus='U' and
>MType='M' and MDateTime<=1124822591
>Last ODBC Command:
>Function: SQLPrepare('select MRecordID from HEATMsg where MTo='Frank' and
>MStatus='U' and MType='M' and MDateTime<=1124822591'
>|||Anthony,
Try using another ODBC tool like WinSQL
(http://www.synametrics.com/winsql) and see if you get the same behavior.
How far is your database from your client? This could also be a network
issue.
Anthony wrote:
> I keep getting an ODBC error (varies) I have SQL 7 on Windows 2000 server
> with all the updated service packs and patches for the OS and SQL. I also
> updated MDAC to 2.8 sp2. We use a third party software program that conne
cts
> to the SQL database to store all our data. Every so often we get
> disconnected with an ODBC error and have to close the client then reconnec
t
> to the server. The frequency is pretty sparatic sometimes it can occur 5
> times and hour or as little as 1 time an hour. Attached is a copy of one
of
> the error we get if anyone has any ideas as to what could be causing this
I
> would greatly appreciate it.
> ConnectionWrite (WrapperWrite()).
> Last SQL String:
> select MRecordID from HEATMsg where MTo='Frank' and MStatus='U' and
> MType='M' and MDateTime<=1124822591
> Last ODBC Command:
> Function: SQLPrepare('select MRecordID from HEATMsg where MTo='Frank' and
> MStatus='U' and MType='M' and MDateTime<=1124822591'
>|||I will look into winsql, thanks. As far as the nework goes everything is in
the same physical location. I have checked network performance and nothing
indicates that it could be a performance problem.
"Dennis Black" wrote:

> Anthony,
> Try using another ODBC tool like WinSQL
> (http://www.synametrics.com/winsql) and see if you get the same behavior.
> How far is your database from your client? This could also be a network
> issue.
>
> Anthony wrote:
>

Error deploying Analysis Service Project

Hi,

We are following the Analysis Service Tutorial and when we tried to deploy we got these errors:

Error 1 OLE DB error: OLE DB or ODBC error: Login failed for user 'PASCAL\CEZAR$'.; 42000. 0 0
Error 2 Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of 'Adventure Works DW', Name of 'Adventure Works DW'. 0 0
Error 3 Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Time', Name of 'Time' was being processed. 0 0
Error 4 Errors in the OLAP storage engine: An error occurred while the 'CalendarYear' attribute of the 'Time' dimension from the 'Analysis Services Project1' database was being processed. 0 0
Error 5 OLE DB error: OLE DB or ODBC error: Login failed for user 'PASCAL\CEZAR$'.; 42000. 0 0
Error 6 Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of 'Adventure Works DW', Name of 'Adventure Works DW'. 0 0
Error 7 Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Time', Name of 'Time' was being processed. 0 0
Error 8 Errors in the OLAP storage engine: An error occurred while the 'CalendarSemester' attribute of the 'Time' dimension from the 'Analysis Services Project1' database was being processed. 0 0

We hope someone can help us.

Thanks a lot.

Hi Cezar. Your problem looks like the user PASCAL\CEZAR$ doesn't have access rights to the SQL Server source data, 'Adventure Works DW'. Check the access rights for 'Adventure Works DW' in SQL Server Manager, and verify that the user PASCAL\CEZAR$ has rights to the database.

Hope this helps - Paul Goldy

|||

Hi,

Thanks for your answer. The user error has been solved, but we got other error messages:

Error 1 OLE DB error: OLE DB or ODBC error: SELECT permission denied on object 'DimTime', database 'AdventureWorksDW', schema 'dbo'.; 42000. 0 0
Error 2 Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Time', Name of 'Time' was being processed. 0 0
Error 3 Errors in the OLAP storage engine: An error occurred while the 'EnglishMonthName' attribute of the 'Time' dimension from the 'Analysis Services Project1' database was being processed. 0 0
Error 4 OLE DB error: OLE DB or ODBC error: SELECT permission denied on object 'DimTime', database 'AdventureWorksDW', schema 'dbo'.; 42000. 0 0
Error 5 Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Time', Name of 'Time' was being processed. 0 0
Error 6 Errors in the OLAP storage engine: An error occurred while the 'CalendarSemester' attribute of the 'Time' dimension from the 'Analysis Services Project1' database was being processed. 0 0
Error 7 Errors in the high-level relational engine. The database operation was cancelled because of an earlier failure. 0 0
Error 8 Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Time', Name of 'Time' was being processed. 0 0
Error 9 Errors in the OLAP storage engine: An error occurred while the 'CalendarYear' attribute of the 'Time' dimension from the 'Analysis Services Project1' database was being processed. 0 0
Error 10 OLE DB error: OLE DB or ODBC error: Opera??o cancelada; HY008. 0 0
Error 11 Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Time', Name of 'Time' was being processed. 0 0
Error 12 Errors in the OLAP storage engine: An error occurred while the 'CalendarQuarter' attribute of the 'Time' dimension from the 'Analysis Services Project1' database was being processed. 0 0

What can we do?

Yours, Cezar

|||

Hi Cezar. The error you received, "SELECT permission denied on object 'DimTime', database 'AdventureWorksDW', schema 'dbo'.; 42000. 0 0", is saying you do NOT have read permission for the AdventureWorksDW database. In SQL manager 2005 you must manage the permission for the AdventureWorksDW database and allow the user (I assume CEZAR\PASCAL$) db_datareader permission for the database. Here is a link which discusses more about setting permissions for SQL Server:

http://msdn2.microsoft.com/en-us/library/ms189121.aspx

Paul Goldy

Error deploying a CLR Stored Procedure that uses a web service

Ok, first some background.

I am writing my first (complex) CLR Stored Procedure using Visual Studio 2005.

This SP worked fine until I added code to make a web service call. That web service is a wrapper web service I created because the actual web service I need to call uses System. Web.Extensions which was not available in my VS2005 Database Project.

At first I was getting the standard "External Access Assembly" errors, so I created a new user (was using SA) and assigned database ownership to the new user, then assigned permissions to that user. This worked to get it deployed, but I get the following error when its run:

<code>

System.InvalidOperationException: Cannot load dynamically generated serialization assembly. In some hosting environments assembly load functionality is restricted, consider using pre-generated serializer. Please see inner exception for more information. > System.IO.FileLoadException: LoadFrom(), LoadFile(), Load(byte[]) and LoadModule() have been disabled by the host.

System.IO.FileLoadException:

at System.Reflection.Assembly.nLoadImage(Byte[] rawAssembly, Byte[] rawSymbolStore, Evidence evidence, StackCrawlMark& stackMark, Boolean fIntrospection)

at System.Reflection.Assembly.Load(Byte[] rawAssembly, Byte[] rawSymbolStore, Evidence securityEvidence)

at Microsoft.CSharp.CSharpCodeGenerator.FromFileBatch(CompilerParameters options, String[] fileNames)

at Microsoft.CSharp.CSharpCodeGenerator.FromSourceBatch(CompilerParameters options, String[] sources)

at Microsoft.CSharp.CSharpCodeGenerator.System.CodeDom.Compiler.ICodeCompiler.CompileAssemblyFromSourceBatch(CompilerParameters options, String[] sources)

at System.CodeDom.Compiler.CodeDomProvider.CompileAssemblyFromSource(CompilerParameters options, S

</code>

Anyone have any ideas?

Thanks!

Dave Borneman

Solution Architect,

anyWare Mobile Solutions.

OK, so when you are using Web services the .NET framework will dynamically generate an assembly based on your proxy code. Dynamic assembly generation is not allowed inside SQL Server (SQLCLR).

What you need to do is to pre-generate the proxy assembly by using the sgen tool and deploy that generated assembly into the database.

Look at this thread: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=74480&SiteID=1 and specifically the 6:th message in that thread how to achieve the pre-generation.

Niels

Error Creating a new cluster on windows 2003 Server EE SP1

Hi,
I'm trying to install cluster service on a Windows 2003 Server Enterprise
Edition SP1.
I've configured Network and Disk.
When I try to create a new a new cluster for the first node, I receive this
error:
Found an existing cluster or node with the name "pippo.mydomain.com". Choose
another name.
A cluster cannot be created with the specified cluster name because that
cluster name is already in use. Specify a different name for the cluster.
I try to change netbios name but it does nothing.(NETBIOS name pippo does
not exsist in mydomain.....i try to use net view \\pippo)
Can You help Me ?
Tank you.
Have you tried to create this cluster before? Chances are that you still
have a DNS entry that needs to be flushed. All Address and Pointer records
for this host/IP address combination need to be flushed before you try and
reinstall.
Sincerely,
Anthony Thomas

"AS" <AS@.discussions.microsoft.com> wrote in message
news:7E9BC8F9-AA47-4D21-B7CF-71E876B9E6F1@.microsoft.com...
Hi,
I'm trying to install cluster service on a Windows 2003 Server Enterprise
Edition SP1.
I've configured Network and Disk.
When I try to create a new a new cluster for the first node, I receive this
error:
Found an existing cluster or node with the name "pippo.mydomain.com". Choose
another name.
A cluster cannot be created with the specified cluster name because that
cluster name is already in use. Specify a different name for the cluster.
I try to change netbios name but it does nothing.(NETBIOS name pippo does
not exsist in mydomain.....i try to use net view \\pippo)
Can You help Me ?
Tank you.

Error connecting to SQL server

Hi,

We have a Windows 2000 terminal server with service pack 4 loaded.This has siebel application 7.8.2 .

We have another Windows 2003 standard edition server with service pack 1. This has SQL 2000 server with Service pack 4 installed.

When trying to connect to the sql server through odbc , i get an error

Microsoft SQL Server Login

Connection failed:
SQLState: '01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.

OK

-I am able to ping the server and viceversa.

Please let me know how to resolve this problem

Then you either have a different port than 1433 (you will have to specify the portnumber after the instance / servername with the syntax --> default instance Servername,Portnumber ; Servername\InstanceName,Portnumber for named instances). Do you have a firewall installed ? Then you will have to check if the appropiate port for SQL are enabled.

HTH, jens Suessmeyer.

http://www.sqlserver2005.de|||

Please follow the instruction and give us more details:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=362498&SiteID=1

|||

Hi

The port is configured to 1433

There is no firewall installed

does it happen due to ODBC version.?

|||

the issue is most likely that you are using terminal server and the odbc is a user odbc, and not a system odbc. if system odbc has not been created for the connection that is having the issue, create it.

ping uses icmp, and not always best test. test the odbc, recreate it if necessary. to check the 1433 port, open telnet client and type in telnet:1433; if it opens, the port is open, otherwise you know it's closed.

also check that the db is using the 1433 port (could have been configured to use alternate).

btw- i don't think siebel 7.8.2 is supported on 2000 server

Error connecting to SQL server

Hi,

We have a Windows 2000 terminal server with service pack 4 loaded.This has siebel application 7.8.2 .

We have another Windows 2003 standard edition server with service pack 1. This has SQL 2000 server with Service pack 4 installed.

When trying to connect to the sql server through odbc , i get an error

Microsoft SQL Server Login

Connection failed:
SQLState: '01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.

OK

-I am able to ping the server and viceversa.

Please let me know how to resolve this problem

Then you either have a different port than 1433 (you will have to specify the portnumber after the instance / servername with the syntax --> default instance Servername,Portnumber ; Servername\InstanceName,Portnumber for named instances). Do you have a firewall installed ? Then you will have to check if the appropiate port for SQL are enabled.

HTH, jens Suessmeyer.

http://www.sqlserver2005.de
|||

Please follow the instruction and give us more details:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=362498&SiteID=1

|||

Hi

The port is configured to 1433

There is no firewall installed

does it happen due to ODBC version.?

|||

the issue is most likely that you are using terminal server and the odbc is a user odbc, and not a system odbc. if system odbc has not been created for the connection that is having the issue, create it.

ping uses icmp, and not always best test. test the odbc, recreate it if necessary. to check the 1433 port, open telnet client and type in telnet:1433; if it opens, the port is open, otherwise you know it's closed.

also check that the db is using the 1433 port (could have been configured to use alternate).

btw- i don't think siebel 7.8.2 is supported on 2000 server

Error connecting Excel to Analysis Service for browsing cube

I have created a cube. Now when I open excel so that to browse the cube in the excel pivot table i am getting connection refused error? I am using olap 9.0 to connect to my cube which is deployed on the sqlserver 2005 analysis server. server is up and running.ok i found the solution. we need to reregister the olap 9.0 provider before we can use it to connect SQL Server 2005 Analysis Service Cube with Excel Pivot Table :
regsvr32 "c:\program files\common files\system\ole db\msolap90.dll"|||

Hi,

I having the similar problem with you. But no sure whether your error message is same with me. Here i get the error message as below:

Connection Failed

SQL State: '28000'

SQL Server Error: 18456

[Microsoft][ODBC SQL Server][SQL Server] Login failed for user 'domain\userida'

I am using olap services 8.0 & sqlserver 2000.

I checked this userida is properly created in the cube under a cube role said 'Accounts'. This role contain of abt 6 user id. Others user id is work fine except for this userida.

Any ideas to solve this issue.

Thanks in advance.

Error Code 2259 applying SQL2005 service pack

I have SQL 2005 Express installed. When I try to apply service pack 1 to this by going through the upgrade process, I get an error ' THe installer has encountered an unexpected error. The error code is 2259. Table(s) update failed'

Any ideas? Help!

Ranjit Charles

Ranjit, are you trying to run the Express SP1 refresh package or the full SP1 installer?

Thanks,
Sam Lester (MSFT)

|||

Sam,

I was using the full SP1 installer. I couldn't really find the SP1 refresh ..

Ranjit

|||

Ah, OK. That should be the issue. If you go to the SP1 page at http://www.microsoft.com/downloads/details.aspx?FamilyID=cb6c71ea-d649-47ff-9176-e7cac58fd4bc&DisplayLang=en

It has a link midway down the page for the Express upgrades. Here's a snippet...

Overview

Service Pack 1 for Microsoft SQL Server 2005 is now available. You can use these packages to upgrade any of the following SQL Server 2005 editions:

Enterprise Enterprise Evaluation Developer Standard Workgroup

error code 17058

Hi everyone. I installed SP1 and it required a reboot. When I attempted to
start the
service from the Management Studio it fails and indicates an instance
failure (system.data). When I attempt to start from the administrative
services control
it fails and indicates a 17058 error, but the search results indicate this
is associated
with sql2000. The directory indicates the system files are there. I have
current
backups of system and data files. Anything I can do short of a complete
reload?
Thanks to everyone for being there to help.
SQL2005 and almost SP1
EdHi!
> Hi everyone. I installed SP1 and it required a reboot. When I attempted to
> start the
> service from the Management Studio it fails and indicates an instance
> failure (system.data). When I attempt to start from the administrative
> services control
> it fails and indicates a 17058 error, but the search results indicate this
> is associated
> with sql2000. The directory indicates the system files are there. I have
> current
> backups of system and data files. Anything I can do short of a complete
> reload?
> Thanks to everyone for being there to help.
> SQL2005 and almost SP1
This can be SQL 2005 error as well - check, for example
http://groups.google.si/group/microsoft.public.sqlserver.server/browse_thread/thread/fd5cb2a8c242612a/c33f0483c5587bdf?lnk=st&q=17058+sql+server+error&rnum=1&hl=sl#c33f0483c5587bdf.
If this is what you get, you should not use Network Service account for the
SQL Server service.
--
Dejan Sarka, SQL Server MVP
Mentor, www.SolidQualityLearning.com
Anything written in this message represents solely the point of view of the
sender.
This message does not imply endorsement from Solid Quality Learning, and it
does not represent the point of view of Solid Quality Learning or any other
person, company or institution mentioned in this message

Error attempting to add server to Active Directory

While attempting to add a SQL Server to the Active Directory, I
received an error stating that the MSSQLServerADHelper service could
not be started. The service is set to manual startup. When I attempt
to start the service myself, I get the following error that I cannot
find any information on in the KB:
The MSSQLServerADHelp service terminated with the service-specific
error 3221225572.
Also searched for $C0000064 in hopes that the error was listed in hex,
to no avail.
Any ideas what the problem is?
Thanks,
Brandon
--
"In the beginning the universe was created. This has made a lot of
people very angry, and has been widely regarded as a bad move." -
Douglas Noel Adams (1952-2001)Issue appears to be related to security. I changed the SQLServer and
SQLAgent startup account to administrator and tried again, and it
successfully added itself to AD through Enterprise Manager.
I think the security for the old security account is messed up. I am
going to remove it and try again.
Brandon
--
"In the beginning the universe was created. This has made a lot of
people very angry, and has been widely regarded as a bad move." -
Douglas Noel Adams (1952-2001)|||please refer to:
http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/architec/8_ar_cs_9mhx.asp
this behaviour is by design, you cannot start
MSSQLServerADHelp service manually, it is started by sql
server or analyis services whenever needed and then stopes
it when done.
Make sure the start up account for MSSQLServerADHelp is
Local System, and also that the server is member of a AD
domain. and sql server service start up account should
have permission to start MSSQLServerADHelp service.
>--Original Message--
>While attempting to add a SQL Server to the Active
Directory, I
>received an error stating that the MSSQLServerADHelper
service could
>not be started. The service is set to manual startup.
When I attempt
>to start the service myself, I get the following error
that I cannot
>find any information on in the KB:
>The MSSQLServerADHelp service terminated with the service-
specific
>error 3221225572.
>Also searched for $C0000064 in hopes that the error was
listed in hex,
>to no avail.
>Any ideas what the problem is?
>Thanks,
>Brandon
>--
>"In the beginning the universe was created. This has
made a lot of
>people very angry, and has been widely regarded as a bad
move." -
>Douglas Noel Adams (1952-2001)
>
>.
>

Error After SQL Server 2005 SP1

SQL Server 2005 SP1 Build 2153 Developer Edition on Windows 2003 Server SP1
When I start the SQL Server service I get:
[298] SQL Server Error: 2812, Could not find stored procedure
'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
Any ideas?
Thanks,
Bryansp1 build is 2047. you must have installed the post sp1 hotfix rollup.
please follow http://support.microsoft.com/Default.aspx?id=918222 to ensure
you have properly install the hotfix in the specified order.
-oj
"BDB" <bdb@.reply.to.group.com> wrote in message
news:%23xzEM2IkGHA.3780@.TK2MSFTNGP03.phx.gbl...
> SQL Server 2005 SP1 Build 2153 Developer Edition on Windows 2003 Server
> SP1
>
> When I start the SQL Server service I get:
> [298] SQL Server Error: 2812, Could not find stored procedure
> 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
>
> Any ideas?
> Thanks,
> Bryan
>|||sp1 build is 2047. you must have installed the post sp1 hotfix rollup.
please follow http://support.microsoft.com/Default.aspx?id=918222 to ensure
you have properly install the hotfix in the specified order.
-oj
"BDB" <bdb@.reply.to.group.com> wrote in message
news:%23xzEM2IkGHA.3780@.TK2MSFTNGP03.phx.gbl...
> SQL Server 2005 SP1 Build 2153 Developer Edition on Windows 2003 Server
> SP1
>
> When I start the SQL Server service I get:
> [298] SQL Server Error: 2812, Could not find stored procedure
> 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
>
> Any ideas?
> Thanks,
> Bryan
>|||Hi, Thank you for your post.
We were aware and followed KB918222 prior to bringing the build to 2153. It
does not appear to be related.
"oj" <nospam_ojngo@.home.com> wrote in message
news:%233htVgRkGHA.4304@.TK2MSFTNGP03.phx.gbl...[vbcol=seagreen]
> sp1 build is 2047. you must have installed the post sp1 hotfix rollup.
> please follow http://support.microsoft.com/Default.aspx?id=918222 to
> ensure you have properly install the hotfix in the specified order.
> --
> -oj
> "BDB" <bdb@.reply.to.group.com> wrote in message
> news:%23xzEM2IkGHA.3780@.TK2MSFTNGP03.phx.gbl...|||Take a closer look at msdb..sp_sqlagent_notify stored procedure. The
execution line should be:
EXECUTE @.retval = master.dbo.xp_sqlagent_notify @.op_type, @.job_id,
@.schedule_id, @.alert_id, @.action_type, @.nt_user_name, @.error_flag,
@.@.trancount, @.wmi_namespace, @.wmi_query
-oj
"BDB" <bdb@.reply.to.group.com> wrote in message
news:%23sVMFlVkGHA.5108@.TK2MSFTNGP02.phx.gbl...
> Hi, Thank you for your post.
> We were aware and followed KB918222 prior to bringing the build to 2153.
> It does not appear to be related.
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:%233htVgRkGHA.4304@.TK2MSFTNGP03.phx.gbl...
>|||Hi, Thank you for your post.
We were aware and followed KB918222 prior to bringing the build to 2153. It
does not appear to be related.
"oj" <nospam_ojngo@.home.com> wrote in message
news:%233htVgRkGHA.4304@.TK2MSFTNGP03.phx.gbl...[vbcol=seagreen]
> sp1 build is 2047. you must have installed the post sp1 hotfix rollup.
> please follow http://support.microsoft.com/Default.aspx?id=918222 to
> ensure you have properly install the hotfix in the specified order.
> --
> -oj
> "BDB" <bdb@.reply.to.group.com> wrote in message
> news:%23xzEM2IkGHA.3780@.TK2MSFTNGP03.phx.gbl...|||Take a closer look at msdb..sp_sqlagent_notify stored procedure. The
execution line should be:
EXECUTE @.retval = master.dbo.xp_sqlagent_notify @.op_type, @.job_id,
@.schedule_id, @.alert_id, @.action_type, @.nt_user_name, @.error_flag,
@.@.trancount, @.wmi_namespace, @.wmi_query
-oj
"BDB" <bdb@.reply.to.group.com> wrote in message
news:%23sVMFlVkGHA.5108@.TK2MSFTNGP02.phx.gbl...
> Hi, Thank you for your post.
> We were aware and followed KB918222 prior to bringing the build to 2153.
> It does not appear to be related.
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:%233htVgRkGHA.4304@.TK2MSFTNGP03.phx.gbl...
>|||Hi, Thanks for following up! On inspection of msdb.dbo.sp_sqlagent_notify
source the calling semantics of master.dbo.xp_sqlagent_notify are the same
as what you specified.
"oj" <nospam_ojngo@.home.com> wrote in message
news:uJB6qmWkGHA.3588@.TK2MSFTNGP02.phx.gbl...[vbcol=seagreen]
> Take a closer look at msdb..sp_sqlagent_notify stored procedure. The
> execution line should be:
> EXECUTE @.retval = master.dbo.xp_sqlagent_notify @.op_type, @.job_id,
> @.schedule_id, @.alert_id, @.action_type, @.nt_user_name, @.error_flag,
> @.@.trancount, @.wmi_namespace, @.wmi_query
> --
> -oj
> "BDB" <bdb@.reply.to.group.com> wrote in message
> news:%23sVMFlVkGHA.5108@.TK2MSFTNGP02.phx.gbl...|||Hi, Thanks for following up! On inspection of msdb.dbo.sp_sqlagent_notify
source the calling semantics of master.dbo.xp_sqlagent_notify are the same
as what you specified.
"oj" <nospam_ojngo@.home.com> wrote in message
news:uJB6qmWkGHA.3588@.TK2MSFTNGP02.phx.gbl...[vbcol=seagreen]
> Take a closer look at msdb..sp_sqlagent_notify stored procedure. The
> execution line should be:
> EXECUTE @.retval = master.dbo.xp_sqlagent_notify @.op_type, @.job_id,
> @.schedule_id, @.alert_id, @.action_type, @.nt_user_name, @.error_flag,
> @.@.trancount, @.wmi_namespace, @.wmi_query
> --
> -oj
> "BDB" <bdb@.reply.to.group.com> wrote in message
> news:%23sVMFlVkGHA.5108@.TK2MSFTNGP02.phx.gbl...|||there must be a process/procedure that calls 'msdb.dbo.xp_sqlagent_notify'.
run this to see if anything returns.
exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from
?.sys.sql_modules where definition like '%msdb.dbo.xp_sqlagent_notify%'"
-oj
"BDB" <bdb@.reply.to.group.com> wrote in message
news:uFvh$UXkGHA.2200@.TK2MSFTNGP05.phx.gbl...
> Hi, Thanks for following up! On inspection of
> msdb.dbo.sp_sqlagent_notify source the calling semantics of
> master.dbo.xp_sqlagent_notify are the same as what you specified.
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:uJB6qmWkGHA.3588@.TK2MSFTNGP02.phx.gbl...
>

Error After SQL Server 2005 SP1

SQL Server 2005 SP1 Build 2153 Developer Edition on Windows 2003 Server SP1
When I start the SQL Server service I get:
[298] SQL Server Error: 2812, Could not find stored procedure
'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
Any ideas?
Thanks,
Bryansp1 build is 2047. you must have installed the post sp1 hotfix rollup.
please follow http://support.microsoft.com/Default.aspx?id=918222 to ensure
you have properly install the hotfix in the specified order.
--
-oj
"BDB" <bdb@.reply.to.group.com> wrote in message
news:%23xzEM2IkGHA.3780@.TK2MSFTNGP03.phx.gbl...
> SQL Server 2005 SP1 Build 2153 Developer Edition on Windows 2003 Server
> SP1
>
> When I start the SQL Server service I get:
> [298] SQL Server Error: 2812, Could not find stored procedure
> 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
>
> Any ideas?
> Thanks,
> Bryan
>|||Hi, Thank you for your post.
We were aware and followed KB918222 prior to bringing the build to 2153. It
does not appear to be related.
"oj" <nospam_ojngo@.home.com> wrote in message
news:%233htVgRkGHA.4304@.TK2MSFTNGP03.phx.gbl...
> sp1 build is 2047. you must have installed the post sp1 hotfix rollup.
> please follow http://support.microsoft.com/Default.aspx?id=918222 to
> ensure you have properly install the hotfix in the specified order.
> --
> -oj
> "BDB" <bdb@.reply.to.group.com> wrote in message
> news:%23xzEM2IkGHA.3780@.TK2MSFTNGP03.phx.gbl...
>> SQL Server 2005 SP1 Build 2153 Developer Edition on Windows 2003 Server
>> SP1
>> When I start the SQL Server service I get:
>> [298] SQL Server Error: 2812, Could not find stored procedure
>> 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
>>
>> Any ideas?
>> Thanks,
>> Bryan|||Take a closer look at msdb..sp_sqlagent_notify stored procedure. The
execution line should be:
EXECUTE @.retval = master.dbo.xp_sqlagent_notify @.op_type, @.job_id,
@.schedule_id, @.alert_id, @.action_type, @.nt_user_name, @.error_flag,
@.@.trancount, @.wmi_namespace, @.wmi_query
-oj
"BDB" <bdb@.reply.to.group.com> wrote in message
news:%23sVMFlVkGHA.5108@.TK2MSFTNGP02.phx.gbl...
> Hi, Thank you for your post.
> We were aware and followed KB918222 prior to bringing the build to 2153.
> It does not appear to be related.
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:%233htVgRkGHA.4304@.TK2MSFTNGP03.phx.gbl...
>> sp1 build is 2047. you must have installed the post sp1 hotfix rollup.
>> please follow http://support.microsoft.com/Default.aspx?id=918222 to
>> ensure you have properly install the hotfix in the specified order.
>> --
>> -oj
>> "BDB" <bdb@.reply.to.group.com> wrote in message
>> news:%23xzEM2IkGHA.3780@.TK2MSFTNGP03.phx.gbl...
>> SQL Server 2005 SP1 Build 2153 Developer Edition on Windows 2003 Server
>> SP1
>> When I start the SQL Server service I get:
>> [298] SQL Server Error: 2812, Could not find stored procedure
>> 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
>>
>> Any ideas?
>> Thanks,
>> Bryan
>|||Hi, Thanks for following up! On inspection of msdb.dbo.sp_sqlagent_notify
source the calling semantics of master.dbo.xp_sqlagent_notify are the same
as what you specified.
"oj" <nospam_ojngo@.home.com> wrote in message
news:uJB6qmWkGHA.3588@.TK2MSFTNGP02.phx.gbl...
> Take a closer look at msdb..sp_sqlagent_notify stored procedure. The
> execution line should be:
> EXECUTE @.retval = master.dbo.xp_sqlagent_notify @.op_type, @.job_id,
> @.schedule_id, @.alert_id, @.action_type, @.nt_user_name, @.error_flag,
> @.@.trancount, @.wmi_namespace, @.wmi_query
> --
> -oj
> "BDB" <bdb@.reply.to.group.com> wrote in message
> news:%23sVMFlVkGHA.5108@.TK2MSFTNGP02.phx.gbl...
>> Hi, Thank you for your post.
>> We were aware and followed KB918222 prior to bringing the build to 2153.
>> It does not appear to be related.
>> "oj" <nospam_ojngo@.home.com> wrote in message
>> news:%233htVgRkGHA.4304@.TK2MSFTNGP03.phx.gbl...
>> sp1 build is 2047. you must have installed the post sp1 hotfix rollup.
>> please follow http://support.microsoft.com/Default.aspx?id=918222 to
>> ensure you have properly install the hotfix in the specified order.
>> --
>> -oj
>> "BDB" <bdb@.reply.to.group.com> wrote in message
>> news:%23xzEM2IkGHA.3780@.TK2MSFTNGP03.phx.gbl...
>> SQL Server 2005 SP1 Build 2153 Developer Edition on Windows 2003 Server
>> SP1
>> When I start the SQL Server service I get:
>> [298] SQL Server Error: 2812, Could not find stored procedure
>> 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
>>
>> Any ideas?
>> Thanks,
>> Bryan|||there must be a process/procedure that calls 'msdb.dbo.xp_sqlagent_notify'.
run this to see if anything returns.
exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from
?.sys.sql_modules where definition like '%msdb.dbo.xp_sqlagent_notify%'"
-oj
"BDB" <bdb@.reply.to.group.com> wrote in message
news:uFvh$UXkGHA.2200@.TK2MSFTNGP05.phx.gbl...
> Hi, Thanks for following up! On inspection of
> msdb.dbo.sp_sqlagent_notify source the calling semantics of
> master.dbo.xp_sqlagent_notify are the same as what you specified.
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:uJB6qmWkGHA.3588@.TK2MSFTNGP02.phx.gbl...
>> Take a closer look at msdb..sp_sqlagent_notify stored procedure. The
>> execution line should be:
>> EXECUTE @.retval = master.dbo.xp_sqlagent_notify @.op_type, @.job_id,
>> @.schedule_id, @.alert_id, @.action_type, @.nt_user_name, @.error_flag,
>> @.@.trancount, @.wmi_namespace, @.wmi_query
>> --
>> -oj
>> "BDB" <bdb@.reply.to.group.com> wrote in message
>> news:%23sVMFlVkGHA.5108@.TK2MSFTNGP02.phx.gbl...
>> Hi, Thank you for your post.
>> We were aware and followed KB918222 prior to bringing the build to 2153.
>> It does not appear to be related.
>> "oj" <nospam_ojngo@.home.com> wrote in message
>> news:%233htVgRkGHA.4304@.TK2MSFTNGP03.phx.gbl...
>> sp1 build is 2047. you must have installed the post sp1 hotfix rollup.
>> please follow http://support.microsoft.com/Default.aspx?id=918222 to
>> ensure you have properly install the hotfix in the specified order.
>> --
>> -oj
>> "BDB" <bdb@.reply.to.group.com> wrote in message
>> news:%23xzEM2IkGHA.3780@.TK2MSFTNGP03.phx.gbl...
>> SQL Server 2005 SP1 Build 2153 Developer Edition on Windows 2003
>> Server SP1
>> When I start the SQL Server service I get:
>> [298] SQL Server Error: 2812, Could not find stored procedure
>> 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
>>
>> Any ideas?
>> Thanks,
>> Bryan
>|||Okay, I ran this and I found no references. I think what might be happening
is that xp_sqlagent_notify is called in the wrong database context. So the
intention is that it is called in master but is instead called in msdb.
However, when I search for just xp_sqlagent_notify, it is only called from
msdb..sp_delete_job
and msdb..sp_sqlagent_notify. BTW, clever code!
"oj" <nospam_ojngo@.home.com> wrote in message
news:OiAGECekGHA.4044@.TK2MSFTNGP03.phx.gbl...
> there must be a process/procedure that calls
> 'msdb.dbo.xp_sqlagent_notify'.
> run this to see if anything returns.
> exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n
> from ?.sys.sql_modules where definition like
> '%msdb.dbo.xp_sqlagent_notify%'"
> --
> -oj
> "BDB" <bdb@.reply.to.group.com> wrote in message
> news:uFvh$UXkGHA.2200@.TK2MSFTNGP05.phx.gbl...
>> Hi, Thanks for following up! On inspection of
>> msdb.dbo.sp_sqlagent_notify source the calling semantics of
>> master.dbo.xp_sqlagent_notify are the same as what you specified.
>> "oj" <nospam_ojngo@.home.com> wrote in message
>> news:uJB6qmWkGHA.3588@.TK2MSFTNGP02.phx.gbl...
>> Take a closer look at msdb..sp_sqlagent_notify stored procedure. The
>> execution line should be:
>> EXECUTE @.retval = master.dbo.xp_sqlagent_notify @.op_type, @.job_id,
>> @.schedule_id, @.alert_id, @.action_type, @.nt_user_name, @.error_flag,
>> @.@.trancount, @.wmi_namespace, @.wmi_query
>> --
>> -oj
>> "BDB" <bdb@.reply.to.group.com> wrote in message
>> news:%23sVMFlVkGHA.5108@.TK2MSFTNGP02.phx.gbl...
>> Hi, Thank you for your post.
>> We were aware and followed KB918222 prior to bringing the build to
>> 2153. It does not appear to be related.
>> "oj" <nospam_ojngo@.home.com> wrote in message
>> news:%233htVgRkGHA.4304@.TK2MSFTNGP03.phx.gbl...
>> sp1 build is 2047. you must have installed the post sp1 hotfix rollup.
>> please follow http://support.microsoft.com/Default.aspx?id=918222 to
>> ensure you have properly install the hotfix in the specified order.
>> --
>> -oj
>> "BDB" <bdb@.reply.to.group.com> wrote in message
>> news:%23xzEM2IkGHA.3780@.TK2MSFTNGP03.phx.gbl...
>> SQL Server 2005 SP1 Build 2153 Developer Edition on Windows 2003
>> Server SP1
>> When I start the SQL Server service I get:
>> [298] SQL Server Error: 2812, Could not find stored procedure
>> 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
>>
>> Any ideas?
>> Thanks,
>> Bryan
>>
>|||hmm...something must be calling this. there is definitely a bug here (if
it's not user code, then it's probably ms) because it references the wrong
database.
-oj
"BDB" <bdb@.reply.to.group.com> wrote in message
news:uDaA$76kGHA.3304@.TK2MSFTNGP03.phx.gbl...
> Okay, I ran this and I found no references. I think what might be
> happening is that xp_sqlagent_notify is called in the wrong database
> context. So the intention is that it is called in master but is instead
> called in msdb. However, when I search for just xp_sqlagent_notify, it is
> only called from msdb..sp_delete_job
> and msdb..sp_sqlagent_notify. BTW, clever code!
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:OiAGECekGHA.4044@.TK2MSFTNGP03.phx.gbl...
>> there must be a process/procedure that calls
>> 'msdb.dbo.xp_sqlagent_notify'.
>> run this to see if anything returns.
>> exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n
>> from ?.sys.sql_modules where definition like
>> '%msdb.dbo.xp_sqlagent_notify%'"
>> --
>> -oj|||look like it's ms bug.
"Ciprian Gerea [MSFT]" <Ciprian.Gerea@.online.microsoft.com> wrote in message
news:%23kozju%23kGHA.1244@.TK2MSFTNGP05.phx.gbl...
> Hi Adrian,
> The error about the call to xp_sqlagent_notify is a benign startup error,
> and we're looking at fixing it for the next service pack. Without more
> information I can't tell why agent is failing, but I believe that the job
> history error that you're mentioning might give us a clue.
-oj
"oj" <nospam_ojngo@.home.com> wrote in message
news:%23eUC$ODlGHA.4200@.TK2MSFTNGP05.phx.gbl...
> hmm...something must be calling this. there is definitely a bug here (if
> it's not user code, then it's probably ms) because it references the wrong
> database.
>
> --
> -oj
>
> "BDB" <bdb@.reply.to.group.com> wrote in message
> news:uDaA$76kGHA.3304@.TK2MSFTNGP03.phx.gbl...
>> Okay, I ran this and I found no references. I think what might be
>> happening is that xp_sqlagent_notify is called in the wrong database
>> context. So the intention is that it is called in master but is instead
>> called in msdb. However, when I search for just xp_sqlagent_notify, it is
>> only called from msdb..sp_delete_job
>> and msdb..sp_sqlagent_notify. BTW, clever code!
>> "oj" <nospam_ojngo@.home.com> wrote in message
>> news:OiAGECekGHA.4044@.TK2MSFTNGP03.phx.gbl...
>> there must be a process/procedure that calls
>> 'msdb.dbo.xp_sqlagent_notify'.
>> run this to see if anything returns.
>> exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n
>> from ?.sys.sql_modules where definition like
>> '%msdb.dbo.xp_sqlagent_notify%'"
>> --
>> -oj
>|||Thanks so much for your help!
"oj" <nospam_ojngo@.home.com> wrote in message
news:%23as6ORDlGHA.1320@.TK2MSFTNGP04.phx.gbl...
> look like it's ms bug.
> "Ciprian Gerea [MSFT]" <Ciprian.Gerea@.online.microsoft.com> wrote in
> message news:%23kozju%23kGHA.1244@.TK2MSFTNGP05.phx.gbl...
>> Hi Adrian,
>> The error about the call to xp_sqlagent_notify is a benign startup error,
>> and we're looking at fixing it for the next service pack. Without more
>> information I can't tell why agent is failing, but I believe that the job
>> history error that you're mentioning might give us a clue.
>
> --
> -oj
>
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:%23eUC$ODlGHA.4200@.TK2MSFTNGP05.phx.gbl...
>> hmm...something must be calling this. there is definitely a bug here (if
>> it's not user code, then it's probably ms) because it references the
>> wrong database.
>>
>> --
>> -oj
>>
>> "BDB" <bdb@.reply.to.group.com> wrote in message
>> news:uDaA$76kGHA.3304@.TK2MSFTNGP03.phx.gbl...
>> Okay, I ran this and I found no references. I think what might be
>> happening is that xp_sqlagent_notify is called in the wrong database
>> context. So the intention is that it is called in master but is instead
>> called in msdb. However, when I search for just xp_sqlagent_notify, it
>> is only called from msdb..sp_delete_job
>> and msdb..sp_sqlagent_notify. BTW, clever code!
>> "oj" <nospam_ojngo@.home.com> wrote in message
>> news:OiAGECekGHA.4044@.TK2MSFTNGP03.phx.gbl...
>> there must be a process/procedure that calls
>> 'msdb.dbo.xp_sqlagent_notify'.
>> run this to see if anything returns.
>> exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n
>> from ?.sys.sql_modules where definition like
>> '%msdb.dbo.xp_sqlagent_notify%'"
>> --
>> -oj
>>
>

Error after service account removed from "SQLServer2005MSSQLUser" Group

I am attempting to configure my SQL Server instance to use a service account with the minimum privileges. I thought I had everything configured correctly, when I realized that having the service account as a member of the "SQLServer2005MSSQLUser" Windows Group meant that the service account was now in the "sysadmin" fixed server role. This was not the configuration I wanted.

I went through the Books Online article "Setting Up Windows Service Accounts" and made sure the login had access to the appropriate folders used by SQL Server. Then I stopped the SQL Server service and tried to restart it, without success. These are the error messages:

Code Snippet

SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.

FCB::Open failed: Could not open file E:\MSSQL$STAGING\Data\model.mdf for file number 1. OS error: 5(Access is denied.).

TDSSNIClient initialization failed with error 0x5, status code 0x1.

TDSSNIClient initialization failed with error 0x5, status code 0x90.

I checked some other posts on this board, and they suggested the problem might be that the "VIA" protocol was enabled. I checked for this protocol in the Configuration Manager, and it is DISABLED in both the SQL Server 2005 Network Configuration and the SQL Native Client Configuration. What else could be causing this error?

The errors do not occur when I add the service account back to the "SQLServer2005MSSQLUser" Windows Group. The SQL Server service starts successfully when the account is back in this group.

Here are my answers to the questions posted at the top of this board:

What is the MS SQL version? - SQL Server 2005 SP2 (9.00.3054.00)

What is the SKU of MS SQL? - Enterprise Edition (SKU ID: 1804890536)

What is the SQL Server Protocol enabled? - TCPIP, Named Pipes

Does the server start successfully? - NO

If not what is the error messages in the SQL server ERRORLOG? - See above.

If SQL Server is a named instance, is the SQL browser enabled? - YES

What is the account that the SQL Server is running under? - Domain Account

Do you make firewall exception for your SQL server TCP port if you want connect remotely through TCP provider? Not applicable, Windows Firewall is not used

Do you make firewall exception for SQL Browser UDP port 1434?
Not Applicable, Windows Firewall is not used

Hi Ken,

You seem to be facing multiple problems with the account setup. First of all - make sure you have granted it read/write access to the folders where databases are located (especially the E:\MSSQL$STAGING\Data).

The next thing to do is grant the account access to the registry, in particular [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer] and subfolders + [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server] and subfolders.

The status code of 0x90 above probably indicates the inability of the service to access a registry entry called ProtocolList, it is usually under [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\SuperSocketNetLib], it is for SQL 2k compatibility purposes. What you can do is to capture a RegMon from a service startup attempt (http://www.microsoft.com/technet/sysinternals/utilities/regmon.mspx) and look for access denied entries in it. Based on that you can grant access and go from there. Similar for files - you could use FileMon (http://www.microsoft.com/technet/sysinternals/FileAndDisk/Filemon.mspx).

More information about the initialization failure status codes is available here: http://blogs.msdn.com/sql_protocols/archive/2006/04/28/585835.aspx.

HTH,
Jivko Dobrev - MSFT
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Thank you, I was looking for a way to see the Registry access.

As far as the database files, here are the folders the account has "Full Control" over:

E:\MSSQL$STAGING\MSSQL.4\MSSQL (Stores the files for the system databases)

E:\MSSQL$STAGING\Data (Stores the files for all other databases)

I orginally granted the account "Full Control" at the parent folder (E:\MSSQL$STAGING), but this did not work.

I'll try out your suggestions and post back later.

|||

I'll need some more time to learn how to use regmon. It was returning far too much data to be useful.

I did a search for "SuperSocketNetLib" within the Registry Editor. I found it in the following keys:

Code Snippet

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer\SuperSocketNetLib

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.4\MSSQLServer\SuperSocketNetLib

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\STAGING\MSSQLServer\SuperSocketNetLib

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SuperSocketNetLib

I granted the service account "Full Control" on the first four keys I listed. The account already had "Read" permissions on "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SuperSocketNetLib" due to its membership in the "SQLServerBrowserUser" Windows group.

After making these changes, I was able to start the SQL Server service. Everything appeared to be working until I checked EventViewer. The following error was rapidly filling the Application Log:

Code Snippet

UpdateUptimeRegKey: Operating system error 5(Access is denied.) encountered.

I searched the Registry for both "UpdateUptime" and "UpdateUptimeRegKey" and found nothing. Is this a Registry key or is this something else?

My next step is to grant the service account "Full Control" over the following keys:

Code Snippet

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server (and subfolders)

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer (and subfolders)

You had told me to do this but I hadn't done so.

I'll post back later with additional results.

|||

Granting the service account "Full Control" over "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server (and subfolders)" and "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer (and subfolders)" resolved the errors for "UpdateUptimeRegKey".

I was now able to start the service and keep it running without any further Windows errors. Unfortunately, I now started receiving errors within SQL Server. Two developers were trying to execute a stored procedure. They received the following error:

"An error occurred during decryption"

I did some research, and found out the error refers to the Service Master Key. Once again, the error disappears when I add the service account back to "SQLServer2005MSSQLUser".

Am I going to need to rebuild the master database in order to accomplish this change?

|||

Hi Ken!

In the last few days I've tried to do exactly the same as you. I become a task to audit an MSSQL 2005 Standard server. I realised that the SQL server was originaly intalled to run the service under the Administrator account. So as in many reference, I try to change also the account to use a service account with the minimum privileges. Which is the 'NT AUTHORITY\NetworkService'. After it, I try to start the service and my problems began. I resolved step-by-step the same problems as you. Registry keys permission change, checking folders permissions and so on. Even I must change some settings with the Component Service Manager to let Local Activation for Microsoft Search FTE Admin. Anyway, at the end I still have this error message in the Event Viewer just as you.

So my question is that have you find out how can this error resolved? Or somebody else?

Many thanks!

|||

Actually, I discovered I misunderstood the new security model for SQL Server. My misunderstanding was that I thought that the SQL Server service account should NOT be a member of the "sysadmin" fixed server role. It turns out that the account IS supposed to be a member of "sysadmin". Therefore, the is no reason to remove the service account from the SQLServer2005MSSQLUser" group.

The documentation in SQL Server Books Online needs to be revised to make this clear. When you read the Books Online article "Setting Up Windows Service Accounts", this is what it says in the "Reviewing Windows Permissions for SQL Server Services", in the "Required permissions" column:

Local user is recommended.

Under "Minimum permissions", it says the following:

"The account must be in the list of accounts that have "List Folder" permissions on the root drive where SQL Server is installed, and on the root of any other drive where SQL Server files are stored." and "The account must have "Full Control" permissions over any folders where data or log files (.mdf, .ndf, .ldf) will reside."

There is not one word about the requirement that the account be a sysadmin. By contrast, here is what the same article says about the Minimum permissions for the SQL Server Agent service account:

"The account must be a member of the sysadmin fixed server role."

Maybe Microsoft just assumed that we would know that the service account needed to be a sysadmin.

Microsoft could save us all a lot of headaches if they would include this simple statement with the information for the SQL Server service account.

Error after service account removed from "SQLServer2005MSSQLUser" Group

I am attempting to configure my SQL Server instance to use a service account with the minimum privileges. I thought I had everything configured correctly, when I realized that having the service account as a member of the "SQLServer2005MSSQLUser" Windows Group meant that the service account was now in the "sysadmin" fixed server role. This was not the configuration I wanted.

I went through the Books Online article "Setting Up Windows Service Accounts" and made sure the login had access to the appropriate folders used by SQL Server. Then I stopped the SQL Server service and tried to restart it, without success. These are the error messages:

Code Snippet

SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.

FCB::Open failed: Could not open file E:\MSSQL$STAGING\Data\model.mdf for file number 1. OS error: 5(Access is denied.).

TDSSNIClient initialization failed with error 0x5, status code 0x1.

TDSSNIClient initialization failed with error 0x5, status code 0x90.

I checked some other posts on this board, and they suggested the problem might be that the "VIA" protocol was enabled. I checked for this protocol in the Configuration Manager, and it is DISABLED in both the SQL Server 2005 Network Configuration and the SQL Native Client Configuration. What else could be causing this error?

The errors do not occur when I add the service account back to the "SQLServer2005MSSQLUser" Windows Group. The SQL Server service starts successfully when the account is back in this group.

Here are my answers to the questions posted at the top of this board:

What is the MS SQL version? - SQL Server 2005 SP2 (9.00.3054.00)

What is the SKU of MS SQL? - Enterprise Edition (SKU ID: 1804890536)

What is the SQL Server Protocol enabled? - TCPIP, Named Pipes

Does the server start successfully? - NO

If not what is the error messages in the SQL server ERRORLOG? - See above.

If SQL Server is a named instance, is the SQL browser enabled? - YES

What is the account that the SQL Server is running under? - Domain Account

Do you make firewall exception for your SQL server TCP port if you want connect remotely through TCP provider? Not applicable, Windows Firewall is not used

Do you make firewall exception for SQL Browser UDP port 1434?
Not Applicable, Windows Firewall is not used

Hi Ken,

You seem to be facing multiple problems with the account setup. First of all - make sure you have granted it read/write access to the folders where databases are located (especially the E:\MSSQL$STAGING\Data).

The next thing to do is grant the account access to the registry, in particular [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer] and subfolders + [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server] and subfolders.

The status code of 0x90 above probably indicates the inability of the service to access a registry entry called ProtocolList, it is usually under [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\SuperSocketNetLib], it is for SQL 2k compatibility purposes. What you can do is to capture a RegMon from a service startup attempt (http://www.microsoft.com/technet/sysinternals/utilities/regmon.mspx) and look for access denied entries in it. Based on that you can grant access and go from there. Similar for files - you could use FileMon (http://www.microsoft.com/technet/sysinternals/FileAndDisk/Filemon.mspx).

More information about the initialization failure status codes is available here: http://blogs.msdn.com/sql_protocols/archive/2006/04/28/585835.aspx.

HTH,
Jivko Dobrev - MSFT
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Thank you, I was looking for a way to see the Registry access.

As far as the database files, here are the folders the account has "Full Control" over:

E:\MSSQL$STAGING\MSSQL.4\MSSQL (Stores the files for the system databases)

E:\MSSQL$STAGING\Data (Stores the files for all other databases)

I orginally granted the account "Full Control" at the parent folder (E:\MSSQL$STAGING), but this did not work.

I'll try out your suggestions and post back later.

|||

I'll need some more time to learn how to use regmon. It was returning far too much data to be useful.

I did a search for "SuperSocketNetLib" within the Registry Editor. I found it in the following keys:

Code Snippet

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer\SuperSocketNetLib

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.4\MSSQLServer\SuperSocketNetLib

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\STAGING\MSSQLServer\SuperSocketNetLib

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SuperSocketNetLib

I granted the service account "Full Control" on the first four keys I listed. The account already had "Read" permissions on "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SuperSocketNetLib" due to its membership in the "SQLServerBrowserUser" Windows group.

After making these changes, I was able to start the SQL Server service. Everything appeared to be working until I checked EventViewer. The following error was rapidly filling the Application Log:

Code Snippet

UpdateUptimeRegKey: Operating system error 5(Access is denied.) encountered.

I searched the Registry for both "UpdateUptime" and "UpdateUptimeRegKey" and found nothing. Is this a Registry key or is this something else?

My next step is to grant the service account "Full Control" over the following keys:

Code Snippet

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server (and subfolders)

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer (and subfolders)

You had told me to do this but I hadn't done so.

I'll post back later with additional results.

|||

Granting the service account "Full Control" over "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server (and subfolders)" and "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer (and subfolders)" resolved the errors for "UpdateUptimeRegKey".

I was now able to start the service and keep it running without any further Windows errors. Unfortunately, I now started receiving errors within SQL Server. Two developers were trying to execute a stored procedure. They received the following error:

"An error occurred during decryption"

I did some research, and found out the error refers to the Service Master Key. Once again, the error disappears when I add the service account back to "SQLServer2005MSSQLUser".

Am I going to need to rebuild the master database in order to accomplish this change?

|||

Hi Ken!

In the last few days I've tried to do exactly the same as you. I become a task to audit an MSSQL 2005 Standard server. I realised that the SQL server was originaly intalled to run the service under the Administrator account. So as in many reference, I try to change also the account to use a service account with the minimum privileges. Which is the 'NT AUTHORITY\NetworkService'. After it, I try to start the service and my problems began. I resolved step-by-step the same problems as you. Registry keys permission change, checking folders permissions and so on. Even I must change some settings with the Component Service Manager to let Local Activation for Microsoft Search FTE Admin. Anyway, at the end I still have this error message in the Event Viewer just as you.

So my question is that have you find out how can this error resolved? Or somebody else?

Many thanks!

|||

Actually, I discovered I misunderstood the new security model for SQL Server. My misunderstanding was that I thought that the SQL Server service account should NOT be a member of the "sysadmin" fixed server role. It turns out that the account IS supposed to be a member of "sysadmin". Therefore, the is no reason to remove the service account from the SQLServer2005MSSQLUser" group.

The documentation in SQL Server Books Online needs to be revised to make this clear. When you read the Books Online article "Setting Up Windows Service Accounts", this is what it says in the "Reviewing Windows Permissions for SQL Server Services", in the "Required permissions" column:

Local user is recommended.

Under "Minimum permissions", it says the following:

"The account must be in the list of accounts that have "List Folder" permissions on the root drive where SQL Server is installed, and on the root of any other drive where SQL Server files are stored." and "The account must have "Full Control" permissions over any folders where data or log files (.mdf, .ndf, .ldf) will reside."

There is not one word about the requirement that the account be a sysadmin. By contrast, here is what the same article says about the Minimum permissions for the SQL Server Agent service account:

"The account must be a member of the sysadmin fixed server role."

Maybe Microsoft just assumed that we would know that the service account needed to be a sysadmin.

Microsoft could save us all a lot of headaches if they would include this simple statement with the information for the SQL Server service account.

Error Accessing SSRS Web Applications - Service Unavailable/Invalid Version

We have an instance of SQL Server 2005 on a server that also has a SQL
Server 2000 instance. Neither was installed with Reporting Services. We went
back and installed Reporting Services on the 2005 instance only. Went
through the config tool with no problems and the virtual directories look
fine in IIS.
When we try to hit the Reports web page using IE, we get "Service
Unavailable." The service shows as "Started."
Event viewer shows two errors, which occur every 12 hours. The first says
"The report server database is an invalid version" (Event ID 117) and the
second says "Report Server Windows Service (MSSQLSERVER) cannot connect to
the report server dartabase" (Event ID 107).
The server has 2.0 of the framework intalled and the SSRS web applications
are pointing to ASP 2.0.
I googled around on these messages and the only resolutions I found
suggested that the Reporting Services config tool had not been run. It had
been run, and to play it safe I ran it again. But no luck.
Any suggestions? The server is running Windows Server 2003 SP1 and SQL
Server is version 9.0.3054.
Thanks in advance for any help.On Dec 6, 11:20 am, "CapCity" <sgomori at yahoo dot com> wrote:
> We have an instance of SQLServer2005 on aserverthat also has a SQLServer2000 instance. Neither was installed with Reporting Services. We went
> back and installed Reporting Services on the 2005 instance only. Went
> through the config tool with no problems and the virtual directories look
> fine in IIS.
> When we try to hit the Reports web page using IE, we get "Service
> Unavailable." Theserviceshows as "Started."
> Event viewer shows two errors, which occur every 12 hours. The first says
> "Thereportserverdatabase is an invalid version" (Event ID 117) and the
> second says "ReportServerWindowsService(MSSQLSERVER) cannot connect to
> thereportserverdartabase" (Event ID 107).
> Theserverhas 2.0 of the framework intalled and the SSRS web applications
> are pointing to ASP 2.0.
> I googled around on these messages and the only resolutions I found
> suggested that the Reporting Services config tool hadnotbeen run. It had
> been run, and to play it safe I ran it again. But no luck.
> Any suggestions? TheserverisrunningWindowsServer2003 SP1 and SQLServeris version 9.0.3054.
> Thanks in advance for any help.
The *WINDOWS* Service may not be running.
Start >> Administrative Tools >> Services >> SQL Server Reporting
Services (MSSQLSERVER)
Make sure that is started and working properly.|||"BM" <moore.brent@.gmail.com> wrote in message
news:c25281d0-9f47-41ff-844f-e6317ec42e09@.w40g2000hsb.googlegroups.com...
> On Dec 6, 11:20 am, "CapCity" <sgomori at yahoo dot com> wrote:
>> We have an instance of SQLServer2005 on aserverthat also has a
>> SQLServer2000 instance. Neither was installed with Reporting Services. We
>> went
>> back and installed Reporting Services on the 2005 instance only. Went
>> through the config tool with no problems and the virtual directories look
>> fine in IIS.
>> When we try to hit the Reports web page using IE, we get "Service
>> Unavailable." Theserviceshows as "Started."
>> Event viewer shows two errors, which occur every 12 hours. The first says
>> "Thereportserverdatabase is an invalid version" (Event ID 117) and the
>> second says "ReportServerWindowsService(MSSQLSERVER) cannot connect to
>> thereportserverdartabase" (Event ID 107).
>> Theserverhas 2.0 of the framework intalled and the SSRS web applications
>> are pointing to ASP 2.0.
>> I googled around on these messages and the only resolutions I found
>> suggested that the Reporting Services config tool hadnotbeen run. It had
>> been run, and to play it safe I ran it again. But no luck.
>> Any suggestions? TheserverisrunningWindowsServer2003 SP1 and SQLServeris
>> version 9.0.3054.
>> Thanks in advance for any help.
> The *WINDOWS* Service may not be running.
> Start >> Administrative Tools >> Services >> SQL Server Reporting
> Services (MSSQLSERVER)
> Make sure that is started and working properly.
The service is running. I even stopped it and restarted it, but still get
the same error.

error accessing rs web service

I am having problems accessing reporting services using the report viewer web service from a web application. We are getting the following error.
System.Net.WebException: The request failed with HTTP status 401: Access Denied.
Below is the code. The uncommented code works, but we don't want to hard code a user. The DefaultCredentials are coming up blank. Any suggestions on why this may be or what to do to correct would be appreciated.
<code>

Dim rsAsNew reportserver_dev.ReportingService

Dim itemAs reportserver_dev.CatalogItem

' gets users network creditentials for reporting services

'rs.Credentials = System.Net.CredentialCache.DefaultCredentials

' ***** to do: this is temporary to force authentication

Dim cacheAsNew System.Net.CredentialCache

cache.Add(New Uri(rs.Url), "Negotiate",New System.Net.NetworkCredential("user", "pwd", "domain"))

rs.Credentials = cache

</code>
Hi,
In your web.config is set <identity impersonate="true" /> ?
Regards
|||Hello creagan,
Is the reporting service on the same machine or on a remote machine? If the
report server is a remote machine, then using impersonation and CredentialCache.DefaultCredentials
doesn't work because of a one-hop limitation in NTLM authentication.
Authentication, Role-based Security, and SQL Reporting Services
Roadmap to Delegation

HTH,|||

Please try these links

http://support.microsoft.com/?id=306158
http://www.c-sharpcorner.com/UploadFile/chauhan_sonu57/ProgrammaticImpersonation02022006080545AM/ProgrammaticImpersonation.aspx?ArticleID=3aa21cd6-b867-4306-96ed-de0ba5930fa1
http://blogs.msdn.com/bimusings/archive/2005/11/18/494436.aspx

Regards,
Jimmy