ERROR EXECUTING EXTENDED STORED PROCEDURE Specified user can not login

Hello All,
I'm wrote a program that uses the extended stored procedure XP_CMDSHELL .
The user is not an admin and I'm not sure how to set up a Proxy account.
I'm getting the following error when I try to add the user into the
Non-SysAdmin job step proxy account.
ERROR EXECUTING EXTENDED STORED PROCEDURE Specified user can not login
I gave the users domain rights to the master database on the server and then
gave permission to use the XP_CMDSHELL procedure.
My knowledge on permissions in SQL SERVER 2000 is hazy and I would like to
know what steps I have to take to add a non-admin user to be able to use the
XP_CMDSHELL procedure. Do I have to set anything outside of SQL SERVER
2000?...
Any help will be greatly appreciated.
Thanks,
Matt
If the user invoking xp_cmdshell is not a member of the sysadmin role, the
proxy account will be used.
The proxy account is setup using the dialog on the SQL Agent property page
in SQL Enterprise Manager (Job System tab) or using the extend stored
procedure xp_sqlagent_proxy_account, see
http://msdn.microsoft.com/library/de...aa-sz_8sdm.asp
See http://www.databasejournal.com/featu...le.php/3372131 for
more background.
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2005 All rights reserved.
"Matthew Beirn" <mbeirn@.ssimed.com> wrote in message
news:u7EruuMTFHA.3336@.TK2MSFTNGP10.phx.gbl...
> Hello All,
> I'm wrote a program that uses the extended stored procedure XP_CMDSHELL .
> The user is not an admin and I'm not sure how to set up a Proxy account.
> I'm getting the following error when I try to add the user into the
> Non-SysAdmin job step proxy account.
> ERROR EXECUTING EXTENDED STORED PROCEDURE Specified user can not login
> I gave the users domain rights to the master database on the server and
> then gave permission to use the XP_CMDSHELL procedure.
> My knowledge on permissions in SQL SERVER 2000 is hazy and I would like to
> know what steps I have to take to add a non-admin user to be able to use
> the XP_CMDSHELL procedure. Do I have to set anything outside of SQL
> SERVER 2000?...
> Any help will be greatly appreciated.
> Thanks,
> Matt
>

ERROR EXECUTING EXTENDED STORED PROCEDURE Specified user can not login

Hello All,
I'm wrote a program that uses the extended stored procedure XP_CMDSHELL .
The user is not an admin and I'm not sure how to set up a Proxy account.
I'm getting the following error when I try to add the user into the
Non-SysAdmin job step proxy account.
ERROR EXECUTING EXTENDED STORED PROCEDURE Specified user can not login
I gave the users domain rights to the master database on the server and then
gave permission to use the XP_CMDSHELL procedure.
My knowledge on permissions in SQL SERVER 2000 is hazy and I would like to
know what steps I have to take to add a non-admin user to be able to use the
XP_CMDSHELL procedure. Do I have to set anything outside of SQL SERVER
2000?...
Any help will be greatly appreciated.
Thanks,
MattIf the user invoking xp_cmdshell is not a member of the sysadmin role, the
proxy account will be used.
The proxy account is setup using the dialog on the SQL Agent property page
in SQL Enterprise Manager (Job System tab) or using the extend stored
procedure xp_sqlagent_proxy_account, see
sz_8sdm.asp" target="_blank">http://msdn.microsoft.com/library/d.../>
sz_8sdm.asp
See http://www.databasejournal.com/feat...cle.php/3372131 for
more background.
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2005 All rights reserved.
"Matthew Beirn" <mbeirn@.ssimed.com> wrote in message
news:u7EruuMTFHA.3336@.TK2MSFTNGP10.phx.gbl...
> Hello All,
> I'm wrote a program that uses the extended stored procedure XP_CMDSHELL .
> The user is not an admin and I'm not sure how to set up a Proxy account.
> I'm getting the following error when I try to add the user into the
> Non-SysAdmin job step proxy account.
> ERROR EXECUTING EXTENDED STORED PROCEDURE Specified user can not login
> I gave the users domain rights to the master database on the server and
> then gave permission to use the XP_CMDSHELL procedure.
> My knowledge on permissions in SQL SERVER 2000 is hazy and I would like to
> know what steps I have to take to add a non-admin user to be able to use
> the XP_CMDSHELL procedure. Do I have to set anything outside of SQL
> SERVER 2000?...
> Any help will be greatly appreciated.
> Thanks,
> Matt
>

ERROR EXECUTING EXTENDED STORED PROCEDURE Specified user can not login

Hello All,
I'm wrote a program that uses the extended stored procedure XP_CMDSHELL .
The user is not an admin and I'm not sure how to set up a Proxy account.
I'm getting the following error when I try to add the user into the
Non-SysAdmin job step proxy account.
ERROR EXECUTING EXTENDED STORED PROCEDURE Specified user can not login
I gave the users domain rights to the master database on the server and then
gave permission to use the XP_CMDSHELL procedure.
My knowledge on permissions in SQL SERVER 2000 is hazy and I would like to
know what steps I have to take to add a non-admin user to be able to use the
XP_CMDSHELL procedure. Do I have to set anything outside of SQL SERVER
2000?...
Any help will be greatly appreciated.
Thanks,
MattIf the user invoking xp_cmdshell is not a member of the sysadmin role, the
proxy account will be used.
The proxy account is setup using the dialog on the SQL Agent property page
in SQL Enterprise Manager (Job System tab) or using the extend stored
procedure xp_sqlagent_proxy_account, see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_xp_aa-sz_8sdm.asp
See http://www.databasejournal.com/features/mssql/article.php/3372131 for
more background.
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright © SQLDev.Net 1991-2005 All rights reserved.
"Matthew Beirn" <mbeirn@.ssimed.com> wrote in message
news:u7EruuMTFHA.3336@.TK2MSFTNGP10.phx.gbl...
> Hello All,
> I'm wrote a program that uses the extended stored procedure XP_CMDSHELL .
> The user is not an admin and I'm not sure how to set up a Proxy account.
> I'm getting the following error when I try to add the user into the
> Non-SysAdmin job step proxy account.
> ERROR EXECUTING EXTENDED STORED PROCEDURE Specified user can not login
> I gave the users domain rights to the master database on the server and
> then gave permission to use the XP_CMDSHELL procedure.
> My knowledge on permissions in SQL SERVER 2000 is hazy and I would like to
> know what steps I have to take to add a non-admin user to be able to use
> the XP_CMDSHELL procedure. Do I have to set anything outside of SQL
> SERVER 2000?...
> Any help will be greatly appreciated.
> Thanks,
> Matt
>sql

Error during Execute sp with IMAGE parameter

Hello.
It is the first time that Im using IMAGE field type..

I created a stored procedure that should return an IMAGE field back to a
c-sharp program .
(@.OutImg IMAGE declared as an output parameter of the procedure.)
(Select @.OutImg = ImgFld from table)
Well,I can compile it , but when execute i get this error :
Msg 2739, Level 16, State 1, Line 14
The text, ntext, and image data types are invalid for local variable.

Is there something I can do ,OR should I use any cast/convert func to solve it ..?
Many thanks.:ofrom 2005 BOL:

text, ntext, and image parameters cannot be used as OUTPUT parameters, unless the procedure is a CLR procedure.

So you'll have to return this in a record set, not in an OUT param.

error during backup

when a database backup is tried to be taken to the hard disk it gives a
error "Write on 'F:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\****.bak'
failed, status =112". The path was changed several times and checked the
same error message was occurring.
Any Clues?
Regards
Sunil Pinto
Hi
Some entry in the ERROR LOG file?
"Sunil Pinto" <SunilPinto@.hotmail.com> wrote in message
news:elnTTAPtEHA.2688@.TK2MSFTNGP14.phx.gbl...
> when a database backup is tried to be taken to the hard disk it gives a
> error "Write on 'F:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\****.bak'
> failed, status =112". The path was changed several times and checked the
> same error message was occurring.
> Any Clues?
> Regards
> Sunil Pinto
>
|||Sunil,
You've run out of disk space. Check how much space is available on your
drives by executing
exec master..xp_fixeddrives
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Sunil Pinto wrote:
> when a database backup is tried to be taken to the hard disk it gives a
> error "Write on 'F:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\****.bak'
> failed, status =112". The path was changed several times and checked the
> same error message was occurring.
> Any Clues?
> Regards
> Sunil Pinto
>

error during backup

when a database backup is tried to be taken to the hard disk it gives a
error "Write on 'F:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\****.bak
'
failed, status =112". The path was changed several times and checked the
same error message was occurring.
Any Clues?
Regards
Sunil PintoHi
Some entry in the ERROR LOG file?
"Sunil Pinto" <SunilPinto@.hotmail.com> wrote in message
news:elnTTAPtEHA.2688@.TK2MSFTNGP14.phx.gbl...
> when a database backup is tried to be taken to the hard disk it gives a
> error "Write on 'F:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\****.bak'
> failed, status =112". The path was changed several times and checked the
> same error message was occurring.
> Any Clues?
> Regards
> Sunil Pinto
>|||Sunil,
You've run out of disk space. Check how much space is available on your
drives by executing
exec master..xp_fixeddrives
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Sunil Pinto wrote:
> when a database backup is tried to be taken to the hard disk it gives a
> error "Write on 'F:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\****.b
ak'
> failed, status =112". The path was changed several times and checked the
> same error message was occurring.
> Any Clues?
> Regards
> Sunil Pinto
>

error during backup

when a database backup is tried to be taken to the hard disk it gives a
error "Write on 'F:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\****.bak'
failed, status =112". The path was changed several times and checked the
same error message was occurring.
Any Clues?
Regards
Sunil PintoHi
Some entry in the ERROR LOG file?
"Sunil Pinto" <SunilPinto@.hotmail.com> wrote in message
news:elnTTAPtEHA.2688@.TK2MSFTNGP14.phx.gbl...
> when a database backup is tried to be taken to the hard disk it gives a
> error "Write on 'F:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\****.bak'
> failed, status =112". The path was changed several times and checked the
> same error message was occurring.
> Any Clues?
> Regards
> Sunil Pinto
>|||Sunil,
You've run out of disk space. Check how much space is available on your
drives by executing
exec master..xp_fixeddrives
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Sunil Pinto wrote:
> when a database backup is tried to be taken to the hard disk it gives a
> error "Write on 'F:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\****.bak'
> failed, status =112". The path was changed several times and checked the
> same error message was occurring.
> Any Clues?
> Regards
> Sunil Pinto
>

Error connection to MSDE

Hi all,
I have the Windows 2003 Server in my company and the MSDE SP3 install with
an instance for a program. But the program can't access the database, I have
tried to create a new data source to SQL Server in ODBC and it tells me SQL
Server Error: 11004 (Connection failed) and SQL Server Error: 6 (Specified
SQL server not found).
The MSDE is running with the name "SERVER\INSTANCE". I have enabled the
protocols in SVRNETCN.
Does anyone know what to do?
Thanks
Hi,
From the SQL server MSDE installed machine can you try to connect to SQL
server using both authentication using OSQL.
OSQL -Sservername -Usa -Ppassword
The aove command is suppose to go to a SQL Prompt. If it does then your SQL
server is working fine.If it is not look into sql serevr logs and find the
rason why sql server is down.
If your first stpe passed then, From command prompt execute a PING from your
client PC to MSDE server.
If it fail "Request time out" then it is a network issue.
Thanks
Hari
MCDBA
"Pedro" <pedronazario@.timetech.pt> wrote in message
news:4065ce47$0$3527$a729d347@.news.telepac.pt...
> Hi all,
>
> I have the Windows 2003 Server in my company and the MSDE SP3 install with
> an instance for a program. But the program can't access the database, I
have
> tried to create a new data source to SQL Server in ODBC and it tells me
SQL
> Server Error: 11004 (Connection failed) and SQL Server Error: 6 (Specified
> SQL server not found).
>
> The MSDE is running with the name "SERVER\INSTANCE". I have enabled the
> protocols in SVRNETCN.
>
> Does anyone know what to do?
>
> Thanks
>
|||By default only shared memory is enabled when you install MSDE. If the
connection is being made from a remote machine or uisng TCP/IP or named
pipes to connect locally the connection will fail. You can use svrnetcn.exe
(SQL Server Network Utiltiy) to enable TCP/IP and/or named pipes.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Error connection to MSDE

Hi all,
I have the Windows 2003 Server in my company and the MSDE SP3 install with
an instance for a program. But the program can't access the database, I have
tried to create a new data source to SQL Server in ODBC and it tells me SQL
Server Error: 11004 (Connection failed) and SQL Server Error: 6 (Specified
SQL server not found).
The MSDE is running with the name "SERVER\INSTANCE". I have enabled the
protocols in SVRNETCN.
Does anyone know what to do?
ThanksHi,
From the SQL server MSDE installed machine can you try to connect to SQL
server using both authentication using OSQL.
OSQL -Sservername -Usa -Ppassword
The aove command is suppose to go to a SQL Prompt. If it does then your SQL
server is working fine.If it is not look into sql serevr logs and find the
rason why sql server is down.
If your first stpe passed then, From command prompt execute a PING from your
client PC to MSDE server.
If it fail "Request time out" then it is a network issue.
Thanks
Hari
MCDBA
"Pedro" <pedronazario@.timetech.pt> wrote in message
news:4065ce47$0$3527$a729d347@.news.telepac.pt...
> Hi all,
>
> I have the Windows 2003 Server in my company and the MSDE SP3 install with
> an instance for a program. But the program can't access the database, I
have
> tried to create a new data source to SQL Server in ODBC and it tells me
SQL
> Server Error: 11004 (Connection failed) and SQL Server Error: 6 (Specified
> SQL server not found).
>
> The MSDE is running with the name "SERVER\INSTANCE". I have enabled the
> protocols in SVRNETCN.
>
> Does anyone know what to do?
>
> Thanks
>|||By default only shared memory is enabled when you install MSDE. If the
connection is being made from a remote machine or uisng TCP/IP or named
pipes to connect locally the connection will fail. You can use svrnetcn.exe
(SQL Server Network Utiltiy) to enable TCP/IP and/or named pipes.
Rand
This posting is provided "as is" with no warranties and confers no rights.

error conection frm clients to the sqlserver

hi
dear members
we have a program that its database is SQLserver2000 that installed on a
computer with ' MIS' name.the type of SQLserver installation is mixed mod
e
(not Authentication ). so , 2 weeks ago the program did run on all of the
network clients without login to the SQlserver besuse the sqlserver is mixed
mod. but now our SQl server has a problem besouse for runing the program on
any client on the network, first we have to login to the SQLserver compute
r
then run the application program . but we want to run the software with
sqlserver database without login to SQLserver computer.
note: My connection from program to SQLserver is ADO Connection with mixed
mode(user name=SA , password = blank""first we have to login to the SQLserver computer
then run the application program ""
Not sure what you mean...are you saying that when you open the application,
you get a username/password prompt, or are you actually logging into the
SQL Server via remote desktop/terminal server?
What is the application? Access? VB.Net?
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"ahi" <ahi@.discussions.microsoft.com> wrote in message
news:594B3C9D-D780-462E-93B7-C3CF683AA3D3@.microsoft.com...
> hi
> dear members
> we have a program that its database is SQLserver2000 that installed on a
> computer with ' MIS' name.the type of SQLserver installation is mixed
> mode
> (not Authentication ). so , 2 weeks ago the program did run on all of the
> network clients without login to the SQlserver besuse the sqlserver is
> mixed
> mod. but now our SQl server has a problem besouse for runing the program
> on
> any client on the network, first we have to login to the SQLserver
> computer
> then run the application program . but we want to run the software with
> sqlserver database without login to SQLserver computer.
> note: My connection from program to SQLserver is ADO Connection with mixed
> mode(user name=SA , password = blank

error conection frm clients to the sqlserver

hi
dear members
we have a program that its database is SQLserver2000 that installed on a
computer with ' MIS' name.the type of SQLserver installation is mixed mode
(not Authentication ). so , 2 weeks ago the program did run on all of the
network clients without login to the SQlserver besuse the sqlserver is mixed
mod. but now our SQl server has a problem besouse for runing the program on
any client on the network, first we have to login to the SQLserver computer
then run the application program . but we want to run the software with
sqlserver database without login to SQLserver computer.
note: My connection from program to SQLserver is ADO Connection with mixed
mode(user name=SA , password = blank
""first we have to login to the SQLserver computer
then run the application program ""
Not sure what you mean...are you saying that when you open the application,
you get a username/password prompt, or are you actually logging into the
SQL Server via remote desktop/terminal server?
What is the application? Access? VB.Net?
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"ahi" <ahi@.discussions.microsoft.com> wrote in message
news:594B3C9D-D780-462E-93B7-C3CF683AA3D3@.microsoft.com...
> hi
> dear members
> we have a program that its database is SQLserver2000 that installed on a
> computer with ' MIS' name.the type of SQLserver installation is mixed
> mode
> (not Authentication ). so , 2 weeks ago the program did run on all of the
> network clients without login to the SQlserver besuse the sqlserver is
> mixed
> mod. but now our SQl server has a problem besouse for runing the program
> on
> any client on the network, first we have to login to the SQLserver
> computer
> then run the application program . but we want to run the software with
> sqlserver database without login to SQLserver computer.
> note: My connection from program to SQLserver is ADO Connection with mixed
> mode(user name=SA , password = blank

Error Code

Error messages:
Source: mscorlib
Target Site: Void WinIOError(Int32, System.String)
Message: Access to the path 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\ReplData\unc\Servername_ADVENTUREWORKS_ADVWORKSPRODUCTTRANS\20070625161637\' is denied.
Stack: at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.Directory.InternalCreateDirectory(String fullPath, String path, DirectorySecurity dirSecurity)
at System.IO.Directory.CreateDirectory(String path, DirectorySecurity directorySecurity)
at Microsoft.SqlServer.Replication.Utilities.CreateDirectoryWithExtendedErrorInformation(String directory)
at Microsoft.SqlServer.Replication.Snapshot.SnapshotProvider.CreateSnapshotFolders()
at Microsoft.SqlServer.Replication.Snapshot.SqlServerSnapshotProvider.GenerateSnapshot()
at Microsoft.SqlServer.Replication.SnapshotGenerationAgent.InternalRun()
at Microsoft.SqlServer.Replication.AgentCore.Run() (Source: mscorlib, Error number: 0)

I totally followed by tutorials of replication, repldata is new created folder

sharing for windowns accounts like shown below

repl_distribution read

repl_merge read

repl_snapshot Full control

the settting for these accounts same with security setting

any idea about this error?

many thanks

Can you confirm that xp_cmdshell is enabled? Also can you confirm that the account your snapshot agent is running under (either the windows impersonation account, of the SQL Server agent account on your publisher) has write, and list files and folders rights on the publisher?

Error changing startup parameters after 8patch

Please help! Here is what happened in details:
----
Originally, the SQL Server install placed the data and log files in
d:\Program Files\Microsoft SQL Server\MSSQL\Data\ folder and the error
logs in d:\Program Files\Microsoft SQL Server\MSSQL\Log folder.
----
For syntactical (commands that do not like spaces in folder or file
names) and security and organizational (separate data and logs to
different drives) reasons, I decided to place them in various
locations. Using http://support.microsoft.com/?kbid=224071 as a
guide, I moved the data file to d:\mssql\data\ and log files to
e:\mssql\transaction_log\ and error logs to e:\mssql\error_log\ by
changing the startup parameters:
-dD:\MSSQL\Data\master.mdf
-lE:\MSSQL\Transaction_Log\mastlog.ldf
-eE:\MSSQL\Error_Log
I followed the exact steps detailed from the link ("Moving the Master
Database").
No problems occurred.
----
I remember I ran the above procedures twice because I renamed one of
the Tlog folder to Transaction_Log. Again, that did not pose any
problems.
----
From time to time, Window updates and this patch were installed on
this machine:
- - ---
Title: Cumulative Patch for Microsoft SQL Server (815495)
Date: 23 July 2003
Software:
- Microsoft SQL Server 7.0
- Microsoft Data Engine (MSDE) 1.0
- Microsoft SQL Server 2000
- Microsoft SQL Server 2000 Desktop Engine (MSDE 2000)
- Microsoft SQL Server 2000 Desktop Engine (Windows)
Impact: Run code of attacker's choice
Max Risk: Important
Bulletin: MS03-031
Microsoft encourages customers to review the Security Bulletins at:
http://www.microsoft.com/technet/security/bulletin/MS03-031.asp
http://www.microsoft.com/security/security_bulletins/ms03-031.asp
- ---
----
The next time, I again attempted to change the location of the error
log file by changing the startup parameters to
-eD:\MSSQL\Process_Log\SQL_Error_Log. On step 8 of the "Moving the
Master Database" instructions, SQL Server was having problems starting
up. The error message received was:
initerrlog: Could not open error log file
'D:\MSSQL\Process_Log\SQL_Error_Log'. Operating system error = 5(Access is denied.).
You could not start SQL Server from anywhere except I found that
running sqlservr.exe from the command prompt with the temporary
startup parameters of the error log file of the original location
worked (sqlservr.exe -eD:\Program Files\Microsoft SQL
Server\MSSQL\Log). SQL server runs under this mode, but SQL Server
Agent cannot start up even still.
While the SQL Server is running using the above command, I attempted
to change the Master Start Parameters of the Error Log back to
-eE:\MSSQL\Error_Log
and even -ed:\Program Files\Microsoft SQL Server\MSSQL\Log
but found no success starting the SQL Server with Enterprise Manager
or Services interfaces (sqlservr.exe was shutdown prior to attempt).
----
I am led to believe that the patch 815495 may have been involved with
the error. There have been times where Enterprise Manager freezes up
and automatically shuts down (occurs at least once a week) when
working within EM such as opening properties of Database Maintenance
Plan. This had not occurred before. In addition all the SQL logs
have been wiped out.
I have installed the same patch to my personal WinXP machine and the
Enterprise Manager no longer works (unable to open and receive an
error message to forward error to Microsoft) even with a reinstall.
These same results occurred on two server machines which were prepared
for production and standby. I don't know what else to do? Please
help!
Thanks so much,
JuneThe Error message you are receiving is access is denied to the log files.
Check your NTFS permissions, and make sure that the SQL Server account has
full control of the log files and the folder that they are in.
--
Denny Cherry
DBA
GameSpy Industries
"June" <jnguyen@.harbourcg.com> wrote in message
news:29f6d8aa.0309121232.54032ff@.posting.google.com...
> Please help! Here is what happened in details:
> ----
--
> Originally, the SQL Server install placed the data and log files in
> d:\Program Files\Microsoft SQL Server\MSSQL\Data\ folder and the error
> logs in d:\Program Files\Microsoft SQL Server\MSSQL\Log folder.
> ----
--
> For syntactical (commands that do not like spaces in folder or file
> names) and security and organizational (separate data and logs to
> different drives) reasons, I decided to place them in various
> locations. Using http://support.microsoft.com/?kbid=224071 as a
> guide, I moved the data file to d:\mssql\data\ and log files to
> e:\mssql\transaction_log\ and error logs to e:\mssql\error_log\ by
> changing the startup parameters:
> -dD:\MSSQL\Data\master.mdf
> -lE:\MSSQL\Transaction_Log\mastlog.ldf
> -eE:\MSSQL\Error_Log
> I followed the exact steps detailed from the link ("Moving the Master
> Database").
> No problems occurred.
> ----
--
> I remember I ran the above procedures twice because I renamed one of
> the Tlog folder to Transaction_Log. Again, that did not pose any
> problems.
> ----
--
> From time to time, Window updates and this patch were installed on
> this machine:
> - - ---
> Title: Cumulative Patch for Microsoft SQL Server (815495)
> Date: 23 July 2003
> Software:
> - Microsoft SQL Server 7.0
> - Microsoft Data Engine (MSDE) 1.0
> - Microsoft SQL Server 2000
> - Microsoft SQL Server 2000 Desktop Engine (MSDE 2000)
> - Microsoft SQL Server 2000 Desktop Engine (Windows)
> Impact: Run code of attacker's choice
> Max Risk: Important
> Bulletin: MS03-031
> Microsoft encourages customers to review the Security Bulletins at:
> http://www.microsoft.com/technet/security/bulletin/MS03-031.asp
> http://www.microsoft.com/security/security_bulletins/ms03-031.asp
> - ---
> ----
--
> The next time, I again attempted to change the location of the error
> log file by changing the startup parameters to
> -eD:\MSSQL\Process_Log\SQL_Error_Log. On step 8 of the "Moving the
> Master Database" instructions, SQL Server was having problems starting
> up. The error message received was:
> initerrlog: Could not open error log file
> 'D:\MSSQL\Process_Log\SQL_Error_Log'. Operating system error => 5(Access is denied.).
> You could not start SQL Server from anywhere except I found that
> running sqlservr.exe from the command prompt with the temporary
> startup parameters of the error log file of the original location
> worked (sqlservr.exe -eD:\Program Files\Microsoft SQL
> Server\MSSQL\Log). SQL server runs under this mode, but SQL Server
> Agent cannot start up even still.
> While the SQL Server is running using the above command, I attempted
> to change the Master Start Parameters of the Error Log back to
> -eE:\MSSQL\Error_Log
> and even -ed:\Program Files\Microsoft SQL Server\MSSQL\Log
> but found no success starting the SQL Server with Enterprise Manager
> or Services interfaces (sqlservr.exe was shutdown prior to attempt).
> ----
--
> I am led to believe that the patch 815495 may have been involved with
> the error. There have been times where Enterprise Manager freezes up
> and automatically shuts down (occurs at least once a week) when
> working within EM such as opening properties of Database Maintenance
> Plan. This had not occurred before. In addition all the SQL logs
> have been wiped out.
> I have installed the same patch to my personal WinXP machine and the
> Enterprise Manager no longer works (unable to open and receive an
> error message to forward error to Microsoft) even with a reinstall.
> These same results occurred on two server machines which were prepared
> for production and standby. I don't know what else to do? Please
> help!
> Thanks so much,
> June