align the parameters in reports

IS it possible to design the Parameters Layout in Reporting Service
reports
miniYou can modify styles in HTMLViewer.css style sheet present in Reporting
Services\ReportServer\Styles folder but you will only affect appearance of
the elements, not the distribution or type of controls you want to show.
If you want to fully customize that layout, you need to use reporting
services API, as I have done. For example, I have used radio buttons to
choose report parameters instead of the default combobox.
Jaime
"mini" wrote:
> IS it possible to design the Parameters Layout in Reporting Service
> reports
> mini
>|||thanks Jaime
can u explain how you use reporting
services API?
Can u reduce the Textbox width displayed in parameter layout?
thanks
mini

Alerts for SQL Service stoppages

Does anyone know if there is a way to get a page alert if SQL Service stops?Andre,
On Windows 2003 and XP you can specify actions on service failures, both in
itial and subsequent.
a command line email client could take it from there ( Recovery tab of a ser
vice's properties ).
If you are on a lower OS then depending on your enthusiasm, it is possible t
o write your own
service to monitor other services, including stopping and starting them, usi
ng API calls to the
service control manager.
If there is any easier way, it's not one I've used !
Regards
AJ
"Andre" <anonymous@.discussions.microsoft.com> wrote in message
news:D7A53734-28F0-418E-8BD2-4898AFFACDD1@.microsoft.com...
> Does anyone know if there is a way to get a page alert if SQL Service stops?[/colo
r]

Agent Service Fails to Start

For some time now, I've been unable to start SQL Server
Agent service. I can run agent in cmd window via:
sqlagent.exe -c -v. The error on failed startup is
something like, sqlagent failed to start in a timely
manner.Have you tried starting the agent from Service Manager? If so, what error
message do you get? What user account does the Agent run with? Does the
account belong to a Win2K domain or the local machine?
The answers to these questions will help to diagnose the problem.
"Clark" <anonymous@.discussions.microsoft.com> wrote in message
news:4a2e01c3ab7d$eebde570$a601280a@.phx.gbl...
> For some time now, I've been unable to start SQL Server
> Agent service. I can run agent in cmd window via:
> sqlagent.exe -c -v. The error on failed startup is
> something like, sqlagent failed to start in a timely
> manner.|||Oh yes, I've tried that.
1. With Service Manager, it fails to start with something
like, sqlagent failed to start in a timely manner.
2. Agent uses the sama account as SQL Server service.
I plan to dink with this on Monday morning.
Question: Can the time to load a service be extended,
for example, to load a service on a very busy server?
>--Original Message--
>Have you tried starting the agent from Service Manager?
If so, what error
>message do you get? What user account does the Agent run
with? Does the
>account belong to a Win2K domain or the local machine?
>The answers to these questions will help to diagnose the
problem.
>
>"Clark" <anonymous@.discussions.microsoft.com> wrote in
message
>news:4a2e01c3ab7d$eebde570$a601280a@.phx.gbl...
>> For some time now, I've been unable to start SQL Server
>> Agent service. I can run agent in cmd window via:
>> sqlagent.exe -c -v. The error on failed startup is
>> something like, sqlagent failed to start in a timely
>> manner.
>
>.
>|||I am having a similar problem too. I am trying to start the service from
Enterprise Manager and get the following error:
A error 5 - (Access is denied) occured while performing the service opeation
on the SQL ServerAgent service
I tried changeing the account info to the SA login and password but to no
avail. Is it possibel that the service is needs the machine domain Admin
account info?
John.
"Clark" <anonymous@.discussions.microsoft.com> wrote in message
news:505301c3ac4e$be0c0070$a601280a@.phx.gbl...
> Oh yes, I've tried that.
> 1. With Service Manager, it fails to start with something
> like, sqlagent failed to start in a timely manner.
> 2. Agent uses the sama account as SQL Server service.
> I plan to dink with this on Monday morning.
> Question: Can the time to load a service be extended,
> for example, to load a service on a very busy server?
>
> >--Original Message--
> >Have you tried starting the agent from Service Manager?
> If so, what error
> >message do you get? What user account does the Agent run
> with? Does the
> >account belong to a Win2K domain or the local machine?
> >
> >The answers to these questions will help to diagnose the
> problem.
> >
> >
> >"Clark" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:4a2e01c3ab7d$eebde570$a601280a@.phx.gbl...
> >> For some time now, I've been unable to start SQL Server
> >> Agent service. I can run agent in cmd window via:
> >> sqlagent.exe -c -v. The error on failed startup is
> >> something like, sqlagent failed to start in a timely
> >> manner.
> >
> >
> >.
> >|||Hi John,
Sa login is for SQL server authentication, which is different from the account used for SQL server agent service. To run sql server agent, one must typically have a domain user account (as it is used for sql mail, replication, backup etc). Also this domain name should have administrative privs on the machine where sql server instance is running.
Sometimes I guess rebuilding registry can solve the problem. Use "regrebld" in the cmd line prompt. I haven't used this utility myself, so inquire with others before using it
Thank
GYK|||Thanks for you help.
"GYK" <anonymous@.discussions.microsoft.com> wrote in message
news:CFD08193-68CB-48CA-A931-04BBA0EC21A2@.microsoft.com...
> Hi John,
> Sa login is for SQL server authentication, which is different from the
account used for SQL server agent service. To run sql server agent, one must
typically have a domain user account (as it is used for sql mail,
replication, backup etc). Also this domain name should have administrative
privs on the machine where sql server instance is running.
> Sometimes I guess rebuilding registry can solve the problem. Use
"regrebld" in the cmd line prompt. I haven't used this utility myself, so
inquire with others before using it.
> Thanks
> GYK

After restoring MASTER database, can't start SQLServer Service: Configuration block version 0 i

Now, I checked and verified that my backup version of SQL Server is the same as the version installed on the computer I'm restoring too.

I have SQL Server on a production machine that I backed up and want to test a full restore on a dev machine to make sure it will work when I need it to.

Now that I've run the restore command on my tape backup and go to restart the SQL server service I receive:

Configuration block version 0 is not a valid version number. SQL Server is exiting. Restore the master database or reinstall.

I'm afraid I don't understand why this is happening. If the builds are the same, then shouldn't restoring the MASTER database have worked normally and I'd be able to restart the service now?

Any thoughts or suggestions?

If the service cannot be started, you must rebuild the

system databases, adding information that has been lost by attaching existing tables and recreating

objects.

After this, Restoring the master database when SQL Server is accessible

With master database accessible, you should start SQL Server in single-user mode and then restore your copy of the

master database from your most recent full database backup in the usual way, as described in the

following steps.

#1 - Start SQL Server in single-user mode.

with command:

sqlservr.exe -c –m

#2 - Restore the master database from the most recent backup:

RESTORE DATABASE master

FROM masterbackup

If Master isn′t accessible:

To rebuild the master database, you should run the SQL Server setup program with the following

options:

? The /qn switch to suppress the user interface.

? The REINSTALLMODE = AMUS property to rebuild system databases.

? The REINSTALL = ALL property to set up the server with the previously installed features.

This must be used when specifying the REINSTALLMODE property.

|||

I tried rebuilding using this command:

start /wait d:\setup.exe /qb INSTANCENAME=MSSQLSERVER REINSTALL=SQL_Engine REBUILDDATABASE=1 SAPWD=YourPassword

However, you are saying those were not the proper commands and switches to use during the reinstallation?

(Also I didn't want to specify an SA account and password, I wanted to use windows authentication but didn't see an option for that).

|||

To use Windows authentication, you need use this parameters:

start /wait d:\setup.exe /qb INSTANCENAME=MSSQLSERVER REINSTALL=SQL_Engine REBUILDDATABASE=1

SQLACCOUNT=<domain\user> SQLPASSWORD=<DomainUserPassword>

|||

Thanks.

Anyway, I tried rebuilding and that DID work.

But when I restored the master database, I was back where I started.

I KNOW the database installations are the same version as I did SELECT @.@.VERSION on both and they match.

So I don't understand why restoring a tape from one server to the other causes the other server to throw this error when the versions of the server do appear to be the same.

After laptop goes into standby, SQLEXPRESS won't start

If my laptop goes into standby with the MSSQL$SQLEXPRESS service running, the service will not start again. I get the following error messages in my log:

2006-03-06 20:49:08.45 Server This instance of SQL Server last reported using a process ID of 1764 at 3/6/2006 1:48:21 PM (local) 3/6/2006 9:48:21 PM (UTC). This is an informational message only; no user action is required.

2006-03-06 20:49:08.45 Server Error: 17053, Severity: 16, State: 1.

2006-03-06 20:49:08.45 Server UpdateUptimeRegKey: Operating system error 5(Access is denied.) encountered.

2006-03-06 20:49:08.45 Server Registry startup parameters:

2006-03-06 20:49:08.45 Server -d c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf

2006-03-06 20:49:08.45 Server -e c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG

2006-03-06 20:49:08.45 Server -l c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf

2006-03-06 20:49:08.56 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

2006-03-06 20:49:08.56 Server Detected 1 CPUs. This is an informational message; no user action is required.

2006-03-06 20:49:09.32 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.

2006-03-06 20:49:09.35 Server Database Mirroring Transport is disabled in the endpoint configuration.

2006-03-06 20:49:09.35 spid5s Starting up database 'master'.

2006-03-06 20:49:09.68 spid5s SQL Trace ID 1 was started by login "sa".

2006-03-06 20:49:09.76 spid5s Starting up database 'mssqlsystemresource'.

2006-03-06 20:49:10.03 spid5s Failed to check for new installation or a renamed server at startup. The logic for this check has failed unexpectedly. Run setup again, or fix the problematic registry key.

2006-03-06 20:49:10.03 Server Error: 17182, Severity: 16, State: 1.

2006-03-06 20:49:10.03 Server TDSSNIClient initialization failed with error 0x5, status code 0x90.

2006-03-06 20:49:10.03 Server Error: 17182, Severity: 16, State: 1.

2006-03-06 20:49:10.03 Server TDSSNIClient initialization failed with error 0x5, status code 0x1.

2006-03-06 20:49:10.03 Server Error: 17826, Severity: 18, State: 3.

2006-03-06 20:49:10.03 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.

2006-03-06 20:49:10.03 Server Error: 17120, Severity: 16, State: 1.

2006-03-06 20:49:10.03 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.

Uninstalling, reinstalling and restoring the databases fixes the problem. Also, is there anyway to gracefully shut down the service on standby? Any help would be greatly appreciated.

Thanks,

David

Essentially this error below means that SQL no longer has access to it's registry keys.

2006-03-06 20:49:10.03 Server Error: 17182, Severity: 16, State: 1.

2006-03-06 20:49:10.03 Server TDSSNIClient initialization failed with error 0x5, status code 0x90.

Error 0x5 means "Access Denied" most likely due to the instance no longer having access to its configuration info stored in the registry. Not sure why going into standby mode would trigger a change in the registry key security.

|||

I don't have this problem on my laptop which goes in and out of standby multiple times a day. This seems like it is probably deeper than just SQL. I'm trying to track down some additional info from the Windows team.

In the mean time, I've occationally seen "weird" behavior associated with a corrupt user profile. You might consider recreating your user profile and see if the problem goes away. Kind of a scatter gun approach, but it's fairly easy to check. Read the following KB articles for more about troubleshooting profiles:

http://support.microsoft.com/kb/305506/en-us

http://support.microsoft.com/kb/811151/en-us

Regards,

Mike Wachal
SQL Express team

|||

Change your SQL Express to logon as the System account, by default it logs on as the Network something or another account which is a total crapshoot as to whether that account can get to the registry.

Gandalf

http://gandalf.hudlow.net

|||gandalf is totally right. I had the same problem on every reboot until I changed the account to LOCAL SYSTEM. Now everything is kosher|||

Every time you install a SQL instance it will automatically grant itself access to the various registry keys that it needs access to. Even if the service is running under network service. So you should not need to run it under local system account to get access to the registry keys. Switching SQL to run under local system will give it carte blanc to read the registry which will solve a problem where setup probably failed to grant itself proper perms on the reg keys.

Perhaps something on your machine is locking down reg key permissions after SQLExpress is installed, this is all I can think of that could cause this issue.

|||Yeah, this is a pretty good demo of why the registry is both the best and worst idea in history :)

After laptop goes into standby, SQLEXPRESS won't start

If my laptop goes into standby with the MSSQL$SQLEXPRESS service running, the service will not start again. I get the following error messages in my log:

2006-03-06 20:49:08.45 Server This instance of SQL Server last reported using a process ID of 1764 at 3/6/2006 1:48:21 PM (local) 3/6/2006 9:48:21 PM (UTC). This is an informational message only; no user action is required.

2006-03-06 20:49:08.45 Server Error: 17053, Severity: 16, State: 1.

2006-03-06 20:49:08.45 Server UpdateUptimeRegKey: Operating system error 5(Access is denied.) encountered.

2006-03-06 20:49:08.45 Server Registry startup parameters:

2006-03-06 20:49:08.45 Server -d c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf

2006-03-06 20:49:08.45 Server -e c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG

2006-03-06 20:49:08.45 Server -l c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf

2006-03-06 20:49:08.56 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

2006-03-06 20:49:08.56 Server Detected 1 CPUs. This is an informational message; no user action is required.

2006-03-06 20:49:09.32 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.

2006-03-06 20:49:09.35 Server Database Mirroring Transport is disabled in the endpoint configuration.

2006-03-06 20:49:09.35 spid5s Starting up database 'master'.

2006-03-06 20:49:09.68 spid5s SQL Trace ID 1 was started by login "sa".

2006-03-06 20:49:09.76 spid5s Starting up database 'mssqlsystemresource'.

2006-03-06 20:49:10.03 spid5s Failed to check for new installation or a renamed server at startup. The logic for this check has failed unexpectedly. Run setup again, or fix the problematic registry key.

2006-03-06 20:49:10.03 Server Error: 17182, Severity: 16, State: 1.

2006-03-06 20:49:10.03 Server TDSSNIClient initialization failed with error 0x5, status code 0x90.

2006-03-06 20:49:10.03 Server Error: 17182, Severity: 16, State: 1.

2006-03-06 20:49:10.03 Server TDSSNIClient initialization failed with error 0x5, status code 0x1.

2006-03-06 20:49:10.03 Server Error: 17826, Severity: 18, State: 3.

2006-03-06 20:49:10.03 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.

2006-03-06 20:49:10.03 Server Error: 17120, Severity: 16, State: 1.

2006-03-06 20:49:10.03 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.

Uninstalling, reinstalling and restoring the databases fixes the problem. Also, is there anyway to gracefully shut down the service on standby? Any help would be greatly appreciated.

Thanks,

David

Essentially this error below means that SQL no longer has access to it's registry keys.

2006-03-06 20:49:10.03 Server Error: 17182, Severity: 16, State: 1.

2006-03-06 20:49:10.03 Server TDSSNIClient initialization failed with error 0x5, status code 0x90.

Error 0x5 means "Access Denied" most likely due to the instance no longer having access to its configuration info stored in the registry. Not sure why going into standby mode would trigger a change in the registry key security.

|||

I don't have this problem on my laptop which goes in and out of standby multiple times a day. This seems like it is probably deeper than just SQL. I'm trying to track down some additional info from the Windows team.

In the mean time, I've occationally seen "weird" behavior associated with a corrupt user profile. You might consider recreating your user profile and see if the problem goes away. Kind of a scatter gun approach, but it's fairly easy to check. Read the following KB articles for more about troubleshooting profiles:

http://support.microsoft.com/kb/305506/en-us

http://support.microsoft.com/kb/811151/en-us

Regards,

Mike Wachal
SQL Express team

|||

Change your SQL Express to logon as the System account, by default it logs on as the Network something or another account which is a total crapshoot as to whether that account can get to the registry.

Gandalf

http://gandalf.hudlow.net

|||gandalf is totally right. I had the same problem on every reboot until I changed the account to LOCAL SYSTEM. Now everything is kosher|||

Every time you install a SQL instance it will automatically grant itself access to the various registry keys that it needs access to. Even if the service is running under network service. So you should not need to run it under local system account to get access to the registry keys. Switching SQL to run under local system will give it carte blanc to read the registry which will solve a problem where setup probably failed to grant itself proper perms on the reg keys.

Perhaps something on your machine is locking down reg key permissions after SQLExpress is installed, this is all I can think of that could cause this issue.

|||Yeah, this is a pretty good demo of why the registry is both the best and worst idea in history :)

After laptop goes into standby, SQLEXPRESS won't start

If my laptop goes into standby with the MSSQL$SQLEXPRESS service running, the service will not start again. I get the following error messages in my log:

2006-03-06 20:49:08.45 Server This instance of SQL Server last reported using a process ID of 1764 at 3/6/2006 1:48:21 PM (local) 3/6/2006 9:48:21 PM (UTC). This is an informational message only; no user action is required.

2006-03-06 20:49:08.45 Server Error: 17053, Severity: 16, State: 1.

2006-03-06 20:49:08.45 Server UpdateUptimeRegKey: Operating system error 5(Access is denied.) encountered.

2006-03-06 20:49:08.45 Server Registry startup parameters:

2006-03-06 20:49:08.45 Server -d c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf

2006-03-06 20:49:08.45 Server -e c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG

2006-03-06 20:49:08.45 Server -l c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf

2006-03-06 20:49:08.56 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

2006-03-06 20:49:08.56 Server Detected 1 CPUs. This is an informational message; no user action is required.

2006-03-06 20:49:09.32 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.

2006-03-06 20:49:09.35 Server Database Mirroring Transport is disabled in the endpoint configuration.

2006-03-06 20:49:09.35 spid5s Starting up database 'master'.

2006-03-06 20:49:09.68 spid5s SQL Trace ID 1 was started by login "sa".

2006-03-06 20:49:09.76 spid5s Starting up database 'mssqlsystemresource'.

2006-03-06 20:49:10.03 spid5s Failed to check for new installation or a renamed server at startup. The logic for this check has failed unexpectedly. Run setup again, or fix the problematic registry key.

2006-03-06 20:49:10.03 Server Error: 17182, Severity: 16, State: 1.

2006-03-06 20:49:10.03 Server TDSSNIClient initialization failed with error 0x5, status code 0x90.

2006-03-06 20:49:10.03 Server Error: 17182, Severity: 16, State: 1.

2006-03-06 20:49:10.03 Server TDSSNIClient initialization failed with error 0x5, status code 0x1.

2006-03-06 20:49:10.03 Server Error: 17826, Severity: 18, State: 3.

2006-03-06 20:49:10.03 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.

2006-03-06 20:49:10.03 Server Error: 17120, Severity: 16, State: 1.

2006-03-06 20:49:10.03 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.

Uninstalling, reinstalling and restoring the databases fixes the problem. Also, is there anyway to gracefully shut down the service on standby? Any help would be greatly appreciated.

Thanks,

David

Essentially this error below means that SQL no longer has access to it's registry keys.

2006-03-06 20:49:10.03 Server Error: 17182, Severity: 16, State: 1.

2006-03-06 20:49:10.03 Server TDSSNIClient initialization failed with error 0x5, status code 0x90.

Error 0x5 means "Access Denied" most likely due to the instance no longer having access to its configuration info stored in the registry. Not sure why going into standby mode would trigger a change in the registry key security.

|||

I don't have this problem on my laptop which goes in and out of standby multiple times a day. This seems like it is probably deeper than just SQL. I'm trying to track down some additional info from the Windows team.

In the mean time, I've occationally seen "weird" behavior associated with a corrupt user profile. You might consider recreating your user profile and see if the problem goes away. Kind of a scatter gun approach, but it's fairly easy to check. Read the following KB articles for more about troubleshooting profiles:

http://support.microsoft.com/kb/305506/en-us

http://support.microsoft.com/kb/811151/en-us

Regards,

Mike Wachal
SQL Express team

|||

Change your SQL Express to logon as the System account, by default it logs on as the Network something or another account which is a total crapshoot as to whether that account can get to the registry.

Gandalf

http://gandalf.hudlow.net

|||gandalf is totally right. I had the same problem on every reboot until I changed the account to LOCAL SYSTEM. Now everything is kosher|||

Every time you install a SQL instance it will automatically grant itself access to the various registry keys that it needs access to. Even if the service is running under network service. So you should not need to run it under local system account to get access to the registry keys. Switching SQL to run under local system will give it carte blanc to read the registry which will solve a problem where setup probably failed to grant itself proper perms on the reg keys.

Perhaps something on your machine is locking down reg key permissions after SQLExpress is installed, this is all I can think of that could cause this issue.

|||Yeah, this is a pretty good demo of why the registry is both the best and worst idea in history :)

After laptop goes into standby, SQLEXPRESS won't start

If my laptop goes into standby with the MSSQL$SQLEXPRESS service running, the service will not start again. I get the following error messages in my log:

2006-03-06 20:49:08.45 Server This instance of SQL Server last reported using a process ID of 1764 at 3/6/2006 1:48:21 PM (local) 3/6/2006 9:48:21 PM (UTC). This is an informational message only; no user action is required.

2006-03-06 20:49:08.45 Server Error: 17053, Severity: 16, State: 1.

2006-03-06 20:49:08.45 Server UpdateUptimeRegKey: Operating system error 5(Access is denied.) encountered.

2006-03-06 20:49:08.45 Server Registry startup parameters:

2006-03-06 20:49:08.45 Server -d c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf

2006-03-06 20:49:08.45 Server -e c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG

2006-03-06 20:49:08.45 Server -l c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf

2006-03-06 20:49:08.56 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

2006-03-06 20:49:08.56 Server Detected 1 CPUs. This is an informational message; no user action is required.

2006-03-06 20:49:09.32 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.

2006-03-06 20:49:09.35 Server Database Mirroring Transport is disabled in the endpoint configuration.

2006-03-06 20:49:09.35 spid5s Starting up database 'master'.

2006-03-06 20:49:09.68 spid5s SQL Trace ID 1 was started by login "sa".

2006-03-06 20:49:09.76 spid5s Starting up database 'mssqlsystemresource'.

2006-03-06 20:49:10.03 spid5s Failed to check for new installation or a renamed server at startup. The logic for this check has failed unexpectedly. Run setup again, or fix the problematic registry key.

2006-03-06 20:49:10.03 Server Error: 17182, Severity: 16, State: 1.

2006-03-06 20:49:10.03 Server TDSSNIClient initialization failed with error 0x5, status code 0x90.

2006-03-06 20:49:10.03 Server Error: 17182, Severity: 16, State: 1.

2006-03-06 20:49:10.03 Server TDSSNIClient initialization failed with error 0x5, status code 0x1.

2006-03-06 20:49:10.03 Server Error: 17826, Severity: 18, State: 3.

2006-03-06 20:49:10.03 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.

2006-03-06 20:49:10.03 Server Error: 17120, Severity: 16, State: 1.

2006-03-06 20:49:10.03 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.

Uninstalling, reinstalling and restoring the databases fixes the problem. Also, is there anyway to gracefully shut down the service on standby? Any help would be greatly appreciated.

Thanks,

David

Essentially this error below means that SQL no longer has access to it's registry keys.

2006-03-06 20:49:10.03 Server Error: 17182, Severity: 16, State: 1.

2006-03-06 20:49:10.03 Server TDSSNIClient initialization failed with error 0x5, status code 0x90.

Error 0x5 means "Access Denied" most likely due to the instance no longer having access to its configuration info stored in the registry. Not sure why going into standby mode would trigger a change in the registry key security.

|||

I don't have this problem on my laptop which goes in and out of standby multiple times a day. This seems like it is probably deeper than just SQL. I'm trying to track down some additional info from the Windows team.

In the mean time, I've occationally seen "weird" behavior associated with a corrupt user profile. You might consider recreating your user profile and see if the problem goes away. Kind of a scatter gun approach, but it's fairly easy to check. Read the following KB articles for more about troubleshooting profiles:

http://support.microsoft.com/kb/305506/en-us

http://support.microsoft.com/kb/811151/en-us

Regards,

Mike Wachal
SQL Express team

|||

Change your SQL Express to logon as the System account, by default it logs on as the Network something or another account which is a total crapshoot as to whether that account can get to the registry.

Gandalf

http://gandalf.hudlow.net

|||gandalf is totally right. I had the same problem on every reboot until I changed the account to LOCAL SYSTEM. Now everything is kosher
|||

Every time you install a SQL instance it will automatically grant itself access to the various registry keys that it needs access to. Even if the service is running under network service. So you should not need to run it under local system account to get access to the registry keys. Switching SQL to run under local system will give it carte blanc to read the registry which will solve a problem where setup probably failed to grant itself proper perms on the reg keys.

Perhaps something on your machine is locking down reg key permissions after SQLExpress is installed, this is all I can think of that could cause this issue.

|||Yeah, this is a pretty good demo of why the registry is both the best and worst idea in history :)

After I change Log on of SQL Server 2005, my SQL service agent can not start, any idea?

I use localsystem to start SQL 2005, and use a domain/user to start SQL 2005 agent, the user is an domain admin and local admin, which works.

I had problem to use openrowset, so I changed the SQL 2005 to use the same domain.user to start, which works, after that, I can use openrowset well, but now, I can not start SQL 2005 agent, I get error:

SQLServerAgent could not be started (reason: SQLServerAgent must be able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a member of the SysAdmin role).

and another enry in event viewer, not sure if they are related

SQL Server blocked access to procedure 'dbo.sp_sqlagent_get_startup_info' of component 'Agent XPs' because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of 'Agent XPs' by using sp_configure. For more information about enabling 'Agent XPs', see "Surface Area Configuration" in SQL Server Books Online.

It is SQL 2005 on window 2003.

Any idea how to fix it?

thanks!

In sql 2005 the agent xps are turned 'off by default' so I think the first thing you need to do is turn on the Agent Xps.

exec sp_configure 'show advanced options' , 1 ;reconfigure

exec sp_configure 'Agent XPs',1;reconfigure

go

hth,

-Steven Gott

S/DET

SQL Server

p.s. SQL 2005 does not need to run as a domain admin , It would be much safer if you set it to run as a normal user b/c the high privilleges of the service account combined with some of the xps like xp_cmdshell allow a dba who is sysadmin to manipulate your domain as the domain admin.

|||

I had problem to use openrowset, so I changed the SQL 2005 to use the same domain.user to start, which works, after that, I can use openrowset well ...

I suspect that your problem with using OPENROWSET had to do with permissions to access the file you were attempting to open. Since your original SQL Server account was not a domain account, you would not have been able to access domain resources, including files, with the MSSQL service. Once you changed to use the domain account that was set up for SQL Agent, the OPENROWSET worked since it could now access domain resources.

|||

Hi,

I think you mixed SQL server account with SQL server agent account, I think it is SQL server account that will access the files for openrowset.

Well, I changed the account for my SQL server from local system to a domain admin, that solves the openrowset problem, but more other problem come in.

First, the Memory used by SQL keeps going up, reached 1.7G, I remember how to solve this, I need give the account "lock page in memory" permission, that solves it

Second, I got error, my CLR reports problem, it says

A .NET Framework error occurred during execution of user-defined routine or aggregate "linkclr_x_pdf_createpdf":
System.DllNotFoundException: Unable to load DLL 'ABCpdfCE6.dll': Not enough storage is available to process this command.

When the error happens, the SQL only use 170M memory, the server has 3G memory.

Really a big problem, how can I just set an account with fully localsystem permssion plus permission to access domain file? Since the localsystem worked fine except the openrowset problem.

thanks

|||

My God, after caused me so much trouble, I found the openrowset may have nothing to do with the account. It only works for some time after each restart, even with local system, it works fine, it can access remote files, maybe because I set the permission to the sql server.

But the issue is it stops working after some time, someone said to set permission to temp folder, doesn't work for me yet.

Isn't that a big bug? could someone from the SQL team to shed a light here? I havn't been asking for the solution for many months.

|||

Steve,

when I run this command I get

Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.

Msg 5845, Level 16, State 1, Line 1

Address Windowing Extensions (AWE) requires the 'lock pages in memory' privilege which is not currently present in the access token of the process.

It just will not let me turn it on ..... is there any other way to change the option?

thank you

mitch

|||

You can try using the SQL Server Surface Area Configuration tool.

It will be in the configuration Tools folder under SQL Server

HTH,

-Steven Gott

SDE/T

SQL Server

|||

Steve,

I tried this and I assume its the ole component? but I was able to fix some of the problem but it says it is not part of the sysadmin role which it is. I just dont know where to go from here.

thanks

mitch

After I change Log on of SQL Server 2005, my SQL service agent can not start, any idea?

I use localsystem to start SQL 2005, and use a domain/user to start SQL 2005 agent, the user is an domain admin and local admin, which works.

I had problem to use openrowset, so I changed the SQL 2005 to use the same domain.user to start, which works, after that, I can use openrowset well, but now, I can not start SQL 2005 agent, I get error:

SQLServerAgent could not be started (reason: SQLServerAgent must be able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a member of the SysAdmin role).

and another enry in event viewer, not sure if they are related

SQL Server blocked access to procedure 'dbo.sp_sqlagent_get_startup_info' of component 'Agent XPs' because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of 'Agent XPs' by using sp_configure. For more information about enabling 'Agent XPs', see "Surface Area Configuration" in SQL Server Books Online.

It is SQL 2005 on window 2003.

Any idea how to fix it?

thanks!

In sql 2005 the agent xps are turned 'off by default' so I think the first thing you need to do is turn on the Agent Xps.

exec sp_configure 'show advanced options' , 1 ;reconfigure

exec sp_configure 'Agent XPs',1;reconfigure

go

hth,

-Steven Gott

S/DET

SQL Server

p.s. SQL 2005 does not need to run as a domain admin , It would be much safer if you set it to run as a normal user b/c the high privilleges of the service account combined with some of the xps like xp_cmdshell allow a dba who is sysadmin to manipulate your domain as the domain admin.

|||

I had problem to use openrowset, so I changed the SQL 2005 to use the same domain.user to start, which works, after that, I can use openrowset well ...

I suspect that your problem with using OPENROWSET had to do with permissions to access the file you were attempting to open. Since your original SQL Server account was not a domain account, you would not have been able to access domain resources, including files, with the MSSQL service. Once you changed to use the domain account that was set up for SQL Agent, the OPENROWSET worked since it could now access domain resources.

|||

Hi,

I think you mixed SQL server account with SQL server agent account, I think it is SQL server account that will access the files for openrowset.

Well, I changed the account for my SQL server from local system to a domain admin, that solves the openrowset problem, but more other problem come in.

First, the Memory used by SQL keeps going up, reached 1.7G, I remember how to solve this, I need give the account "lock page in memory" permission, that solves it

Second, I got error, my CLR reports problem, it says

A .NET Framework error occurred during execution of user-defined routine or aggregate "linkclr_x_pdf_createpdf":
System.DllNotFoundException: Unable to load DLL 'ABCpdfCE6.dll': Not enough storage is available to process this command.

When the error happens, the SQL only use 170M memory, the server has 3G memory.

Really a big problem, how can I just set an account with fully localsystem permssion plus permission to access domain file? Since the localsystem worked fine except the openrowset problem.

thanks

|||

My God, after caused me so much trouble, I found the openrowset may have nothing to do with the account. It only works for some time after each restart, even with local system, it works fine, it can access remote files, maybe because I set the permission to the sql server.

But the issue is it stops working after some time, someone said to set permission to temp folder, doesn't work for me yet.

Isn't that a big bug? could someone from the SQL team to shed a light here? I havn't been asking for the solution for many months.

|||

Steve,

when I run this command I get

Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.

Msg 5845, Level 16, State 1, Line 1

Address Windowing Extensions (AWE) requires the 'lock pages in memory' privilege which is not currently present in the access token of the process.

It just will not let me turn it on ..... is there any other way to change the option?

thank you

mitch

|||

You can try using the SQL Server Surface Area Configuration tool.

It will be in the configuration Tools folder under SQL Server

HTH,

-Steven Gott

SDE/T

SQL Server

|||

Steve,

I tried this and I assume its the ole component? but I was able to fix some of the problem but it says it is not part of the sysadmin role which it is. I just dont know where to go from here.

thanks

mitch

After Full SQL Server 2005 Install SSIS is still not a service on the machine?

I have done a full Sql Server install on a server and the SSIS service is not available. Normally when I load Sql Server I get “SQL Server Integration Services" as a service that I can start. On this machine it is not listed after the install. I don't get any errors through out the install.

Please Help!

Steve

Setup forum may have more helpful for this issue:
http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=95&SiteID=1

Advice on Switching 7 Recovery Models

The databases I just took over are on SQL Server 7.0 with NO SQL Server Serv
ice Packs installed. Several application (not system) databases have FULL r
ecovery specified and several use SIMPLE. The manager wants to implement Fu
ll Recovery on all the appl
ication databases. He also does not want to install any service packs unles
s something is broken that a service pack will fix. Currently there is noth
ing broken.
I have read that the switch from SIMPLE to FULL Recovery is not as simple as
it appears. What are the implications? What makes it challenging? Can I
just remove the truncate on checkpoint option and chnage the database mainte
nance plans to start backin
g up tran logs?
Thanks for your insight.Hi,
(In SQL 7.0 there is no concept of recovery model)
So if you remove the "Truncate Log on checkpoint" option on database will
enable the logging. There is no impication in disabling this option, only
problem is you have to monitor the growth of transaction log file. The file
growth will be very high if you have any batch operations.
After disabling the Truncate log on checkpoint do,
1. Perform a Full database backup of database (After enabling this option
you have perform a full backup to recreate the backup chain)
2. After that change the database maintenance plan to perform a transaction
log backup
3. Weekly monitor the growth of Transaction log file, if the physical file
size is high then do a DBCC SHIRNKFILE (refer books online)
to shrink the physical file.
Thanks
Hari
MCDBA
"?" <anonymous@.discussions.microsoft.com> wrote in message
news:0EA95DE2-9AED-4F5B-ACCD-55E743371C21@.microsoft.com...
> The databases I just took over are on SQL Server 7.0 with NO SQL Server
Service Packs installed. Several application (not system) databases have
FULL recovery specified and several use SIMPLE. The manager wants to
implement Full Recovery on all the application databases. He also does not
want to install any service packs unless something is broken that a service
pack will fix. Currently there is nothing broken.
> I have read that the switch from SIMPLE to FULL Recovery is not as simple
as it appears. What are the implications? What makes it challenging? Can
I just remove the truncate on checkpoint option and chnage the database
maintenance plans to start backing up tran logs?
> Thanks for your insight.
>|||Thank you very much!