Thursday, March 29, 2012
can't connect 2005 reporting server...need help
window2003 with sp1 and IIS 6.0 is running on it as well. I am in local
admin and got error when i try to connect report server:
Cannot execute a program. The command being executed was
"C:\WINNT\Microsoft.NET\Framework\v2.0.50727\csc.exe" /noconfig /fullpaths
@."C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
Files\reports$sql2005\47980326\bf0ad169\lzwjfwcj.cmdline".
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information about
the error and where it originated in the code.
Exception Details: System.Runtime.InteropServices.ExternalException: Cannot
execute a program. The command being executed was
"C:\WINNT\Microsoft.NET\Framework\v2.0.50727\csc.exe" /noconfig /fullpaths
@."C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
Files\reports$sql2005\47980326\bf0ad169\lzwjfwcj.cmdline".
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
anyone knows about this and thanks alot for a help
Karen,On Apr 27, 1:50 pm, Karen Chen <KarenC...@.discussions.microsoft.com>
wrote:
> We installed sql 2005 server and reporting services (standard edition) on
> window2003 with sp1 and IIS 6.0 is running on it as well. I am in local
> admin and got error when i try to connect report server:
> Cannot execute a program. The command being executed was
> "C:\WINNT\Microsoft.NET\Framework\v2.0.50727\csc.exe" /noconfig /fullpaths
> @."C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
> Files\reports$sql2005\47980326\bf0ad169\lzwjfwcj.cmdline".
> Description: An unhandled exception occurred during the execution of the
> current web request. Please review the stack trace for more information about
> the error and where it originated in the code.
> Exception Details: System.Runtime.InteropServices.ExternalException: Cannot
> execute a program. The command being executed was
> "C:\WINNT\Microsoft.NET\Framework\v2.0.50727\csc.exe" /noconfig /fullpaths
> @."C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
> Files\reports$sql2005\47980326\bf0ad169\lzwjfwcj.cmdline".
> Source Error:
> An unhandled exception was generated during the execution of the current web
> request. Information regarding the origin and location of the exception can
> be identified using the exception stack trace below.
> anyone knows about this and thanks alot for a help
> Karen,
I received your email and noticed that you posted here as well. If you
do not have the .NET 2.0 framework installed, this might be the
problem.
Regards,
Enrique Martinez
Sr. Software Consultant
Can't connect 2005 reporting server
window2003 with sp1 and IIS 6.0 is running on it as well. I am in local
admin and got error when i try to connect report server:
Cannot execute a program. The command being executed was
"C:\WINNT\Microsoft.NET\Framework\v2.0.50727\csc.exe" /noconfig /fullpaths
@."C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
Files\reports$sql2005\47980326\bf0ad169\lzwjfwcj.cmdline".
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information about
the error and where it originated in the code.
Exception Details: System.Runtime.InteropServices.ExternalException: Cannot
execute a program. The command being executed was
"C:\WINNT\Microsoft.NET\Framework\v2.0.50727\csc.exe" /noconfig /fullpaths
@."C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
Files\reports$sql2005\47980326\bf0ad169\lzwjfwcj.cmdline".
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
anyone knows about this and thanks alot for a help
Karen,On Apr 27, 2:24 pm, Karen Chen <KarenC...@.discussions.microsoft.com>
wrote:
> We installed sql 2005 server and reporting services (standard edition) on
> window2003 with sp1 and IIS 6.0 is running on it as well. I am in local
> admin and got error when i try to connect report server:
> Cannot execute a program. The command being executed was
> "C:\WINNT\Microsoft.NET\Framework\v2.0.50727\csc.exe" /noconfig /fullpaths
> @."C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
> Files\reports$sql2005\47980326\bf0ad169\lzwjfwcj.cmdline".
> Description: An unhandled exception occurred during the execution of the
> current web request. Please review the stack trace for more information about
> the error and where it originated in the code.
> Exception Details: System.Runtime.InteropServices.ExternalException: Cannot
> execute a program. The command being executed was
> "C:\WINNT\Microsoft.NET\Framework\v2.0.50727\csc.exe" /noconfig /fullpaths
> @."C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
> Files\reports$sql2005\47980326\bf0ad169\lzwjfwcj.cmdline".
> Source Error:
> An unhandled exception was generated during the execution of the current web
> request. Information regarding the origin and location of the exception can
> be identified using the exception stack trace below.
> anyone knows about this and thanks alot for a help
> Karen,
Please refer to my previous post at:
http://groups.google.com/group/microsoft.public.sqlserver.reportingsvcs/browse_thread/thread/9efeaacdc0875e6d/7ce06f2ec8a78f36#7ce06f2ec8a78f36
Regards,
Enrique Martinez
Sr. Software Consultant|||Hi Enrique,
Thanks your replay and i do have .NET 2.0 installed. I feel like its
security issue.
What is security context of .NETservice account (NT
Authority\NetworkService)? and how do you confiure this account for web
service identity?
"EMartinez" wrote:
> On Apr 27, 2:24 pm, Karen Chen <KarenC...@.discussions.microsoft.com>
> wrote:
> > We installed sql 2005 server and reporting services (standard edition) on
> > window2003 with sp1 and IIS 6.0 is running on it as well. I am in local
> > admin and got error when i try to connect report server:
> > Cannot execute a program. The command being executed was
> > "C:\WINNT\Microsoft.NET\Framework\v2.0.50727\csc.exe" /noconfig /fullpaths
> > @."C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
> > Files\reports$sql2005\47980326\bf0ad169\lzwjfwcj.cmdline".
> > Description: An unhandled exception occurred during the execution of the
> > current web request. Please review the stack trace for more information about
> > the error and where it originated in the code.
> >
> > Exception Details: System.Runtime.InteropServices.ExternalException: Cannot
> > execute a program. The command being executed was
> > "C:\WINNT\Microsoft.NET\Framework\v2.0.50727\csc.exe" /noconfig /fullpaths
> > @."C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
> > Files\reports$sql2005\47980326\bf0ad169\lzwjfwcj.cmdline".
> >
> > Source Error:
> > An unhandled exception was generated during the execution of the current web
> > request. Information regarding the origin and location of the exception can
> > be identified using the exception stack trace below.
> >
> > anyone knows about this and thanks alot for a help
> >
> > Karen,
>
> Please refer to my previous post at:
> http://groups.google.com/group/microsoft.public.sqlserver.reportingsvcs/browse_thread/thread/9efeaacdc0875e6d/7ce06f2ec8a78f36#7ce06f2ec8a78f36
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>|||Hi Enrique,
Thanks your replay and we do have .Net 2.0 installed. I feel like that this
problem related to security issue.
How do you configure your web service account (NT Authoriry/NetworkServices)
?
Karen,
"EMartinez" wrote:
> On Apr 27, 2:24 pm, Karen Chen <KarenC...@.discussions.microsoft.com>
> wrote:
> > We installed sql 2005 server and reporting services (standard edition) on
> > window2003 with sp1 and IIS 6.0 is running on it as well. I am in local
> > admin and got error when i try to connect report server:
> > Cannot execute a program. The command being executed was
> > "C:\WINNT\Microsoft.NET\Framework\v2.0.50727\csc.exe" /noconfig /fullpaths
> > @."C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
> > Files\reports$sql2005\47980326\bf0ad169\lzwjfwcj.cmdline".
> > Description: An unhandled exception occurred during the execution of the
> > current web request. Please review the stack trace for more information about
> > the error and where it originated in the code.
> >
> > Exception Details: System.Runtime.InteropServices.ExternalException: Cannot
> > execute a program. The command being executed was
> > "C:\WINNT\Microsoft.NET\Framework\v2.0.50727\csc.exe" /noconfig /fullpaths
> > @."C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
> > Files\reports$sql2005\47980326\bf0ad169\lzwjfwcj.cmdline".
> >
> > Source Error:
> > An unhandled exception was generated during the execution of the current web
> > request. Information regarding the origin and location of the exception can
> > be identified using the exception stack trace below.
> >
> > anyone knows about this and thanks alot for a help
> >
> > Karen,
>
> Please refer to my previous post at:
> http://groups.google.com/group/microsoft.public.sqlserver.reportingsvcs/browse_thread/thread/9efeaacdc0875e6d/7ce06f2ec8a78f36#7ce06f2ec8a78f36
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>
Tuesday, March 27, 2012
cant comm with RS
Error says...
Unable to communicate with report server. Please verify that the report
server is operational.
The report server service is running. I rebooted after installing sp1.
Any ideas?
Thanks,
GaryVerify that you can access http://<machinename>/ReportServer. If you can,
make sure this URL is specified in the config file of Report Manager
(RSWebApplication.config).
--
Dmitry Vasilevsky, SQL Server Reporting Services Developer
This posting is provided "AS IS" with no warranties, and confers no rights.
--
---
"Gary D." <Dean@.nospam.com> wrote in message
news:#IQgxtIhEHA.140@.TK2MSFTNGP12.phx.gbl...
> After installing SP1 Report Manager can't communicate with Report Server.
> Error says...
> Unable to communicate with report server. Please verify that the report
> server is operational.
> The report server service is running. I rebooted after installing sp1.
> Any ideas?
> Thanks,
> Gary
>
Can't clean buffer cache
Hi,
My problem is that I cannot completely clean buffer cache on SQL Server 2005 version 9.00.2047.00 (probably SP1).
Right after I run DBCC DROPCLEANBUFFERS in the context of my database (this is development server, and so far I am only the one who is working with a particular database), I run a script that quetries sys.dm_os_buffer_descriptors view also from the context of my database to make sure that the buffer cache is really clean. However it shows large number of entries totalling 42 MB.
I ran both DBCC an the script in the past too, and it always showed nothing in the results, that means that buffers were really clean. The reason why I am running this is for benchmarking of existing and new application.
Does anybody have any idea, suggestions, how to troubleshoot this issue ? I already closed all connections to this database, but rebooting the server is not an option since other people are also working on it.
Thanks
BoL (link) does suggest issuing a CHECKPOINT before the DBCC DROPCLEANBUFFERS, have you tried that?|||Hi Mark
Moffs suggestion is correct, you will need to run the CHECKPOINT command.
Checkpoint all the databases that you want to have buffers to cold and then run the dbcc command.
I don't think you can get rid of all the buffers from the sysdatabases.
Could you please post the output of the following command once you have completed the checkpoint and dbcc.
Code Snippet
select distinct db_name(database_id) from sys.dm_os_buffer_descriptors
Jag
Can't change TCP Port using configuration manager for x64 SQL 2005 SP1 virtual instance
Hi, I hope someone can help me! I changed the TCP port that the default instance of SQL 2005 x64 SP1 is listening on and now SQL server won't start as the port is being used - no problem I say to myself, I'll just change it again, however I can't!
My problem is that I can not change the TCP Port back again using Configuration Manager - no matter what values I put in, after a restart of the instance it comes up with this in the IP Addresses tab for TCP/IP Properties and SQL Server won't start:
IP1
Active Yes
Enabled No
IP Address aaa.bbb.ccc.111
TCP Dynamic Ports
TCP Port 0
IP2
Active Yes
Enabled No
IP Address aaa.bbb.ccc.222
TCP Dynamic Ports
TCP Port 0
IP3
Active Yes
Enabled No
IP Address aaa.bbb.ccc.333
TCP Dynamic Ports
TCP Port 0
IP4
Active Yes
Enabled No
IP Address 10.1.1.1
TCP Dynamic Ports
TCP Port 0
IP5
Active Yes
Enabled No
IP Address 127.0.0.1
TCP Dynamic Ports
TCP Port 0
IPALL
TCP Dynamic Ports 2020
TCP Port 2020
Interestingly, the ip address that the server is listening on aaa.bbb.ccc.444 is not reported in the list of IP addresses in the configuration manager for this instance, yet it is when I view the available IP addresses for the other two instances - is this significant?
I have tried failing to the other node, changing it there, changing it at the console and also while logged onto the the virtual machine remote desktop, rebooting both nodes, etc, etc. There are two other instances on this cluster that are still working fine but I hvae not attempted to change the TCP ports they listen on.
I used the same method to change this default instance as I did for a named instance on a similarly configured cluster and it worked fine. How to fix this?
Regards, Mike
2007-02-27 12:03:17.69 Server Server is listening on [ aaa.bbb.ccc.444<ipv4> 2020].
2007-02-27 12:03:17.71 spid9s Starting up database 'tempdb'.
2007-02-27 12:03:17.72 Server Error: 26023, Severity: 16, State: 1.
2007-02-27 12:03:17.72 Server Server TCP provider failed to listen on [ aaa.bbb.ccc.444<ipv4> 2020]. Tcp port is already in use.
2007-02-27 12:03:17.75 Server Error: 17182, Severity: 16, State: 1.
2007-02-27 12:03:17.75 Server TDSSNIClient initialization failed with error 0x2740, status code 0xa.
2007-02-27 12:03:17.75 Server Error: 17182, Severity: 16, State: 1.
2007-02-27 12:03:17.75 Server TDSSNIClient initialization failed with error 0x2740, status code 0x1.
2007-02-27 12:03:17.75 Server Error: 17826, Severity: 18, State: 3.
2007-02-27 12:03:17.75 Server 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.
2007-02-27 12:03:17.77 Server Error: 17120, Severity: 16, State: 1.
2007-02-27 12:03:17.77 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
BWAHAHAHAHAHAHA!!!!! The same thing happened to me today! What a nightmare! I came about 10min away from nuking my virtual server instance and restoring 50+ databases. It was supposed to be such a simple change... I even tested it on a non-clustered box first. Oh well.
I had *exactly* the same setup as you, except 32bit. I think the problem was that I made the change on my passive node. My cluster has multiple instances spread over all nodes, but the virtual instance I was changing wasn't changed on the active node. I think that's what did me in.
In my situation, the IP settings I ented in caused the SQL Server instance to not start (too lazy to check the actual error at the moment). What happens is that the cluster service is configured to replicate the registry settings that govern the TCP/IP paramenters. If you edit the parameters incorrectly (or at least the way I did) then the cluster service continues to replicate those parameters to all nodes. Mind you, I used the SSCM too! The registry replication occurs when the cluster group changes nodes. If the SQL Server service does not start, then the cluster quorum logs never get cleared. In other words, the cluster doesn't think the registry params got applied correctly. No matter what you do to the registry on each node, the cluster quorum logs will continue to apply the replicated settings until SQL starts successfully (which never happens).
To fix it, I had to stop MSCS from replicating the bad registry params so that I could manually rebuild them. Here's how I did it, YMMV:
0. (I forgot a step) Set your broken SQL instance cluster resource to not restart automatically in MSCS
1. Stop cluster service on all nodes
2. Locate the SQL Server instance cluster resource you're having issues with here: HKLM\Cluster\Resources
Change the following parameter from this:
Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER
to this:
Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER\CurrentVersion
on all nodes
3. Fix the following registry branch on all nodes to what they were before (use your other instances as a guide if necessary):
Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER\supersocketnetlib\TCP
4. Start the cluster service on all nodes.
5. SQL Server will not start because you've messed with the registry replication params. (but it'll be a different error than before)
6. Move this cluster group to all nodes and let it fail on all nodes.
6b. Verify that the TCP/IP parameters are still good on all nodes.
7. Take your group completely offline.
8. Revert the registry replication changes you made in step 2 back to what they should be.
9. Clean up Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER\CurrentVersion. (It'll be messed up from the forced registry replication. Do this on all nodes.
10. cycle the SQL browser service on all nodes for good measure.
11. Bring your broken SQL instance back to life. I had to cycle SQL Browser one more time while I was doing this.
12. Verify that the SQL instance comes back on all nodes.
This worked for me. Good luck. Oh, and for my gratification, how about you try changing the IP address parameters from the Active node using SSCM while SQL is up? Let me know it if works :) and I'll attempt it on my cluster again.
-EDF
This sucks Beavis.
|||Thanks EDF. This looks very promising. I actually made my changes while RDP'd to the virtual instance name so it must have been the active node but maybe making the change through Remote Desktop stuffed it. I'll give it a go tomorrow and try my IP config changes again from the active node at the console and let everyone know how it goes. Thanks again.|||I tried the above changes but it did not help. I am going to raise a call with MS Support and I'll post the resolution.|||
Gengleman, did either of you successfully change the IP address of the cluster? We are currently attempting this and although I did it once before I think I got lucky. I'd love to see the steps followed.
UJ
|||Yeah, I did. It turns out that "Listen on All IP Addresses" *really* means "Listen on All IP Addresses in the cluster group". Move all your SQL instances to one node. Log into that node and start the IP binding configuration tool, SSCM. Leave the entry for "listen all"=Yes (totally against all that is good & right in me...). I wanted all my SQL instances to listen on the same port (2048), but diff IP addresses. On the IP Addresses tab, I set all my IP addresses entries to Enabled=No. At the bottom, I set IPAll entry so that TCP Dynamic Ports was NULL (not 0) and TCP Port=2048. On start up, each SQL instance then only attempts to bind port 2048 to it's own IP address. Certainly NOT what I would have expected, but I suppose it makes sense.|||Hi, I was trying to change the port, not the IP address, when somehow it got screwed up - I guess I mis-typed something. I ended up calling in PSS and they fixed it for me as I couldn't reproduce the fix that fischere suggested. It is very easy to screw up your TCP/IP config with the SSCM - the MS tech used it to corrupt his installation to reproduce my problem so it would be a good idea to play around with it on an environment that isn't important first and then make sure you follow the process exactly on your other instances.
If you end up screwing up the instance (by changing IP addresses, ports, etc) so that it won't start, you can reset it back to what it was using the Cluster Server Recovery Utility (ClusterRecovery.exe) which is available for download from the MS website. It's main purpose seems to be to recover from failed drives, but it has the ability to override the registry entries that cluster services wants to apply to a node using the "checkpoint" option. This allows you to overcome the problem of not being able to reset the values that the SSCM tries to write to the registry on each node because when you try and bring an instance on line or fail to another node the settings get restored from cluster services as fischere points out. To fix a failed instance using this tool, follow these steps:
1. move the failed instance to a node
2. change the registry settings to what they should be on that node, eg HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer\SuperSocketNetLib\Tcp\IPAll
3. checkpoint the cluster using the tool on that node
4. bring the instance on line
5. repeat this process on each node.
I hope this helps someone else!
|||Thanks for posting this solution. It worked like a charm for me.sql
Can't change TCP Port using configuration manager for x64 SQL 2005 SP1 virtual instance
Hi, I hope someone can help me! I changed the TCP port that the default instance of SQL 2005 x64 SP1 is listening on and now SQL server won't start as the port is being used - no problem I say to myself, I'll just change it again, however I can't!
My problem is that I can not change the TCP Port back again using Configuration Manager - no matter what values I put in, after a restart of the instance it comes up with this in the IP Addresses tab for TCP/IP Properties and SQL Server won't start:
IP1
Active Yes
Enabled No
IP Address aaa.bbb.ccc.111
TCP Dynamic Ports
TCP Port 0
IP2
Active Yes
Enabled No
IP Address aaa.bbb.ccc.222
TCP Dynamic Ports
TCP Port 0
IP3
Active Yes
Enabled No
IP Address aaa.bbb.ccc.333
TCP Dynamic Ports
TCP Port 0
IP4
Active Yes
Enabled No
IP Address 10.1.1.1
TCP Dynamic Ports
TCP Port 0
IP5
Active Yes
Enabled No
IP Address 127.0.0.1
TCP Dynamic Ports
TCP Port 0
IPALL
TCP Dynamic Ports 2020
TCP Port 2020
Interestingly, the ip address that the server is listening on aaa.bbb.ccc.444 is not reported in the list of IP addresses in the configuration manager for this instance, yet it is when I view the available IP addresses for the other two instances - is this significant?
I have tried failing to the other node, changing it there, changing it at the console and also while logged onto the the virtual machine remote desktop, rebooting both nodes, etc, etc. There are two other instances on this cluster that are still working fine but I hvae not attempted to change the TCP ports they listen on.
I used the same method to change this default instance as I did for a named instance on a similarly configured cluster and it worked fine. How to fix this?
Regards, Mike
2007-02-27 12:03:17.69 Server Server is listening on [ aaa.bbb.ccc.444<ipv4> 2020].
2007-02-27 12:03:17.71 spid9s Starting up database 'tempdb'.
2007-02-27 12:03:17.72 Server Error: 26023, Severity: 16, State: 1.
2007-02-27 12:03:17.72 Server Server TCP provider failed to listen on [ aaa.bbb.ccc.444<ipv4> 2020]. Tcp port is already in use.
2007-02-27 12:03:17.75 Server Error: 17182, Severity: 16, State: 1.
2007-02-27 12:03:17.75 Server TDSSNIClient initialization failed with error 0x2740, status code 0xa.
2007-02-27 12:03:17.75 Server Error: 17182, Severity: 16, State: 1.
2007-02-27 12:03:17.75 Server TDSSNIClient initialization failed with error 0x2740, status code 0x1.
2007-02-27 12:03:17.75 Server Error: 17826, Severity: 18, State: 3.
2007-02-27 12:03:17.75 Server 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.
2007-02-27 12:03:17.77 Server Error: 17120, Severity: 16, State: 1.
2007-02-27 12:03:17.77 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
BWAHAHAHAHAHAHA!!!!! The same thing happened to me today! What a nightmare! I came about 10min away from nuking my virtual server instance and restoring 50+ databases. It was supposed to be such a simple change... I even tested it on a non-clustered box first. Oh well.
I had *exactly* the same setup as you, except 32bit. I think the problem was that I made the change on my passive node. My cluster has multiple instances spread over all nodes, but the virtual instance I was changing wasn't changed on the active node. I think that's what did me in.
In my situation, the IP settings I ented in caused the SQL Server instance to not start (too lazy to check the actual error at the moment). What happens is that the cluster service is configured to replicate the registry settings that govern the TCP/IP paramenters. If you edit the parameters incorrectly (or at least the way I did) then the cluster service continues to replicate those parameters to all nodes. Mind you, I used the SSCM too! The registry replication occurs when the cluster group changes nodes. If the SQL Server service does not start, then the cluster quorum logs never get cleared. In other words, the cluster doesn't think the registry params got applied correctly. No matter what you do to the registry on each node, the cluster quorum logs will continue to apply the replicated settings until SQL starts successfully (which never happens).
To fix it, I had to stop MSCS from replicating the bad registry params so that I could manually rebuild them. Here's how I did it, YMMV:
0. (I forgot a step) Set your broken SQL instance cluster resource to not restart automatically in MSCS
1. Stop cluster service on all nodes
2. Locate the SQL Server instance cluster resource you're having issues with here: HKLM\Cluster\Resources
Change the following parameter from this:
Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER
to this:
Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER\CurrentVersion
on all nodes
3. Fix the following registry branch on all nodes to what they were before (use your other instances as a guide if necessary):
Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER\supersocketnetlib\TCP
4. Start the cluster service on all nodes.
5. SQL Server will not start because you've messed with the registry replication params. (but it'll be a different error than before)
6. Move this cluster group to all nodes and let it fail on all nodes.
6b. Verify that the TCP/IP parameters are still good on all nodes.
7. Take your group completely offline.
8. Revert the registry replication changes you made in step 2 back to what they should be.
9. Clean up Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER\CurrentVersion. (It'll be messed up from the forced registry replication. Do this on all nodes.
10. cycle the SQL browser service on all nodes for good measure.
11. Bring your broken SQL instance back to life. I had to cycle SQL Browser one more time while I was doing this.
12. Verify that the SQL instance comes back on all nodes.
This worked for me. Good luck. Oh, and for my gratification, how about you try changing the IP address parameters from the Active node using SSCM while SQL is up? Let me know it if works :) and I'll attempt it on my cluster again.
-EDF
This sucks Beavis.
|||Thanks EDF. This looks very promising. I actually made my changes while RDP'd to the virtual instance name so it must have been the active node but maybe making the change through Remote Desktop stuffed it. I'll give it a go tomorrow and try my IP config changes again from the active node at the console and let everyone know how it goes. Thanks again.|||I tried the above changes but it did not help. I am going to raise a call with MS Support and I'll post the resolution.|||
Gengleman, did either of you successfully change the IP address of the cluster? We are currently attempting this and although I did it once before I think I got lucky. I'd love to see the steps followed.
UJ
|||Yeah, I did. It turns out that "Listen on All IP Addresses" *really* means "Listen on All IP Addresses in the cluster group". Move all your SQL instances to one node. Log into that node and start the IP binding configuration tool, SSCM. Leave the entry for "listen all"=Yes (totally against all that is good & right in me...). I wanted all my SQL instances to listen on the same port (2048), but diff IP addresses. On the IP Addresses tab, I set all my IP addresses entries to Enabled=No. At the bottom, I set IPAll entry so that TCP Dynamic Ports was NULL (not 0) and TCP Port=2048. On start up, each SQL instance then only attempts to bind port 2048 to it's own IP address. Certainly NOT what I would have expected, but I suppose it makes sense.|||Hi, I was trying to change the port, not the IP address, when somehow it got screwed up - I guess I mis-typed something. I ended up calling in PSS and they fixed it for me as I couldn't reproduce the fix that fischere suggested. It is very easy to screw up your TCP/IP config with the SSCM - the MS tech used it to corrupt his installation to reproduce my problem so it would be a good idea to play around with it on an environment that isn't important first and then make sure you follow the process exactly on your other instances.
If you end up screwing up the instance (by changing IP addresses, ports, etc) so that it won't start, you can reset it back to what it was using the Cluster Server Recovery Utility (ClusterRecovery.exe) which is available for download from the MS website. It's main purpose seems to be to recover from failed drives, but it has the ability to override the registry entries that cluster services wants to apply to a node using the "checkpoint" option. This allows you to overcome the problem of not being able to reset the values that the SSCM tries to write to the registry on each node because when you try and bring an instance on line or fail to another node the settings get restored from cluster services as fischere points out. To fix a failed instance using this tool, follow these steps:
1. move the failed instance to a node
2. change the registry settings to what they should be on that node, eg HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer\SuperSocketNetLib\Tcp\IPAll
3. checkpoint the cluster using the tool on that node
4. bring the instance on line
5. repeat this process on each node.
I hope this helps someone else!
|||Thanks for posting this solution. It worked like a charm for me.
Can't change TCP Port using configuration manager for x64 SQL 2005 SP1 virtual instance
Hi, I hope someone can help me! I changed the TCP port that the default instance of SQL 2005 x64 SP1 is listening on and now SQL server won't start as the port is being used - no problem I say to myself, I'll just change it again, however I can't!
My problem is that I can not change the TCP Port back again using Configuration Manager - no matter what values I put in, after a restart of the instance it comes up with this in the IP Addresses tab for TCP/IP Properties and SQL Server won't start:
IP1
Active Yes
Enabled No
IP Address aaa.bbb.ccc.111
TCP Dynamic Ports
TCP Port 0
IP2
Active Yes
Enabled No
IP Address aaa.bbb.ccc.222
TCP Dynamic Ports
TCP Port 0
IP3
Active Yes
Enabled No
IP Address aaa.bbb.ccc.333
TCP Dynamic Ports
TCP Port 0
IP4
Active Yes
Enabled No
IP Address 10.1.1.1
TCP Dynamic Ports
TCP Port 0
IP5
Active Yes
Enabled No
IP Address 127.0.0.1
TCP Dynamic Ports
TCP Port 0
IPALL
TCP Dynamic Ports 2020
TCP Port 2020
Interestingly, the ip address that the server is listening on aaa.bbb.ccc.444 is not reported in the list of IP addresses in the configuration manager for this instance, yet it is when I view the available IP addresses for the other two instances - is this significant?
I have tried failing to the other node, changing it there, changing it at the console and also while logged onto the the virtual machine remote desktop, rebooting both nodes, etc, etc. There are two other instances on this cluster that are still working fine but I hvae not attempted to change the TCP ports they listen on.
I used the same method to change this default instance as I did for a named instance on a similarly configured cluster and it worked fine. How to fix this?
Regards, Mike
2007-02-27 12:03:17.69 Server Server is listening on [ aaa.bbb.ccc.444<ipv4> 2020].
2007-02-27 12:03:17.71 spid9s Starting up database 'tempdb'.
2007-02-27 12:03:17.72 Server Error: 26023, Severity: 16, State: 1.
2007-02-27 12:03:17.72 Server Server TCP provider failed to listen on [ aaa.bbb.ccc.444<ipv4> 2020]. Tcp port is already in use.
2007-02-27 12:03:17.75 Server Error: 17182, Severity: 16, State: 1.
2007-02-27 12:03:17.75 Server TDSSNIClient initialization failed with error 0x2740, status code 0xa.
2007-02-27 12:03:17.75 Server Error: 17182, Severity: 16, State: 1.
2007-02-27 12:03:17.75 Server TDSSNIClient initialization failed with error 0x2740, status code 0x1.
2007-02-27 12:03:17.75 Server Error: 17826, Severity: 18, State: 3.
2007-02-27 12:03:17.75 Server 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.
2007-02-27 12:03:17.77 Server Error: 17120, Severity: 16, State: 1.
2007-02-27 12:03:17.77 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
BWAHAHAHAHAHAHA!!!!! The same thing happened to me today! What a nightmare! I came about 10min away from nuking my virtual server instance and restoring 50+ databases. It was supposed to be such a simple change... I even tested it on a non-clustered box first. Oh well.
I had *exactly* the same setup as you, except 32bit. I think the problem was that I made the change on my passive node. My cluster has multiple instances spread over all nodes, but the virtual instance I was changing wasn't changed on the active node. I think that's what did me in.
In my situation, the IP settings I ented in caused the SQL Server instance to not start (too lazy to check the actual error at the moment). What happens is that the cluster service is configured to replicate the registry settings that govern the TCP/IP paramenters. If you edit the parameters incorrectly (or at least the way I did) then the cluster service continues to replicate those parameters to all nodes. Mind you, I used the SSCM too! The registry replication occurs when the cluster group changes nodes. If the SQL Server service does not start, then the cluster quorum logs never get cleared. In other words, the cluster doesn't think the registry params got applied correctly. No matter what you do to the registry on each node, the cluster quorum logs will continue to apply the replicated settings until SQL starts successfully (which never happens).
To fix it, I had to stop MSCS from replicating the bad registry params so that I could manually rebuild them. Here's how I did it, YMMV:
0. (I forgot a step) Set your broken SQL instance cluster resource to not restart automatically in MSCS
1. Stop cluster service on all nodes
2. Locate the SQL Server instance cluster resource you're having issues with here: HKLM\Cluster\Resources
Change the following parameter from this:
Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER
to this:
Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER\CurrentVersion
on all nodes
3. Fix the following registry branch on all nodes to what they were before (use your other instances as a guide if necessary):
Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER\supersocketnetlib\TCP
4. Start the cluster service on all nodes.
5. SQL Server will not start because you've messed with the registry replication params. (but it'll be a different error than before)
6. Move this cluster group to all nodes and let it fail on all nodes.
6b. Verify that the TCP/IP parameters are still good on all nodes.
7. Take your group completely offline.
8. Revert the registry replication changes you made in step 2 back to what they should be.
9. Clean up Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER\CurrentVersion. (It'll be messed up from the forced registry replication. Do this on all nodes.
10. cycle the SQL browser service on all nodes for good measure.
11. Bring your broken SQL instance back to life. I had to cycle SQL Browser one more time while I was doing this.
12. Verify that the SQL instance comes back on all nodes.
This worked for me. Good luck. Oh, and for my gratification, how about you try changing the IP address parameters from the Active node using SSCM while SQL is up? Let me know it if works :) and I'll attempt it on my cluster again.
-EDF
This sucks Beavis.
|||Thanks EDF. This looks very promising. I actually made my changes while RDP'd to the virtual instance name so it must have been the active node but maybe making the change through Remote Desktop stuffed it. I'll give it a go tomorrow and try my IP config changes again from the active node at the console and let everyone know how it goes. Thanks again.|||I tried the above changes but it did not help. I am going to raise a call with MS Support and I'll post the resolution.|||
Gengleman, did either of you successfully change the IP address of the cluster? We are currently attempting this and although I did it once before I think I got lucky. I'd love to see the steps followed.
UJ
|||Yeah, I did. It turns out that "Listen on All IP Addresses" *really* means "Listen on All IP Addresses in the cluster group". Move all your SQL instances to one node. Log into that node and start the IP binding configuration tool, SSCM. Leave the entry for "listen all"=Yes (totally against all that is good & right in me...). I wanted all my SQL instances to listen on the same port (2048), but diff IP addresses. On the IP Addresses tab, I set all my IP addresses entries to Enabled=No. At the bottom, I set IPAll entry so that TCP Dynamic Ports was NULL (not 0) and TCP Port=2048. On start up, each SQL instance then only attempts to bind port 2048 to it's own IP address. Certainly NOT what I would have expected, but I suppose it makes sense.|||Hi, I was trying to change the port, not the IP address, when somehow it got screwed up - I guess I mis-typed something. I ended up calling in PSS and they fixed it for me as I couldn't reproduce the fix that fischere suggested. It is very easy to screw up your TCP/IP config with the SSCM - the MS tech used it to corrupt his installation to reproduce my problem so it would be a good idea to play around with it on an environment that isn't important first and then make sure you follow the process exactly on your other instances.
If you end up screwing up the instance (by changing IP addresses, ports, etc) so that it won't start, you can reset it back to what it was using the Cluster Server Recovery Utility (ClusterRecovery.exe) which is available for download from the MS website. It's main purpose seems to be to recover from failed drives, but it has the ability to override the registry entries that cluster services wants to apply to a node using the "checkpoint" option. This allows you to overcome the problem of not being able to reset the values that the SSCM tries to write to the registry on each node because when you try and bring an instance on line or fail to another node the settings get restored from cluster services as fischere points out. To fix a failed instance using this tool, follow these steps:
1. move the failed instance to a node
2. change the registry settings to what they should be on that node, eg HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer\SuperSocketNetLib\Tcp\IPAll
3. checkpoint the cluster using the tool on that node
4. bring the instance on line
5. repeat this process on each node.
I hope this helps someone else!
|||Thanks for posting this solution. It worked like a charm for me.
Can't change TCP Port using configuration manager for x64 SQL 2005 SP1 virtual instance
Hi, I hope someone can help me! I changed the TCP port that the default instance of SQL 2005 x64 SP1 is listening on and now SQL server won't start as the port is being used - no problem I say to myself, I'll just change it again, however I can't!
My problem is that I can not change the TCP Port back again using Configuration Manager - no matter what values I put in, after a restart of the instance it comes up with this in the IP Addresses tab for TCP/IP Properties and SQL Server won't start:
IP1
Active Yes
Enabled No
IP Address aaa.bbb.ccc.111
TCP Dynamic Ports
TCP Port 0
IP2
Active Yes
Enabled No
IP Address aaa.bbb.ccc.222
TCP Dynamic Ports
TCP Port 0
IP3
Active Yes
Enabled No
IP Address aaa.bbb.ccc.333
TCP Dynamic Ports
TCP Port 0
IP4
Active Yes
Enabled No
IP Address 10.1.1.1
TCP Dynamic Ports
TCP Port 0
IP5
Active Yes
Enabled No
IP Address 127.0.0.1
TCP Dynamic Ports
TCP Port 0
IPALL
TCP Dynamic Ports 2020
TCP Port 2020
Interestingly, the ip address that the server is listening on aaa.bbb.ccc.444 is not reported in the list of IP addresses in the configuration manager for this instance, yet it is when I view the available IP addresses for the other two instances - is this significant?
I have tried failing to the other node, changing it there, changing it at the console and also while logged onto the the virtual machine remote desktop, rebooting both nodes, etc, etc. There are two other instances on this cluster that are still working fine but I hvae not attempted to change the TCP ports they listen on.
I used the same method to change this default instance as I did for a named instance on a similarly configured cluster and it worked fine. How to fix this?
Regards, Mike
2007-02-27 12:03:17.69 Server Server is listening on [ aaa.bbb.ccc.444<ipv4> 2020].
2007-02-27 12:03:17.71 spid9s Starting up database 'tempdb'.
2007-02-27 12:03:17.72 Server Error: 26023, Severity: 16, State: 1.
2007-02-27 12:03:17.72 Server Server TCP provider failed to listen on [ aaa.bbb.ccc.444<ipv4> 2020]. Tcp port is already in use.
2007-02-27 12:03:17.75 Server Error: 17182, Severity: 16, State: 1.
2007-02-27 12:03:17.75 Server TDSSNIClient initialization failed with error 0x2740, status code 0xa.
2007-02-27 12:03:17.75 Server Error: 17182, Severity: 16, State: 1.
2007-02-27 12:03:17.75 Server TDSSNIClient initialization failed with error 0x2740, status code 0x1.
2007-02-27 12:03:17.75 Server Error: 17826, Severity: 18, State: 3.
2007-02-27 12:03:17.75 Server 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.
2007-02-27 12:03:17.77 Server Error: 17120, Severity: 16, State: 1.
2007-02-27 12:03:17.77 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
BWAHAHAHAHAHAHA!!!!! The same thing happened to me today! What a nightmare! I came about 10min away from nuking my virtual server instance and restoring 50+ databases. It was supposed to be such a simple change... I even tested it on a non-clustered box first. Oh well.
I had *exactly* the same setup as you, except 32bit. I think the problem was that I made the change on my passive node. My cluster has multiple instances spread over all nodes, but the virtual instance I was changing wasn't changed on the active node. I think that's what did me in.
In my situation, the IP settings I ented in caused the SQL Server instance to not start (too lazy to check the actual error at the moment). What happens is that the cluster service is configured to replicate the registry settings that govern the TCP/IP paramenters. If you edit the parameters incorrectly (or at least the way I did) then the cluster service continues to replicate those parameters to all nodes. Mind you, I used the SSCM too! The registry replication occurs when the cluster group changes nodes. If the SQL Server service does not start, then the cluster quorum logs never get cleared. In other words, the cluster doesn't think the registry params got applied correctly. No matter what you do to the registry on each node, the cluster quorum logs will continue to apply the replicated settings until SQL starts successfully (which never happens).
To fix it, I had to stop MSCS from replicating the bad registry params so that I could manually rebuild them. Here's how I did it, YMMV:
0. (I forgot a step) Set your broken SQL instance cluster resource to not restart automatically in MSCS
1. Stop cluster service on all nodes
2. Locate the SQL Server instance cluster resource you're having issues with here: HKLM\Cluster\Resources
Change the following parameter from this:
Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER
to this:
Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER\CurrentVersion
on all nodes
3. Fix the following registry branch on all nodes to what they were before (use your other instances as a guide if necessary):
Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER\supersocketnetlib\TCP
4. Start the cluster service on all nodes.
5. SQL Server will not start because you've messed with the registry replication params. (but it'll be a different error than before)
6. Move this cluster group to all nodes and let it fail on all nodes.
6b. Verify that the TCP/IP parameters are still good on all nodes.
7. Take your group completely offline.
8. Revert the registry replication changes you made in step 2 back to what they should be.
9. Clean up Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER\CurrentVersion. (It'll be messed up from the forced registry replication. Do this on all nodes.
10. cycle the SQL browser service on all nodes for good measure.
11. Bring your broken SQL instance back to life. I had to cycle SQL Browser one more time while I was doing this.
12. Verify that the SQL instance comes back on all nodes.
This worked for me. Good luck. Oh, and for my gratification, how about you try changing the IP address parameters from the Active node using SSCM while SQL is up? Let me know it if works :) and I'll attempt it on my cluster again.
-EDF
This sucks Beavis.
|||Thanks EDF. This looks very promising. I actually made my changes while RDP'd to the virtual instance name so it must have been the active node but maybe making the change through Remote Desktop stuffed it. I'll give it a go tomorrow and try my IP config changes again from the active node at the console and let everyone know how it goes. Thanks again.|||I tried the above changes but it did not help. I am going to raise a call with MS Support and I'll post the resolution.|||
Gengleman, did either of you successfully change the IP address of the cluster? We are currently attempting this and although I did it once before I think I got lucky. I'd love to see the steps followed.
UJ
|||Yeah, I did. It turns out that "Listen on All IP Addresses" *really* means "Listen on All IP Addresses in the cluster group". Move all your SQL instances to one node. Log into that node and start the IP binding configuration tool, SSCM. Leave the entry for "listen all"=Yes (totally against all that is good & right in me...). I wanted all my SQL instances to listen on the same port (2048), but diff IP addresses. On the IP Addresses tab, I set all my IP addresses entries to Enabled=No. At the bottom, I set IPAll entry so that TCP Dynamic Ports was NULL (not 0) and TCP Port=2048. On start up, each SQL instance then only attempts to bind port 2048 to it's own IP address. Certainly NOT what I would have expected, but I suppose it makes sense.|||Hi, I was trying to change the port, not the IP address, when somehow it got screwed up - I guess I mis-typed something. I ended up calling in PSS and they fixed it for me as I couldn't reproduce the fix that fischere suggested. It is very easy to screw up your TCP/IP config with the SSCM - the MS tech used it to corrupt his installation to reproduce my problem so it would be a good idea to play around with it on an environment that isn't important first and then make sure you follow the process exactly on your other instances.
If you end up screwing up the instance (by changing IP addresses, ports, etc) so that it won't start, you can reset it back to what it was using the Cluster Server Recovery Utility (ClusterRecovery.exe) which is available for download from the MS website. It's main purpose seems to be to recover from failed drives, but it has the ability to override the registry entries that cluster services wants to apply to a node using the "checkpoint" option. This allows you to overcome the problem of not being able to reset the values that the SSCM tries to write to the registry on each node because when you try and bring an instance on line or fail to another node the settings get restored from cluster services as fischere points out. To fix a failed instance using this tool, follow these steps:
1. move the failed instance to a node
2. change the registry settings to what they should be on that node, eg HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer\SuperSocketNetLib\Tcp\IPAll
3. checkpoint the cluster using the tool on that node
4. bring the instance on line
5. repeat this process on each node.
I hope this helps someone else!
|||Thanks for posting this solution. It worked like a charm for me.
Can't change language in server properties
Hi
I'm running SQL Server 2005 Express SP1 on a Danish PC, and I need to have the server language set to Danish.
However, when I want to change the language in server properties (the current language is English (US) using Management Studio Express, I can't - all of the properties on the General page are greyed out.
I know that the SQL Server Express SP1 download is available in several languages (Danish not being one of them) - does that mean that I can't get my SQL Server Express SP1 installation to "speak" Danish at all?
Please help - it's driving me up the wall.
It depends on what you mean by "speak" Danish.
If you mean you want your error messages in Danish, that won't happen. We only support a limited number of localized versions of SQL Server.
If you mean you want to have SQL to store Danish language data, we support that through unicode data types and collation order. You can read more about SQL Collation in BOL; try starting at http://msdn2.microsoft.com/en-US/library/ms143503(SQL.90).aspx for a quick overview and move on from there.
Regards,
Mike Wachal
|||I have a similar problem, my client and server use the brazilian language but the SQL Server 2005 uses English-US.
How I change the language to brazilian?
I have problems using datetime send from a application developped in Delphi.
The program woks fine dates in the months Jan, Mar, Jun, Jul, Nov and Dec
|||I have a similar problem, my client and server use the brazilian language but the SQL Server 2005 uses English-US.
How I change the language to brazilian?
I have problems using datetime send from a application developped in Delphi.
The program woks fine dates in the months Jan, Mar, Jun, Jul, Nov and Dec
procedure TForm1.BitBtn1Click(Sender: TObject);
var
i:Integer;
begin
Table1.EmptyTable;
Table1.open;
for I := 1 to 500 do
begin
Table1.Append;
Table1Teste.value:= 'Testando '+Inttostr(I);
Table1Data.Value:= Date+I;
Table1.post;
end;
ShowMessage('Terminei');
Table1.close;
end;
end.
sqlCan't change language in server properties
Hi
I'm running SQL Server 2005 Express SP1 on a Danish PC, and I need to have the server language set to Danish.
However, when I want to change the language in server properties (the current language is English (US) using Management Studio Express, I can't - all of the properties on the General page are greyed out.
I know that the SQL Server Express SP1 download is available in several languages (Danish not being one of them) - does that mean that I can't get my SQL Server Express SP1 installation to "speak" Danish at all?
Please help - it's driving me up the wall.
It depends on what you mean by "speak" Danish.
If you mean you want your error messages in Danish, that won't happen. We only support a limited number of localized versions of SQL Server.
If you mean you want to have SQL to store Danish language data, we support that through unicode data types and collation order. You can read more about SQL Collation in BOL; try starting at http://msdn2.microsoft.com/en-US/library/ms143503(SQL.90).aspx for a quick overview and move on from there.
Regards,
Mike Wachal
|||I have a similar problem, my client and server use the brazilian language but the SQL Server 2005 uses English-US.
How I change the language to brazilian?
I have problems using datetime send from a application developped in Delphi.
The program woks fine dates in the months Jan, Mar, Jun, Jul, Nov and Dec
|||I have a similar problem, my client and server use the brazilian language but the SQL Server 2005 uses English-US.
How I change the language to brazilian?
I have problems using datetime send from a application developped in Delphi.
The program woks fine dates in the months Jan, Mar, Jun, Jul, Nov and Dec
procedure TForm1.BitBtn1Click(Sender: TObject);
var
i:Integer;
begin
Table1.EmptyTable;
Table1.open;
for I := 1 to 500 do
begin
Table1.Append;
Table1Teste.value:= 'Testando '+Inttostr(I);
Table1Data.Value:= Date+I;
Table1.post;
end;
ShowMessage('Terminei');
Table1.close;
end;
end.
Tuesday, March 20, 2012
can't access named instance by it's name
Hi,
I have sql2005 sp1 active-active installation.
I've fixed the named instance port.
I can't reach it from clients with i'ts name (servername\instancename) .
I manage to rech it only by using servername, ip-port.
The sql browser has the following error:
"The configuration of the AdminConnection\TCP protocol in the SQL instance GILBOACL is not valid."
your help is appreciated!
Shahar
1. Is UPD port 1434 open?2. Does the browser service account have access to the registry key? See the following article for more info.
http://support.microsoft.com/kb/905618
Monday, March 19, 2012
Cant access (local) server
I installed the .Net Enterprise Architect and SQL Reporting Services. My SQL instance is still running, but I can't get to it through EM and SQLServerAgent won't start. When I try to start SQLServerAgent manually, it gets about halfway through the process, then shuts itself down again. I also have an MSDE instance that is not complaining at all.
I can get to the server from my applications. I can also register it in EM with the IP and get to it that way.
Here's what's in sqlagent.out:
2007-01-02 16:34:41 - ! [298] SQLServer Error: 6, Specified SQL server not found. [SQLSTATE 08001]
2007-01-02 16:34:41 - ! [298] SQLServer Error: 11004, ConnectionOpen (Connect()). [SQLSTATE 01000]
2007-01-02 16:34:41 - ! [000] Unable to connect to server '(local)'; SQLServerAgent cannot start
2007-01-02 16:34:42 - ? [098] SQLServerAgent terminated (normally)
I did confirm in the registry that the port is set to 1433. It's not blank or incorrect. I am also working with a local account that is in the administrators group. There is no AD structure at work.
Many thanks for any ideas. This one feels like a little needle in a big haystack.
EaglesYouc an't have a 2k and an msde instance both named local... one of them HAS to be a named instance. Which one is named?|||The MSDE instance is named. The SQL Server 2000 instance is local.|||what server name do you use to connect to msde?|||One question (which will lead to others..) Were the two instances (Both MSDE and SQL Server existing before all the other installs? And happily co-existing?|||Yes, the 2 instances have been happily co-existing for over a year and things have been very stable. Since it's all the SQL instances are test environment, there's quite of bit of database creation and deletion in both the SS2K and MSDE instance. I also freqently register my clients SQL servers when I'm on-site also. There is actually a third instance which is another MSDE instance. Here's a snippet of them:
(local) - SS2k WITH sp3a. Currently houses a database for Project server and several small company databases for an accounting app. This instance starts automatically. It has been in place for ever a year.
acsob- MSDE instance with several company databases for an accounting application. This instance and it's accompanying sqlserver agent start automatically. It has been in place for over year.
quickalerts - MSDE instance with an interface application to the SS2K accounting application. This instance and accompanying sqlserveragent are set to start manually and are rarely running. This instance was installed 2 weeks ago. It was running constantly during initial configuration and testing.
All these servers are test environments with very low usage. I use them to do software demos, training, and testing. There's rarely more than one user logged in to any of the servers.
Last night after I opened this thread I registered the local sql server instance using the machine IP (assigned by the DHCP server). I was able to get it using the IP address but not as (local). That brought to light another piece of possible useful info. About a month ago, I enabled the mail role on this machine so I could send mail when I'm on the road. That all worked fine with one exception. I can not send email to my own domain account. I can send email to any other domains. I can also receive email to myself that I send from my providers webmail. Not sure if this is relevant, but it's starting to feel like a dns issue somewhere.
Thanks.
Eagles|||I can now get to the the sql instance through EM. The hosts file contained the following entry:
127.0.0.1 localhost
I added this entry:
127.0.0.1 local
A network admin at a client site suggested this.
The sqlserveragent still starts and immediately shuts down.
Friday, February 24, 2012
Cannot shrink transaction log - windows 2003/sp1 and SQL 2000/SP4
This particular transaction log is about 135 GB and is filling up the hard
drive. Is there a way to force this?http://support.microsoft.com/kb/q272318/
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Sabo, Eric" wrote:
> I cannot shrink a transaction log to a database through the enterprise mmc.
> This particular transaction log is about 135 GB and is filling up the hard
> drive. Is there a way to force this?|||Mike,
Thanks for the reply but where do you run this command from. Also, what
if I have no space to backup this transaction log.
"Mike Epprecht (SQL MVP)" wrote:
> http://support.microsoft.com/kb/q272318/
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "Sabo, Eric" wrote:
> > I cannot shrink a transaction log to a database through the enterprise mmc.
> > This particular transaction log is about 135 GB and is filling up the hard
> > drive. Is there a way to force this?|||It is saying the following when I tried to shrink the database:
Cannot shrink log file 2 (XXXXXXXX_log) because all logical log files are in
use.
"Sabo, Eric" wrote:
> I cannot shrink a transaction log to a database through the enterprise mmc.
> This particular transaction log is about 135 GB and is filling up the hard
> drive. Is there a way to force this?|||Hi
OK, so I assume that you have not backuped up your transaction log, nor
require it, so put the DB in simple Recovery Mode using Enterprise Manager
(Property of the DB)
This will clear all inactive entries in the log and then you can shrink the
log,
You need to run those commands in the KB from Query Analyser.
Look up "recovery plan" in Books Online to understand how the log is used
for recovery in DR scenarios.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Sabo, Eric" wrote:
> Mike,
> Thanks for the reply but where do you run this command from. Also, what
> if I have no space to backup this transaction log.
> "Mike Epprecht (SQL MVP)" wrote:
> > http://support.microsoft.com/kb/q272318/
> > --
> > --
> > Mike Epprecht, Microsoft SQL Server MVP
> > Zurich, Switzerland
> >
> > MVP Program: http://www.microsoft.com/mvp
> >
> > Blog: http://www.msmvps.com/epprecht/
> >
> >
> >
> > "Sabo, Eric" wrote:
> >
> > > I cannot shrink a transaction log to a database through the enterprise mmc.
> > > This particular transaction log is about 135 GB and is filling up the hard
> > > drive. Is there a way to force this?|||Mike,
Thanks alot.
That worked. I restricted the growth this time so it will not fill up my
hard drive again. Thanks again!
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> OK, so I assume that you have not backuped up your transaction log, nor
> require it, so put the DB in simple Recovery Mode using Enterprise Manager
> (Property of the DB)
> This will clear all inactive entries in the log and then you can shrink the
> log,
> You need to run those commands in the KB from Query Analyser.
> Look up "recovery plan" in Books Online to understand how the log is used
> for recovery in DR scenarios.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "Sabo, Eric" wrote:
> > Mike,
> >
> > Thanks for the reply but where do you run this command from. Also, what
> > if I have no space to backup this transaction log.
> >
> > "Mike Epprecht (SQL MVP)" wrote:
> >
> > > http://support.microsoft.com/kb/q272318/
> > > --
> > > --
> > > Mike Epprecht, Microsoft SQL Server MVP
> > > Zurich, Switzerland
> > >
> > > MVP Program: http://www.microsoft.com/mvp
> > >
> > > Blog: http://www.msmvps.com/epprecht/
> > >
> > >
> > >
> > > "Sabo, Eric" wrote:
> > >
> > > > I cannot shrink a transaction log to a database through the enterprise mmc.
> > > > This particular transaction log is about 135 GB and is filling up the hard
> > > > drive. Is there a way to force this?
Cannot shrink transaction log - windows 2003/sp1 and SQL 2000/SP4
This particular transaction log is about 135 GB and is filling up the hard
drive. Is there a way to force this?
http://support.microsoft.com/kb/q272318/
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Sabo, Eric" wrote:
> I cannot shrink a transaction log to a database through the enterprise mmc.
> This particular transaction log is about 135 GB and is filling up the hard
> drive. Is there a way to force this?
|||It is saying the following when I tried to shrink the database:
Cannot shrink log file 2 (XXXXXXXX_log) because all logical log files are in
use.
"Sabo, Eric" wrote:
> I cannot shrink a transaction log to a database through the enterprise mmc.
> This particular transaction log is about 135 GB and is filling up the hard
> drive. Is there a way to force this?
Cannot shrink transaction log - windows 2003/sp1 and SQL 2000/SP4
This particular transaction log is about 135 GB and is filling up the hard
drive. Is there a way to force this?http://support.microsoft.com/kb/q272318/
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Sabo, Eric" wrote:
> I cannot shrink a transaction log to a database through the enterprise mmc
.
> This particular transaction log is about 135 GB and is filling up the hard
> drive. Is there a way to force this?|||It is saying the following when I tried to shrink the database:
Cannot shrink log file 2 (XXXXXXXX_log) because all logical log files are in
use.
"Sabo, Eric" wrote:
> I cannot shrink a transaction log to a database through the enterprise mmc
.
> This particular transaction log is about 135 GB and is filling up the hard
> drive. Is there a way to force this?
Sunday, February 19, 2012
Cannot show requested dialog Error on View Database Permissions
I am having issues with the database permissions on SQL Server Express. I downloaded the SQL Server 2005 Express Edition with Advanced Services SP1 and everytime I try to view database/schema permissions I get an error "Cannot show requested dialog." I have 3 different installs of Sql Express 2005 on different machines and they all throw the same error. The error happens in a couple locations but one way is going databases > select any database > Security > Schemas > Select and right click on a schema > permissions > and click view database permissions, I get the error message below. Does anyone else have this problem?
Thanks
Scott
===================================
Cannot show requested dialog.
===================================
Could not load file or assembly 'file:///c:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\SqlManagerUi.dll' or one of its dependencies. The system cannot find the file specified. (mscorlib)
Program Location:
at System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
at System.Reflection.Assembly.InternalLoadFrom(String assemblyFile, Evidence securityEvidence, Byte[] hashValue, AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection, StackCrawlMark& stackMark)
at System.Reflection.Assembly.LoadFrom(String assemblyFile, Evidence securityEvidence)
at System.Activator.CreateInstanceFrom(String assemblyFile, String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, Evidence securityInfo)
at System.Activator.CreateInstanceFrom(String assemblyFile, String typeName, Object[] activationAttributes)
at Microsoft.SqlServer.Management.SqlMgmt.DefaultLaunchFormHostedControlAllocator.AllocateDialog(XmlDocument initializationXml, IServiceProvider dialogServiceProvider, CDataContainer dc)
at Microsoft.SqlServer.Management.SqlMgmt.DefaultLaunchFormHostedControlAllocator.Microsoft.SqlServer.Management.SqlMgmt.ILaunchFormHostedControlAllocator.CreateDialog(XmlDocument initializationXml, IServiceProvider dialogServiceProvider)
at Microsoft.SqlServer.Management.SqlMgmt.LaunchForm.InitializeForm(XmlDocument doc, IServiceProvider provider, ISqlControlCollection control)
at Microsoft.SqlServer.Management.SqlMgmt.LaunchForm..ctor(XmlDocument doc, IServiceProvider provider)
at Microsoft.SqlServer.Management.SqlMgmt.FormLauncher.OnCreateAndShowForm(IServiceProvider serviceProvider, XmlDocument xml)
at Microsoft.SqlServer.Management.SqlMgmt.RunningFormsTable.RunningFormsTableImpl.ThreadStarter.StartThread()
Seems like a managment studio issue. I'm going to move this question to the Tools forum.
Mike
Cannot show requested dialog Error on View Database Permissions
I am having issues with the database permissions on SQL Server Express. I downloaded the SQL Server 2005 Express Edition with Advanced Services SP1 and everytime I try to view database/schema permissions I get an error "Cannot show requested dialog." I have 3 different installs of Sql Express 2005 on different machines and they all throw the same error. The error happens in a couple locations but one way is going databases > select any database > Security > Schemas > Select and right click on a schema > permissions > and click view database permissions, I get the error message below. Does anyone else have this problem?
Thanks
Scott
===================================
Cannot show requested dialog.
===================================
Could not load file or assembly 'file:///c:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\SqlManagerUi.dll' or one of its dependencies. The system cannot find the file specified. (mscorlib)
Program Location:
at System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
at System.Reflection.Assembly.InternalLoadFrom(String assemblyFile, Evidence securityEvidence, Byte[] hashValue, AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection, StackCrawlMark& stackMark)
at System.Reflection.Assembly.LoadFrom(String assemblyFile, Evidence securityEvidence)
at System.Activator.CreateInstanceFrom(String assemblyFile, String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, Evidence securityInfo)
at System.Activator.CreateInstanceFrom(String assemblyFile, String typeName, Object[] activationAttributes)
at Microsoft.SqlServer.Management.SqlMgmt.DefaultLaunchFormHostedControlAllocator.AllocateDialog(XmlDocument initializationXml, IServiceProvider dialogServiceProvider, CDataContainer dc)
at Microsoft.SqlServer.Management.SqlMgmt.DefaultLaunchFormHostedControlAllocator.Microsoft.SqlServer.Management.SqlMgmt.ILaunchFormHostedControlAllocator.CreateDialog(XmlDocument initializationXml, IServiceProvider dialogServiceProvider)
at Microsoft.SqlServer.Management.SqlMgmt.LaunchForm.InitializeForm(XmlDocument doc, IServiceProvider provider, ISqlControlCollection control)
at Microsoft.SqlServer.Management.SqlMgmt.LaunchForm..ctor(XmlDocument doc, IServiceProvider provider)
at Microsoft.SqlServer.Management.SqlMgmt.FormLauncher.OnCreateAndShowForm(IServiceProvider serviceProvider, XmlDocument xml)
at Microsoft.SqlServer.Management.SqlMgmt.RunningFormsTable.RunningFormsTableImpl.ThreadStarter.StartThread()
Seems like a managment studio issue. I'm going to move this question to the Tools forum.
Mike
Sunday, February 12, 2012
Cannot restore Report Server to a new machine
SP1 all english, new machine is Win2003 with SQL Server 2000 Enterprise SP3
and RS SP1, all german.
The new machine doesn't have the same network name as the original machine.
After a first failed attempt, I decided to start over again on the new
machine:
I de-installed Reporting Services, and reinstalled, applied SP1.
The RS server was functionnal.
I applied the Forms Authentication changes as per the Microsoft article.
The RS server was functionnal.
I restored the ReportServer and ReportServerTempDB from the Win2000 server
and copied the encryption key using rskeymgmt. I made sure that the accounts
on the restored DBs are ok by running sp_change_users_login
I'm still getting the same error:
The report server installation is not initialized. Check the documentation
for more information. (rsReportServerNotActivated)
I run rsactivate, and I'm still getting the error.
All possible users have been given SA priviledges on the SQL Server (ASPNET,
IUSR_xxx, the account used by RS to connect to SQL, the local admin and the
administrators group)
Could it be because:
1) You cannot restore a RS server from a Win2000 English machine to a
Win2003 German machine?
2) You cannot restore a RS Server to a server that has a different name?
PS: This is a continuation of post about RSActivate since I have now been
able to narrow down the problem to the reporting server restore, instead of
rsactivate.
Here are the logs, from ReportServer and ReportServerWebApp:
<Header>
<Product>Microsoft SQL Server Reporting Services, Version
8.00.878.00</Product>
<Locale>de-DE</Locale>
<TimeZone>Mitteleuropäische Sommerzeit </TimeZone>
<Path>C:\Programme\Microsoft SQL Server\MSSQL\Reporting
Services\LogFiles\ReportServerWebApp__05_09_2005_14_33_11.log</Path>
<SystemName>xxxxxxTEST</SystemName>
<OSName>Microsoft Windows NT 5.2.3790.0</OSName>
<OSVersion>5.2.3790.0</OSVersion>
</Header>
w3wp!library!c10!09.05.2005-14:33:11:: i INFO: Initializing
MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
w3wp!library!c10!09.05.2005-14:33:11:: i INFO: Initializing MaxScheduleWait
to default value of '1' second(s) because it was not specified in
Configuration file.
w3wp!library!c10!09.05.2005-14:33:11:: i INFO: Initializing
DatabaseQueryTimeout to default value of '30' second(s) because it was not
specified in Configuration file.
w3wp!library!c10!09.05.2005-14:33:11:: i INFO: Initializing InstanceName to
default value of 'MSSQLSERVER.1' because it was not specified in
Configuration file.
w3wp!library!c10!09.05.2005-14:33:11:: i INFO: Initializing
ProcessRecycleOptions to default value of '0' because it was not specified
in Configuration file.
w3wp!library!c10!09.05.2005-14:33:11:: i INFO: Initializing
RunningRequestsScavengerCycle to default value of '30' second(s) because it
was not specified in Configuration file.
w3wp!library!c10!09.05.2005-14:33:11:: i INFO: Initializing
RunningRequestsDbCycle to default value of '30' second(s) because it was not
specified in Configuration file.
w3wp!library!c10!09.05.2005-14:33:11:: i INFO: Initializing
RunningRequestsAge to default value of '30' second(s) because it was not
specified in Configuration file.
w3wp!library!c10!09.05.2005-14:33:11:: i INFO: Initializing
CleanupCycleMinutes to default value of '10' minute(s) because it was not
specified in Configuration file.
w3wp!library!c10!09.05.2005-14:33:11:: i INFO: Initializing
SecureConnectionLevel to default value of '1' because it was not specified
in Configuration file.
w3wp!library!c10!09.05.2005-14:33:11:: i INFO: Initializing DisplayErrorLink
to 'True' as specified in Configuration file.
w3wp!library!c10!09.05.2005-14:33:11:: i INFO: Initializing
WebServiceUseFileShareStorage to default value of 'False' because it was not
specified in Configuration file.
w3wp!ui!ac!5/9/2005-14:33:15:: e ERROR: Unable to communicate with report
server. Please verify that the report server is operational.
w3wp!ui!ac!5/9/2005-14:33:15:: e ERROR: HTTP status code --> 500
<Header>
<Product>Microsoft SQL Server Reporting Services, Version
8.00.878.00</Product>
<Locale>de-DE</Locale>
<TimeZone>Mitteleuropäische Sommerzeit </TimeZone>
<Path>C:\Programme\Microsoft SQL Server\MSSQL\Reporting
Services\LogFiles\ReportServer__05_10_2005_10_05_47.log</Path>
<SystemName>xxxxxTEST</SystemName>
<OSName>Microsoft Windows NT 5.2.3790.0</OSName>
<OSVersion>5.2.3790.0</OSVersion>
</Header>
w3wp!webserver!a44!10.05.2005-10:05:47:: i INFO: Reporting Web Server started
w3wp!library!a44!10.05.2005-10:05:47:: i INFO: Initializing ConnectionType
to '0' as specified in Configuration file.
w3wp!library!a44!10.05.2005-10:05:47:: i INFO: Initializing
IsSchedulingService to 'True' as specified in Configuration file.
w3wp!library!a44!10.05.2005-10:05:47:: i INFO: Initializing
IsNotificationService to 'True' as specified in Configuration file.
w3wp!library!a44!10.05.2005-10:05:47:: i INFO: Initializing IsEventService
to 'True' as specified in Configuration file.
w3wp!library!a44!10.05.2005-10:05:47:: i INFO: Initializing PollingInterval
to '10' second(s) as specified in Configuration file.
w3wp!library!a44!10.05.2005-10:05:47:: i INFO: Initializing MemoryLimit to
'60' percent as specified in Configuration file.
w3wp!library!a44!10.05.2005-10:05:47:: i INFO: Initializing RecycleTime to
'720' minute(s) as specified in Configuration file.
w3wp!library!a44!10.05.2005-10:05:47:: i INFO: Initializing
MaximumMemoryLimit to '80' percent as specified in Configuration file.
w3wp!library!a44!10.05.2005-10:05:47:: i INFO: Initializing
MaxAppDomainUnloadTime to '30' minute(s) as specified in Configuration file.
w3wp!library!a44!10.05.2005-10:05:47:: i INFO: Initializing MaxQueueThreads
to '0' thread(s) as specified in Configuration file.
w3wp!library!a44!10.05.2005-10:05:47:: i INFO: Initializing
MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
w3wp!library!a44!10.05.2005-10:05:47:: i INFO: Initializing MaxScheduleWait
to '5' second(s) as specified in Configuration file.
w3wp!library!a44!10.05.2005-10:05:47:: i INFO: Initializing
DatabaseQueryTimeout to '120' second(s) as specified in Configuration file.
w3wp!library!a44!10.05.2005-10:05:47:: i INFO: Initializing InstanceName to
'MSSQLSERVER' as specified in Configuration file.
w3wp!library!a44!10.05.2005-10:05:47:: i INFO: Initializing
ProcessRecycleOptions to '0' as specified in Configuration file.
w3wp!library!a44!10.05.2005-10:05:47:: i INFO: Initializing
RunningRequestsScavengerCycle to '60' second(s) as specified in Configuration
file.
w3wp!library!a44!10.05.2005-10:05:47:: i INFO: Initializing
RunningRequestsDbCycle to '60' second(s) as specified in Configuration file.
w3wp!library!a44!10.05.2005-10:05:47:: i INFO: Initializing
RunningRequestsAge to '30' second(s) as specified in Configuration file.
w3wp!library!a44!10.05.2005-10:05:47:: i INFO: Initializing
CleanupCycleMinutes to '10' minute(s) as specified in Configuration file.
w3wp!library!a44!10.05.2005-10:05:47:: i INFO: Initializing
SecureConnectionLevel to '0' as specified in Configuration file.
w3wp!library!a44!10.05.2005-10:05:47:: i INFO: Initializing DisplayErrorLink
to 'True' as specified in Configuration file.
w3wp!library!a44!10.05.2005-10:05:47:: i INFO: Initializing
WebServiceUseFileShareStorage to default value of 'False' because it was not
specified in Configuration file.
w3wp!resourceutilities!a44!10.05.2005-10:05:47:: i INFO: Running on 0
physical processors, 1 logical processors
w3wp!resourceutilities!a44!10.05.2005-10:05:47:: i INFO: Reporting Services
starting SKU: Enterprise
w3wp!runningjobs!a44!10.05.2005-10:05:47:: i INFO: Database Cleanup (Web
Service) timer enabled: Cycle: 600 seconds
w3wp!runningjobs!a44!10.05.2005-10:05:47:: i INFO: Running Requests
Scavenger timer enabled: Cycle: 60 seconds
w3wp!runningjobs!a44!10.05.2005-10:05:47:: i INFO: Running Requests DB timer
enabled: Cycle: 60 seconds
w3wp!runningjobs!a44!10.05.2005-10:05:47:: i INFO: Memory stats update timer
enabled: Cycle: 60 seconds
w3wp!library!af8!05/10/2005-10:06:07:: i INFO: Call to GetPermissions:/
w3wp!crypto!af8!05/10/2005-10:06:07:: i INFO: Initializing crypto as user:
NT-AUTORITÃ?T\NETZWERKDIENST
w3wp!crypto!af8!05/10/2005-10:06:07:: i INFO: Exporting public key
w3wp!crypto!af8!05/10/2005-10:06:07:: w WARN: Web Service not activated
w3wp!crypto!af8!05/10/2005-10:06:07:: i INFO: Client is not a local admin.
Not attempting activation.
w3wp!library!af8!05/10/2005-10:06:07:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerNotActivatedException:
The report server installation is not initialized. Check the documentation
for more information., ;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerNotActivatedException:
The report server installation is not initialized. Check the documentation
for more information.
w3wp!library!af8!05/10/2005-10:06:11:: i INFO: Call to GetSystemPermissions
w3wp!crypto!af8!05/10/2005-10:06:12:: i INFO: Initializing crypto as user:
NT-AUTORITÃ?T\NETZWERKDIENST
w3wp!crypto!af8!05/10/2005-10:06:12:: i INFO: Exporting public key
w3wp!crypto!af8!05/10/2005-10:06:12:: w WARN: Web Service not activated
w3wp!crypto!af8!05/10/2005-10:06:12:: i INFO: Client is not a local admin.
Not attempting activation.
w3wp!library!af8!05/10/2005-10:06:12:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerNotActivatedException:
The report server installation is not initialized. Check the documentation
for more information., ;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerNotActivatedException:
The report server installation is not initialized. Check the documentation
for more information.Hi,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood you are not able to move Reporting
Services from Windows 2000 to Windows Server 2003. If I have misunderstood
your concern, please feel free to point it out.
Based on my knowlege, we have a Knowledge Base article describes how to
move a Reporting Services database from a computer that is running
Microsoft SQL Server Reporting Services to another computer. You could
follow the step by step in the MORE INFORMATION section
How to move a Reporting Services database from a computer that is running
Reporting Services to another computer
http://support.microsoft.com/kb/842425
From the log file you have posted, I have noticed following entries
=============w3wp!crypto!af8!05/10/2005-10:06:07:: i INFO: Initializing crypto as user:
NT-AUTORITÃ?T\NETZWERKDIENST
w3wp!crypto!af8!05/10/2005-10:06:07:: i INFO: Exporting public key
w3wp!crypto!af8!05/10/2005-10:06:07:: w WARN: Web Service not activated
w3wp!crypto!af8!05/10/2005-10:06:07:: i INFO: Client is not a local admin.
Not attempting activation.
=============
Though the user can login to SQL machine, this error happens if the logged
user account which is used to run the Rsactivate did not have permission on
the database and database objects in SQL Server, specifically the
reportserver and reportservertempdb.
You should add the user account which is used to run the rsactivate to the
sql server box as a local admin. By default local admin has full privileges
on the database and the database objects. If you cannot add them as local
admin, you can add them just to the reportserver and reportservertempdb.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael,
As far as I can tell, I did follow the procedure, and also I did run the
rsactivate as a local admin.
In the meantime, I have opened a support case with Microsoft in Germany.
Many thanks.
"Michael Cheng [MSFT]" wrote:
> Hi,
> Welcome to use MSDN Managed Newsgroup!
> From your descriptions, I understood you are not able to move Reporting
> Services from Windows 2000 to Windows Server 2003. If I have misunderstood
> your concern, please feel free to point it out.
> Based on my knowlege, we have a Knowledge Base article describes how to
> move a Reporting Services database from a computer that is running
> Microsoft SQL Server Reporting Services to another computer. You could
> follow the step by step in the MORE INFORMATION section
> How to move a Reporting Services database from a computer that is running
> Reporting Services to another computer
> http://support.microsoft.com/kb/842425
> From the log file you have posted, I have noticed following entries
> =============> w3wp!crypto!af8!05/10/2005-10:06:07:: i INFO: Initializing crypto as user:
> NT-AUTORITÃ?â'T\NETZWERKDIENST
> w3wp!crypto!af8!05/10/2005-10:06:07:: i INFO: Exporting public key
> w3wp!crypto!af8!05/10/2005-10:06:07:: w WARN: Web Service not activated
> w3wp!crypto!af8!05/10/2005-10:06:07:: i INFO: Client is not a local admin.
> Not attempting activation.
> =============> Though the user can login to SQL machine, this error happens if the logged
> user account which is used to run the Rsactivate did not have permission on
> the database and database objects in SQL Server, specifically the
> reportserver and reportservertempdb.
> You should add the user account which is used to run the rsactivate to the
> sql server box as a local admin. By default local admin has full privileges
> on the database and the database objects. If you cannot add them as local
> admin, you can add them just to the reportserver and reportservertempdb.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi,
Thanks for your understanding, you are welcome to let us know the result
when your case was finally resolved. Share it in the newsgroup and I
believe others will definitely benefit from your contribution.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.|||Got a solution after 2 weeks of hard work from PSS.
See resolution under thread "RS Activation is failing"
"Michael Cheng [MSFT]" wrote:
> Hi,
> Thanks for your understanding, you are welcome to let us know the result
> when your case was finally resolved. Share it in the newsgroup and I
> believe others will definitely benefit from your contribution.
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>|||Hi James,
GREAT!
Thanks for your sharing it with us! For others convenience, I post the
RESOLUTION here
--
Newsgroups: microsoft.public.sqlserver.reportingsvcs
From: "James" <aa1...@.nospam.nospam> - Find messages by this author
Date: Fri, 27 May 2005 08:32:10 -0700
Local: Fri,May 27 2005 11:32 am
Subject: RE: RS Activation is failing
I got the solution. One needs to first transfer the 2 databases and restore
them on the new server, copy the encryption key and run rskeymgmt.
Then go to the Report manager so that the RS installation gets activated.
And then and only then, reapply all changes necessary to implement forms
auth.
My problem was that I had copied the 6 config files that are involved in
forms auth from the old server, and there is encrypted info in there that
isn't valid on the new server. Also, activation only works in Windows
authentication mode, that's why one has to start in Windows mode, and only
then move to Forms Auth.
--
Thanks James!! Once more for your efforts!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.