I just got a new laptop for work, and our local IT/Hardware guy used
PCMover from Laplink to migrate the apps and settings from my old
machine to this new one. I was skeptical, but it's actually worked
quite well, the biggest issue that I'm having is getting SQL Server to
run on the new machine.
Using SQL Server 2000. Both laptops are Windows XP Pro SP2.
After the migration, I did have to recreate the services for the
server and agent (those services weren't migrated):
C:\Program Files\Microsoft SQL Server\80\Tools\Binn\scm.exe -action 5 -
service MSSQLServer -exepath "c:\Program Files\Microsoft SQL Server
\MSSQL\Binn\sqlservr.exe"
C:\Program Files\Microsoft SQL Server\80\Tools\Binn\scm.exe -action 5 -
service SQLSERVERAGENT -exepath "c:\Program Files\Microsoft SQL Server
\MSSQL\Binn\sqlagent.exe" -dependencies MSSQLServer
If I don't include the SQL Server dependency on the SQL Agent, then
the Agent starts just fine. When I try to start the SQL Server
service, it displays a dialog error:
The MSSQLServer service on Local Computer started and then stopped.
Some Services stop automatically if they have no work to do, for
example, the Performance Logs and Alerts service.
Here's the contents of the server log:
2007-02-08 10:38:58.14 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
2007-02-08 10:38:58.14 server Copyright (C) 1988-2002 Microsoft
Corporation.
2007-02-08 10:38:58.14 server All rights reserved.
2007-02-08 10:38:58.14 server Server Process ID is 5860.
2007-02-08 10:38:58.14 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2007-02-08 10:38:58.17 server SQL Server is starting at priority
class 'normal'(2 CPUs detected).
2007-02-08 10:38:58.84 server SQL Server configured for thread mode
processing.
2007-02-08 10:38:58.84 server Using dynamic lock allocation. [2500]
Lock Blocks, [5000] Lock Owner Blocks.
2007-02-08 10:38:58.87 server Attempting to initialize Distributed
Transaction Coordinator.
2007-02-08 10:38:58.89 server Failed to obtain
TransactionDispenserInterface: Result Code = 0x8004d01b
2007-02-08 10:38:58.89 server Unable to load any NETLIBs. Server
shutting down.
2007-02-08 10:38:58.89 spid4 Starting up database 'master'.
The failure to obtain TransactionDispenserInterface message was
occurring on the old machine, so I conclude that isn't part of the
issue.
The Server Network Utility does show TCP/IP as the only protocol
enabled. The Network Libraries tab does show the TCP/IP SSNETLIB.DLL
listed and that dll is residing in the expected location (C:\Program
Files\Microsoft SQL Server\MSSQL\Binn).
The service properties page page Log On tab shows the Local System
Account to be used for logon.
So, I'm figuring it can't find ssnetlib.dll. Short of uninstalling
and re-installing SQL Server, how can I get my SQL Server back up and
running?
Thanks in advance
Mark>I just got a new laptop for work, and our local IT/Hardware guy used
> PCMover from Laplink to migrate the apps and settings from my old
> machine to this new one. I was skeptical,
And you should have been. The errorlog clearly states that SQL Server cannot load any netlibs, so it
refuses to start. I.e., the installation isn't OK...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<mark.a.lemoine@.gmail.com> wrote in message
news:1170950095.972400.293760@.s48g2000cws.googlegroups.com...
>I just got a new laptop for work, and our local IT/Hardware guy used
> PCMover from Laplink to migrate the apps and settings from my old
> machine to this new one. I was skeptical, but it's actually worked
> quite well, the biggest issue that I'm having is getting SQL Server to
> run on the new machine.
> Using SQL Server 2000. Both laptops are Windows XP Pro SP2.
> After the migration, I did have to recreate the services for the
> server and agent (those services weren't migrated):
> C:\Program Files\Microsoft SQL Server\80\Tools\Binn\scm.exe -action 5 -
> service MSSQLServer -exepath "c:\Program Files\Microsoft SQL Server
> \MSSQL\Binn\sqlservr.exe"
> C:\Program Files\Microsoft SQL Server\80\Tools\Binn\scm.exe -action 5 -
> service SQLSERVERAGENT -exepath "c:\Program Files\Microsoft SQL Server
> \MSSQL\Binn\sqlagent.exe" -dependencies MSSQLServer
> If I don't include the SQL Server dependency on the SQL Agent, then
> the Agent starts just fine. When I try to start the SQL Server
> service, it displays a dialog error:
> The MSSQLServer service on Local Computer started and then stopped.
> Some Services stop automatically if they have no work to do, for
> example, the Performance Logs and Alerts service.
> Here's the contents of the server log:
> 2007-02-08 10:38:58.14 server Microsoft SQL Server 2000 - 8.00.760
> (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
> 2007-02-08 10:38:58.14 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2007-02-08 10:38:58.14 server All rights reserved.
> 2007-02-08 10:38:58.14 server Server Process ID is 5860.
> 2007-02-08 10:38:58.14 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> 2007-02-08 10:38:58.17 server SQL Server is starting at priority
> class 'normal'(2 CPUs detected).
> 2007-02-08 10:38:58.84 server SQL Server configured for thread mode
> processing.
> 2007-02-08 10:38:58.84 server Using dynamic lock allocation. [2500]
> Lock Blocks, [5000] Lock Owner Blocks.
> 2007-02-08 10:38:58.87 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2007-02-08 10:38:58.89 server Failed to obtain
> TransactionDispenserInterface: Result Code = 0x8004d01b
> 2007-02-08 10:38:58.89 server Unable to load any NETLIBs. Server
> shutting down.
> 2007-02-08 10:38:58.89 spid4 Starting up database 'master'.
> The failure to obtain TransactionDispenserInterface message was
> occurring on the old machine, so I conclude that isn't part of the
> issue.
> The Server Network Utility does show TCP/IP as the only protocol
> enabled. The Network Libraries tab does show the TCP/IP SSNETLIB.DLL
> listed and that dll is residing in the expected location (C:\Program
> Files\Microsoft SQL Server\MSSQL\Binn).
> The service properties page page Log On tab shows the Local System
> Account to be used for logon.
> So, I'm figuring it can't find ssnetlib.dll. Short of uninstalling
> and re-installing SQL Server, how can I get my SQL Server back up and
> running?
> Thanks in advance
> Mark
>sql
Showing posts with label apps. Show all posts
Showing posts with label apps. Show all posts
Tuesday, March 27, 2012
Can't start the MSSQLServer Service
I just got a new laptop for work, and our local IT/Hardware guy used
PCMover from Laplink to migrate the apps and settings from my old
machine to this new one. I was skeptical, but it's actually worked
quite well, the biggest issue that I'm having is getting SQL Server to
run on the new machine.
Using SQL Server 2000. Both laptops are Windows XP Pro SP2.
After the migration, I did have to recreate the services for the
server and agent (those services weren't migrated):
C:\Program Files\Microsoft SQL Server\80\Tools\Binn\scm.exe -action 5 -
service MSSQLServer -exepath "c:\Program Files\Microsoft SQL Server
\MSSQL\Binn\sqlservr.exe"
C:\Program Files\Microsoft SQL Server\80\Tools\Binn\scm.exe -action 5 -
service SQLSERVERAGENT -exepath "c:\Program Files\Microsoft SQL Server
\MSSQL\Binn\sqlagent.exe" -dependencies MSSQLServer
If I don't include the SQL Server dependency on the SQL Agent, then
the Agent starts just fine. When I try to start the SQL Server
service, it displays a dialog error:
The MSSQLServer service on Local Computer started and then stopped.
Some Services stop automatically if they have no work to do, for
example, the Performance Logs and Alerts service.
Here's the contents of the server log:
2007-02-08 10:38:58.14 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
2007-02-08 10:38:58.14 server Copyright (C) 1988-2002 Microsoft
Corporation.
2007-02-08 10:38:58.14 server All rights reserved.
2007-02-08 10:38:58.14 server Server Process ID is 5860.
2007-02-08 10:38:58.14 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2007-02-08 10:38:58.17 server SQL Server is starting at priority
class 'normal'(2 CPUs detected).
2007-02-08 10:38:58.84 server SQL Server configured for thread mode
processing.
2007-02-08 10:38:58.84 server Using dynamic lock allocation. [2500]
Lock Blocks, [5000] Lock Owner Blocks.
2007-02-08 10:38:58.87 server Attempting to initialize Distributed
Transaction Coordinator.
2007-02-08 10:38:58.89 server Failed to obtain
TransactionDispenserInterface: Result Code = 0x8004d01b
2007-02-08 10:38:58.89 server Unable to load any NETLIBs. Server
shutting down.
2007-02-08 10:38:58.89 spid4 Starting up database 'master'.
The failure to obtain TransactionDispenserInterface message was
occurring on the old machine, so I conclude that isn't part of the
issue.
The Server Network Utility does show TCP/IP as the only protocol
enabled. The Network Libraries tab does show the TCP/IP SSNETLIB.DLL
listed and that dll is residing in the expected location (C:\Program
Files\Microsoft SQL Server\MSSQL\Binn).
The service properties page page Log On tab shows the Local System
Account to be used for logon.
So, I'm figuring it can't find ssnetlib.dll. Short of uninstalling
and re-installing SQL Server, how can I get my SQL Server back up and
running?
Thanks in advance
Mark>I just got a new laptop for work, and our local IT/Hardware guy used
> PCMover from Laplink to migrate the apps and settings from my old
> machine to this new one. I was skeptical,
And you should have been. The errorlog clearly states that SQL Server cannot
load any netlibs, so it
refuses to start. I.e., the installation isn't OK...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<mark.a.lemoine@.gmail.com> wrote in message
news:1170950095.972400.293760@.s48g2000cws.googlegroups.com...
>I just got a new laptop for work, and our local IT/Hardware guy used
> PCMover from Laplink to migrate the apps and settings from my old
> machine to this new one. I was skeptical, but it's actually worked
> quite well, the biggest issue that I'm having is getting SQL Server to
> run on the new machine.
> Using SQL Server 2000. Both laptops are Windows XP Pro SP2.
> After the migration, I did have to recreate the services for the
> server and agent (those services weren't migrated):
> C:\Program Files\Microsoft SQL Server\80\Tools\Binn\scm.exe -action 5 -
> service MSSQLServer -exepath "c:\Program Files\Microsoft SQL Server
> \MSSQL\Binn\sqlservr.exe"
> C:\Program Files\Microsoft SQL Server\80\Tools\Binn\scm.exe -action 5 -
> service SQLSERVERAGENT -exepath "c:\Program Files\Microsoft SQL Server
> \MSSQL\Binn\sqlagent.exe" -dependencies MSSQLServer
> If I don't include the SQL Server dependency on the SQL Agent, then
> the Agent starts just fine. When I try to start the SQL Server
> service, it displays a dialog error:
> The MSSQLServer service on Local Computer started and then stopped.
> Some Services stop automatically if they have no work to do, for
> example, the Performance Logs and Alerts service.
> Here's the contents of the server log:
> 2007-02-08 10:38:58.14 server Microsoft SQL Server 2000 - 8.00.760
> (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
> 2007-02-08 10:38:58.14 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2007-02-08 10:38:58.14 server All rights reserved.
> 2007-02-08 10:38:58.14 server Server Process ID is 5860.
> 2007-02-08 10:38:58.14 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> 2007-02-08 10:38:58.17 server SQL Server is starting at priority
> class 'normal'(2 CPUs detected).
> 2007-02-08 10:38:58.84 server SQL Server configured for thread mode
> processing.
> 2007-02-08 10:38:58.84 server Using dynamic lock allocation. [2500]
> Lock Blocks, [5000] Lock Owner Blocks.
> 2007-02-08 10:38:58.87 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2007-02-08 10:38:58.89 server Failed to obtain
> TransactionDispenserInterface: Result Code = 0x8004d01b
> 2007-02-08 10:38:58.89 server Unable to load any NETLIBs. Server
> shutting down.
> 2007-02-08 10:38:58.89 spid4 Starting up database 'master'.
> The failure to obtain TransactionDispenserInterface message was
> occurring on the old machine, so I conclude that isn't part of the
> issue.
> The Server Network Utility does show TCP/IP as the only protocol
> enabled. The Network Libraries tab does show the TCP/IP SSNETLIB.DLL
> listed and that dll is residing in the expected location (C:\Program
> Files\Microsoft SQL Server\MSSQL\Binn).
> The service properties page page Log On tab shows the Local System
> Account to be used for logon.
> So, I'm figuring it can't find ssnetlib.dll. Short of uninstalling
> and re-installing SQL Server, how can I get my SQL Server back up and
> running?
> Thanks in advance
> Mark
>
PCMover from Laplink to migrate the apps and settings from my old
machine to this new one. I was skeptical, but it's actually worked
quite well, the biggest issue that I'm having is getting SQL Server to
run on the new machine.
Using SQL Server 2000. Both laptops are Windows XP Pro SP2.
After the migration, I did have to recreate the services for the
server and agent (those services weren't migrated):
C:\Program Files\Microsoft SQL Server\80\Tools\Binn\scm.exe -action 5 -
service MSSQLServer -exepath "c:\Program Files\Microsoft SQL Server
\MSSQL\Binn\sqlservr.exe"
C:\Program Files\Microsoft SQL Server\80\Tools\Binn\scm.exe -action 5 -
service SQLSERVERAGENT -exepath "c:\Program Files\Microsoft SQL Server
\MSSQL\Binn\sqlagent.exe" -dependencies MSSQLServer
If I don't include the SQL Server dependency on the SQL Agent, then
the Agent starts just fine. When I try to start the SQL Server
service, it displays a dialog error:
The MSSQLServer service on Local Computer started and then stopped.
Some Services stop automatically if they have no work to do, for
example, the Performance Logs and Alerts service.
Here's the contents of the server log:
2007-02-08 10:38:58.14 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
2007-02-08 10:38:58.14 server Copyright (C) 1988-2002 Microsoft
Corporation.
2007-02-08 10:38:58.14 server All rights reserved.
2007-02-08 10:38:58.14 server Server Process ID is 5860.
2007-02-08 10:38:58.14 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2007-02-08 10:38:58.17 server SQL Server is starting at priority
class 'normal'(2 CPUs detected).
2007-02-08 10:38:58.84 server SQL Server configured for thread mode
processing.
2007-02-08 10:38:58.84 server Using dynamic lock allocation. [2500]
Lock Blocks, [5000] Lock Owner Blocks.
2007-02-08 10:38:58.87 server Attempting to initialize Distributed
Transaction Coordinator.
2007-02-08 10:38:58.89 server Failed to obtain
TransactionDispenserInterface: Result Code = 0x8004d01b
2007-02-08 10:38:58.89 server Unable to load any NETLIBs. Server
shutting down.
2007-02-08 10:38:58.89 spid4 Starting up database 'master'.
The failure to obtain TransactionDispenserInterface message was
occurring on the old machine, so I conclude that isn't part of the
issue.
The Server Network Utility does show TCP/IP as the only protocol
enabled. The Network Libraries tab does show the TCP/IP SSNETLIB.DLL
listed and that dll is residing in the expected location (C:\Program
Files\Microsoft SQL Server\MSSQL\Binn).
The service properties page page Log On tab shows the Local System
Account to be used for logon.
So, I'm figuring it can't find ssnetlib.dll. Short of uninstalling
and re-installing SQL Server, how can I get my SQL Server back up and
running?
Thanks in advance
Mark>I just got a new laptop for work, and our local IT/Hardware guy used
> PCMover from Laplink to migrate the apps and settings from my old
> machine to this new one. I was skeptical,
And you should have been. The errorlog clearly states that SQL Server cannot
load any netlibs, so it
refuses to start. I.e., the installation isn't OK...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<mark.a.lemoine@.gmail.com> wrote in message
news:1170950095.972400.293760@.s48g2000cws.googlegroups.com...
>I just got a new laptop for work, and our local IT/Hardware guy used
> PCMover from Laplink to migrate the apps and settings from my old
> machine to this new one. I was skeptical, but it's actually worked
> quite well, the biggest issue that I'm having is getting SQL Server to
> run on the new machine.
> Using SQL Server 2000. Both laptops are Windows XP Pro SP2.
> After the migration, I did have to recreate the services for the
> server and agent (those services weren't migrated):
> C:\Program Files\Microsoft SQL Server\80\Tools\Binn\scm.exe -action 5 -
> service MSSQLServer -exepath "c:\Program Files\Microsoft SQL Server
> \MSSQL\Binn\sqlservr.exe"
> C:\Program Files\Microsoft SQL Server\80\Tools\Binn\scm.exe -action 5 -
> service SQLSERVERAGENT -exepath "c:\Program Files\Microsoft SQL Server
> \MSSQL\Binn\sqlagent.exe" -dependencies MSSQLServer
> If I don't include the SQL Server dependency on the SQL Agent, then
> the Agent starts just fine. When I try to start the SQL Server
> service, it displays a dialog error:
> The MSSQLServer service on Local Computer started and then stopped.
> Some Services stop automatically if they have no work to do, for
> example, the Performance Logs and Alerts service.
> Here's the contents of the server log:
> 2007-02-08 10:38:58.14 server Microsoft SQL Server 2000 - 8.00.760
> (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
> 2007-02-08 10:38:58.14 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2007-02-08 10:38:58.14 server All rights reserved.
> 2007-02-08 10:38:58.14 server Server Process ID is 5860.
> 2007-02-08 10:38:58.14 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> 2007-02-08 10:38:58.17 server SQL Server is starting at priority
> class 'normal'(2 CPUs detected).
> 2007-02-08 10:38:58.84 server SQL Server configured for thread mode
> processing.
> 2007-02-08 10:38:58.84 server Using dynamic lock allocation. [2500]
> Lock Blocks, [5000] Lock Owner Blocks.
> 2007-02-08 10:38:58.87 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2007-02-08 10:38:58.89 server Failed to obtain
> TransactionDispenserInterface: Result Code = 0x8004d01b
> 2007-02-08 10:38:58.89 server Unable to load any NETLIBs. Server
> shutting down.
> 2007-02-08 10:38:58.89 spid4 Starting up database 'master'.
> The failure to obtain TransactionDispenserInterface message was
> occurring on the old machine, so I conclude that isn't part of the
> issue.
> The Server Network Utility does show TCP/IP as the only protocol
> enabled. The Network Libraries tab does show the TCP/IP SSNETLIB.DLL
> listed and that dll is residing in the expected location (C:\Program
> Files\Microsoft SQL Server\MSSQL\Binn).
> The service properties page page Log On tab shows the Local System
> Account to be used for logon.
> So, I'm figuring it can't find ssnetlib.dll. Short of uninstalling
> and re-installing SQL Server, how can I get my SQL Server back up and
> running?
> Thanks in advance
> Mark
>
Tuesday, March 20, 2012
Can't see new objects created in SQL Server from C#
We have just installed SQL and C# Express. We have lots of experience with SQL, but none with C#. With both the SQL and C# apps running; if we create a new table, view etc, we cannot see that new object from C# only the objects that existed when we opened the apps for the first time (each time).
If we close everything and re-open everything from scratch, the new objects show..!?!?
Thank you for any information on this difficult problem.
Hard to tell without knowing which technique youuse to display the objects and if there is eventually somehow a caching mechanism involved. Could you post some code which does the retrieval ?Jens K. Suessmeyer
http://www.sqlserver2005.de
Friday, February 10, 2012
Can't get Reporting Services working after reinstall
I had to make room on the system partition so I uninstalled SQL 2005 Ent. and reinstalled it in a different partition, which is mounted in c:\apps. Since doing this, although MSSQL works fine, RS does not respond. During the reinstall, Setup reported that RS was "installed but not configured". I ran the RS Configuration Mgr and went through the config sequence. However, on the Initialization page, which has a red 'x' in the left panel, the local server is not listed -- the grid is empty.
__
EventID 18456: "Login failed for user 'NT AUTHORITY\NETWORK SERVICE'." from MSSQL
The RS service is running, using the same credentials as MSSQL, the admin account .\SQLExec. It logs a normal startup in the Event Log. However, on visiting http://localhost/Reports, I get a message saying that Reporting Services is not responding. SP2 installed OK on the system, and reported that all components were upgraded.
How can I debug this installation?
Check for any other information on windows event log.
Also check under the services whether thye have been started successfully.
|||MSSQL, SSRS, SQL Agent, and IIS are running. I did see some interesting messages in the Application Log:__
EventID 18456: "Login failed for user 'NT AUTHORITY\NETWORK SERVICE'." from MSSQL
EventID 107: "Report Server (MSSQLSERVER) cannot connect to the report server database." From Reporting Svcs.
__
I check in SQL Mgt. Studio: 'NT Authority\Network Service' is set up as a SQL login. The account is in the dbo and RSExecRole roles in the ReportServer database. In the RS Config Mgr, this account is shown as the ASP.NET Service account. The Report Server and Report Manager are both set to "Default Application Pool".
sp_who shows that the 'NT Authority\Network Service' login IS connected to the ReportServer database, along with two other connections to this db from the SQL Service account, .\SQLExec, which is used by all SQL-related services.
When I visit http://localhost/Reports, I now get the message: "Key not valid for use in specified state.
(Exception from HRESULT: 0x8009000B) (rsRPCError)". What does this mean?
One thing I recall seeing when I created the ReportServer database in the RS Configuration Mgr was a warning (yellow '!') saying it was "unable to access internal information" about the installation to verify the connection. Is this a clue?
Any advice how to proceed?|||Further searching revealed this may have to do with a crypto key left over from the prior installation, found under "C:\Documents and Settings\SQLExec\Application
Data\Microsoft\Crypto\RSA" in a file matching "1aedd7b5699f3d6a88e354100b596aae*" Advice was to delete this file and recreate it using the 'rsactivate' utility, which I cannot find. The discussion I found pertained to SSRS 2000 and not in 2005.
What's the correct way to fix this problem in Reporting Services 2005?|||Deleting the 1aedd* key file corrected the problem. I uninstalled SSRS, deleted the old RS databases, deleted the key file, reinstalled SSRS, reapplied SP2. After doing this, each step in the Reporting Svcs Config Mgr then worked correctly.
I would rate this as a serious problem with either SQL Setup or the RS Config Mgr if neither can diagnose nor correct the problem. If I hadn't stumbled across mention of the 1aedd* file on someone's blog I would not have been able to get Reporting Services to work following the reinstallation of MSSQL and its components.
Can't get Reporting Services working after reinstall
I had to make room on the system partition so I uninstalled SQL 2005 Ent. and reinstalled it in a different partition, which is mounted in c:\apps. Since doing this, although MSSQL works fine, RS does not respond. During the reinstall, Setup reported that RS was "installed but not configured". I ran the RS Configuration Mgr and went through the config sequence. However, on the Initialization page, which has a red 'x' in the left panel, the local server is not listed -- the grid is empty.
__
EventID 18456: "Login failed for user 'NT AUTHORITY\NETWORK SERVICE'." from MSSQL
The RS service is running, using the same credentials as MSSQL, the admin account .\SQLExec. It logs a normal startup in the Event Log. However, on visiting http://localhost/Reports, I get a message saying that Reporting Services is not responding. SP2 installed OK on the system, and reported that all components were upgraded.
How can I debug this installation?
Check for any other information on windows event log.
Also check under the services whether thye have been started successfully.
|||MSSQL, SSRS, SQL Agent, and IIS are running. I did see some interesting messages in the Application Log:__
EventID 18456: "Login failed for user 'NT AUTHORITY\NETWORK SERVICE'." from MSSQL
EventID 107: "Report Server (MSSQLSERVER) cannot connect to the report server database." From Reporting Svcs.
__
I check in SQL Mgt. Studio: 'NT Authority\Network Service' is set up as a SQL login. The account is in the dbo and RSExecRole roles in the ReportServer database. In the RS Config Mgr, this account is shown as the ASP.NET Service account. The Report Server and Report Manager are both set to "Default Application Pool".
sp_who shows that the 'NT Authority\Network Service' login IS connected to the ReportServer database, along with two other connections to this db from the SQL Service account, .\SQLExec, which is used by all SQL-related services.
When I visit http://localhost/Reports, I now get the message: "Key not valid for use in specified state.
(Exception from HRESULT: 0x8009000B) (rsRPCError)". What does this mean?
One thing I recall seeing when I created the ReportServer database in the RS Configuration Mgr was a warning (yellow '!') saying it was "unable to access internal information" about the installation to verify the connection. Is this a clue?
Any advice how to proceed?|||Further searching revealed this may have to do with a crypto key left over from the prior installation, found under "C:\Documents and Settings\SQLExec\Application
Data\Microsoft\Crypto\RSA" in a file matching "1aedd7b5699f3d6a88e354100b596aae*" Advice was to delete this file and recreate it using the 'rsactivate' utility, which I cannot find. The discussion I found pertained to SSRS 2000 and not in 2005.
What's the correct way to fix this problem in Reporting Services 2005?|||Deleting the 1aedd* key file corrected the problem. I uninstalled SSRS, deleted the old RS databases, deleted the key file, reinstalled SSRS, reapplied SP2. After doing this, each step in the Reporting Svcs Config Mgr then worked correctly.
I would rate this as a serious problem with either SQL Setup or the RS Config Mgr if neither can diagnose nor correct the problem. If I hadn't stumbled across mention of the 1aedd* file on someone's blog I would not have been able to get Reporting Services to work following the reinstallation of MSSQL and its components.
Subscribe to:
Posts (Atom)