Showing posts with label configured. Show all posts
Showing posts with label configured. Show all posts

Tuesday, March 27, 2012

Error executing Backup

Hello,
I've configure "HP Omniback" to perform backups on databases servers under the account "omni_acc", when i configured this account i assign this account the "System Administrators" Server Role because i can=B4t did backups if the account wasn=B4t assign to this role.
Now i want to give to the omni_acc account other previleges since we have the "db_backupoperator" database role but... i cant do the backups if the user is only assign to this role. Can anybody explain to me this situation?
Is not supposed that a user assign to the "db_backupoperator" database role perform backups and restores to databases?
How can i give permissions to a user to make backups and restores of databases?
Best regardsFor RESTORE you cannot use db_backup operator if the database doesn't exist, as ... the database doesn't
exist! In this case, dbcreator server role should do.
Your problem is very likely that HP wrote their software so it requires this permissions. The place to start
is the documentation for the software. If there is no, ask the vendor of the software (HP).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message news:1919d01c44c8f$47eb8c30$a501280a@.phx.gbl...
Hello,
I've configure "HP Omniback" to perform backups on
databases servers under the account "omni_acc", when i
configured this account i assign this account the "System
Administrators" Server Role because i can´t did backups if
the account wasn´t assign to this role.
Now i want to give to the omni_acc account other
previleges since we have the "db_backupoperator" database
role but... i cant do the backups if the user is only
assign to this role. Can anybody explain to me this
situation?
Is not supposed that a user assign to
the "db_backupoperator" database role perform backups and
restores to databases?
How can i give permissions to a user to make backups and
restores of databases?
Best regards

error during SQL Server 2005 Express help...

The "Setup Progress" window displays the selected components to be configured.

After completion, the window displays a red x beside Reporting Services.

On all the other results, you can click and view a log generated during installation.

Clicking on the "Reporting Services" (that didn't install) does not display the log file.

Any help is appreciated.

Thanks,

Trint

You can get the setup logs from here - %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files. Look for the RS log that looks something like SQLSetup0001_<machinename>_RS.log

Thanks,

Sharmila

error during SQL Server 2005 Express help...

The "Setup Progress" window displays the selected components to be
configured.
After completion, the window displays a red x beside Reporting
Services.
On all the other results, you can click and view a log generated
during installation.
Clicking on the "Reporting Services" (that didn't install) does not
display the log file.
Any help is appreciated.
Thanks,
TrintOn Feb 16, 12:11 pm, "trint" <trinity.sm...@.gmail.com> wrote:
> The "Setup Progress" window displays the selected components to be
> configured.
> After completion, the window displays a red x beside Reporting
> Services.
> On all the other results, you can click and view a log generated
> during installation.
> Clicking on the "Reporting Services" (that didn't install) does not
> display the log file.
> Any help is appreciated.
> Thanks,
> Trint
I had this occur in the past, you can try to see if the reason for the
error appeared in the Event Viewer. I would suggest uninstalling SQL
Server 2005 Express and reinstalling it and of course, make sure that
you have all trial versions uninstalled before reinstalling it (where
applicable). Hope this helps.
Regards,
Enrique Martinez
Sr. SQL Server Developer|||On Feb 18, 7:26 pm, "EMartinez" <emartinez...@.gmail.com> wrote:
> On Feb 16, 12:11 pm, "trint" <trinity.sm...@.gmail.com> wrote:
> > The "Setup Progress" window displays the selected components to be
> > configured.
> > After completion, the window displays a red x beside Reporting
> > Services.
> > On all the other results, you can click and view a log generated
> > during installation.
> > Clicking on the "Reporting Services" (that didn't install) does not
> > display the log file.
> > Any help is appreciated.
> > Thanks,
> >Trint
> I had this occur in the past, you can try to see if the reason for the
> error appeared in the Event Viewer. I would suggest uninstalling SQL
> Server 2005 Express and reinstalling it and of course, make sure that
> you have all trial versions uninstalled before reinstalling it (where
> applicable). Hope this helps.
> Regards,
> Enrique Martinez
> Sr. SQL Server Developer
Enrique,
I did that and also on two different machines (same problem).
Thanks,
Trint

Monday, March 19, 2012

Error Creating a new cluster on windows 2003 Server EE SP1

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

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

Wednesday, March 7, 2012

Error connecting to Oracle via linked server after SP2 installatio

We have a test SQL Server box configured with the following:
Windows 2000, SP4
SQL Server: 8.00.944
Oracle Client Tools: 9.2.0.1
Microsoft ODBC for Oracle: 2.573.9030.00
We built a linked server to a 3rd party Oracle application. We used the
standard "Microsoft OLE DB Provider for Oracle" drvier from the drop down
list. We created views using this linked server and they worked fine.
However, after installing SP2 of Reporting Services, we now receive the
following error when we attempt to use the views:
[Microsoft][ODBC SQL Server Driver][SQL Server][OLE/DB provider returned
error message: Oracle client and networking components not found. These
components are supplied by Oracle Corporation and are part of the Oracle
Version 7.3.3 or later client software installation.
Provider is unable to function until these components are installed.]
We use a free SQL Tool called "Toad" to access the Oracle environment. This
tool uses the same Oracle Client Tools referred to in the error message.
This tool continues to function normally.
We really want to take advantage of some of the new features in SP2, but we
can't deploy this on our production SQL Reporting box until we get this issue
resolved. Any help in this matter would be greatly appreciated. Thanks!
--
Grande ApplicationsHello,
Microsoft OLE DB Provider for Oracle and Microsoft ODBC Driver for Oracle
are not supported with any Oracle versions later than 8i. For more
information, click the following article number to view the article in the
Microsoft Knowledge Base:
244661 Limitations of Microsoft Oracle ODBC Driver and OLE DB Provider
http://support.microsoft.com/default.aspx?scid=KB;EN-US;244661
Therefore, the cause of the issue is not related to the reporting service.
If you want to use Oracle version 9i, you can use the following settings in
step 3 of this procedure in the article 280106:
280106 How to set up and troubleshoot a linked server to Oracle in SQL
Server
http://support.microsoft.com/?id=280106
However, this configuration is not supported and is discouraged.
Oracle Client Microsoft Windows 2000
9.x
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxOCI]
"OracleXaLib"="oraclient9.dll"
"OracleSqlLib"="orasql9.dll"
"OracleOciLib"="oci.dll"
You can refer to the article 280106 to set up and troubleshoot a linked
server. I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Sophie,
Thanks much for your response. We were able to resolve the problem by
restarting the SQL server (SQL Server service); however, we have discovered
from others that this resolution has been known to provide only a temporary
fix.
Do you know where I can find a list of all of the files (and file versions)
installed and updated by Reporting Services SP 2? This would be very helpful
to us.
Thank you.
Grande Applications
Thank you
"Sophie Guo [MSFT]" wrote:
> Hello,
> Microsoft OLE DB Provider for Oracle and Microsoft ODBC Driver for Oracle
> are not supported with any Oracle versions later than 8i. For more
> information, click the following article number to view the article in the
> Microsoft Knowledge Base:
> 244661 Limitations of Microsoft Oracle ODBC Driver and OLE DB Provider
> http://support.microsoft.com/default.aspx?scid=KB;EN-US;244661
> Therefore, the cause of the issue is not related to the reporting service.
> If you want to use Oracle version 9i, you can use the following settings in
> step 3 of this procedure in the article 280106:
> 280106 How to set up and troubleshoot a linked server to Oracle in SQL
> Server
> http://support.microsoft.com/?id=280106
> However, this configuration is not supported and is discouraged.
> Oracle Client Microsoft Windows 2000
> 9.x
> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxOCI]
> "OracleXaLib"="oraclient9.dll"
> "OracleSqlLib"="orasql9.dll"
> "OracleOciLib"="oci.dll"
>
> You can refer to the article 280106 to set up and troubleshoot a linked
> server. I hope the information is helpful.
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> =====================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>

Error connecting to OLEDB for DB2

I'm attempting to configure a new Microsoft OLE DB Provider for DB2 connection using the provided Data Access Tool and Wizard. I'm configured for DB2\MVS TCP/IP and have my Catalog and other defaults set. When I go to connect I get the following:

Could not connect to data source 'New Data Source':
An internal network library error has occurred. A network level conversational protocol error has occurred. SQLSTATE: HY000, SQLCODE: -343

The port I've configured is what is used when we use the IBM OLE DB and ODBC drivers. Where can I look to see what the problem is?

Thanks,

Mike

I'm moving your thread to the Data Access forum as you'll have a greater chance of having an OLEDB question answered.|||

Hi,

some OLEDB providers have the functionality for logging implemented which can be turned on with a flag on the client side, this should give you more information about the error you ar egetting. The Provider flags are very specific so you should look in the documentation of the used provider.

HTH, jens Suessmeyer.


http://www.sqlserver2005.de

Friday, February 17, 2012

Error after service account removed from "SQLServer2005MSSQLUser" Group

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

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

Code Snippet

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

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

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

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

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

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

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

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

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

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

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

Does the server start successfully? - NO

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

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

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

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

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

Hi Ken,

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

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

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

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

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

|||

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

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

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

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

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

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

|||

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

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

Code Snippet

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

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

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

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SuperSocketNetLib

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

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

Code Snippet

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

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

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

Code Snippet

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

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer (and subfolders)

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

I'll post back later with additional results.

|||

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

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

"An error occurred during decryption"

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

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

|||

Hi Ken!

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

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

Many thanks!

|||

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

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

Local user is recommended.

Under "Minimum permissions", it says the following:

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

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

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

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

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

Error after service account removed from "SQLServer2005MSSQLUser" Group

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

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

Code Snippet

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

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

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

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

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

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

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

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

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

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

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

Does the server start successfully? - NO

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

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

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

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

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

Hi Ken,

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

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

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

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

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

|||

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

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

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

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

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

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

|||

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

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

Code Snippet

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

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

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

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SuperSocketNetLib

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

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

Code Snippet

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

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

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

Code Snippet

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

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer (and subfolders)

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

I'll post back later with additional results.

|||

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

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

"An error occurred during decryption"

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

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

|||

Hi Ken!

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

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

Many thanks!

|||

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

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

Local user is recommended.

Under "Minimum permissions", it says the following:

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

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

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

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

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

Error After Package Configuration

I have a package that executes succesfully before package is configured.

but when package is configured to use configuration details either from SQL Server configuration table or XML configuration file, gives an error :

[Connection manager "XYZ"] Error: An OLE DB error has occurred. Error code: 0x80040E21. An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040E21 Description: "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.".

Can anyone help me out with this ?

Experts !!! this is my second post, my previous post is still unanswered.

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

Can you share the configuration for connection manager "XYZ"? Also, are there any other error messages?|||

Details for Connection Manager XYZ

Provider: Native OLE DB\Microsoft OLE DB Provider for Oracle

Server Name : Ora_serv

UserName: User1

Pawwword: Password

Execution Result :

[DTS.Pipeline] Information: Validation phase is beginning.
Progress: Validating - 0 percent complete
Progress: Validating - 50 percent complete
[OLE DB Source "PQR" [1]] Error: The AcquireConnection method call to the connection manager "XYZ" failed with error code 0xC0202009.
[DTS.Pipeline] Error: component "OLE DB Source PQR" (1) failed validation and returned error code 0xC020801C.
Progress: Validating - 100 percent complete
[DTS.Pipeline] Error: One or more component failed validation.
Error: There were errors during task validation.
Validation is completed
[Connection manager "XYZ"] Error: An OLE DB error has occurred. Error code: 0x80040E21. An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040E21 Description: "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.".
Validation is completed|||I'm curious... Do you have the Oracle client installed by chance? If so (and you need it to be), do you have "Ora_serv" listed in the tnsnames.ora file?|||

Yup !!! i have configured all the settings. After disabling the package configuration, package executes succesfully for the same connections details that are there in dtsConfig file. One thing that i have noticed, SSIS is not saving password in the config file. Even in Connection string SSIS is not saving password for oracle server.

|||SSIS won't save the password in the configuration file on its own. You can edit the configuration file yourself and add it though.|||I have tried that too, but it results in error given above.
Connection string works, but i want to use either SQL Server Table or XML file.