Regarding the above errors, I decided to apply sp4. A copy of the database was made and placed on a test server and now we cannot start the SQL Server. I have checked the registration and all seems fine. Any ideas ?Check the contents of the ERRORLOG file in LOGS directory as well as Application and System errorlog in Event Viewer and let us know what you see there.|||You need to identify what the base cause of this problem is. The first step to doing that is reviewing all errors on the machine in question.|||The above problem is now okay. DBAs from another Department came over and assisted with the problem. Because we had problems moving the data to another location, we decided to make a copy of the database and run DBCC repair on the production database. This fixed the problem and only a few records were lost.
Thanks to all for your assistance.
Showing posts with label copy. Show all posts
Showing posts with label copy. Show all posts
Monday, March 26, 2012
Friday, March 9, 2012
ERROR 5120
I tried attach/detach approach to migrate sql server 2000 databases to sql 2005. I installed a fresh copy of sql server 2005 on windows 2003 server. I could move most of my databases except one. While attaching the database to the sql 2005 I got the following error:
Unable to oen "c:\program files\microsoftSQL server \MSSQL.1\MSSQL\DATA\mydb_log.ldf". operating system error 32:" 32(the process cannot access the file because it is being used by another process)". microsoft SQL server, error:5120)
You must be attaching the wrong file (one being used by another database).|||I have a similar problem with the same error:
1) Detached MyDb.mdf (and .ldf) (Auto close = True)
2) copied MyDb.mdf and MyDb.ldf to a different folder
3) Re-attached MyDb from original location
4) Renamed copy to MyDbX.mdf and MyDbX.ldf
5) Attach copy (MyDbX.mdf), and in attach dialog change "Attach As" column to MyDbX
= Error 5120
Problem was the rename at step 4. Without this step the attach works OK, with step 5 renaming the database.
Without going back to check, I think step 4 was ok in SQL 2000 EM.
Sunday, February 26, 2012
error 3146
Only one user has the problem.
I have given them a new copy of the switchboard but same startup error.
Thank you for your help.
>
> IOSDSQL 664-964 ENTER SQLSetStmtOption
> HSTMT 0A0B1EC8
> UWORD 0 <SQL_QUERY_TIMEOUT>
> SQLPOINTER 0x0000003C
>
> IOSDSQL 664-964 EXIT SQLSetStmtOption with return code 0
> (SQL_SUCCESS)
> HSTMT 0A0B1EC8
> UWORD 0 <SQL_QUERY_TIMEOUT>
> SQLPOINTER 0x0000003C (BADMEM)
>
> IOSDSQL 664-964 ENTER SQLExecDirect
> HSTMT 0A0B1EC8
> UCHAR * 0x09FB18C0 [ -3] "SELECT
> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int:No" FROM
> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
> SDWORD -3
>
> IOSDSQL 664-964 EXIT SQLExecDirect with return code -1
> (SQL_ERROR)
> HSTMT 0A0B1EC8
> UCHAR * 0x09FB18C0 [ -3] "SELECT
> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int:No" FROM
> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
> SDWORD -3
>
> DIAG [37000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1:
> Incorrect syntax near '.'. (170)
>Check to make sure QUOTED_IDENTIFIER is ON.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"BrianMultilLanguage" <brian@.clilang.com> wrote in message
news:12kv1p37855g42@.corp.supernews.com...
> Only one user has the problem.
> I have given them a new copy of the switchboard but same startup error.
> Thank you for your help.
>> IOSDSQL 664-964 ENTER SQLSetStmtOption
>> HSTMT 0A0B1EC8
>> UWORD 0 <SQL_QUERY_TIMEOUT>
>> SQLPOINTER 0x0000003C
>> IOSDSQL 664-964 EXIT SQLSetStmtOption with return code 0
>> (SQL_SUCCESS)
>> HSTMT 0A0B1EC8
>> UWORD 0 <SQL_QUERY_TIMEOUT>
>> SQLPOINTER 0x0000003C (BADMEM)
>> IOSDSQL 664-964 ENTER SQLExecDirect
>> HSTMT 0A0B1EC8
>> UCHAR * 0x09FB18C0 [ -3] "SELECT
>> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int:No" FROM
>> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
>> SDWORD -3
>> IOSDSQL 664-964 EXIT SQLExecDirect with return code -1
>> (SQL_ERROR)
>> HSTMT 0A0B1EC8
>> UCHAR * 0x09FB18C0 [ -3] "SELECT
>> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int:No" FROM
>> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
>> SDWORD -3
>> DIAG [37000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1:
>> Incorrect syntax near '.'. (170)
>|||BINGO~!
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:59C18CE9-04B5-49E1-87AB-4EA2DAD4E977@.microsoft.com...
> Check to make sure QUOTED_IDENTIFIER is ON.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "BrianMultilLanguage" <brian@.clilang.com> wrote in message
> news:12kv1p37855g42@.corp.supernews.com...
>> Only one user has the problem.
>> I have given them a new copy of the switchboard but same startup error.
>> Thank you for your help.
>>
>> IOSDSQL 664-964 ENTER SQLSetStmtOption
>> HSTMT 0A0B1EC8
>> UWORD 0 <SQL_QUERY_TIMEOUT>
>> SQLPOINTER 0x0000003C
>> IOSDSQL 664-964 EXIT SQLSetStmtOption with return code 0
>> (SQL_SUCCESS)
>> HSTMT 0A0B1EC8
>> UWORD 0 <SQL_QUERY_TIMEOUT>
>> SQLPOINTER 0x0000003C (BADMEM)
>> IOSDSQL 664-964 ENTER SQLExecDirect
>> HSTMT 0A0B1EC8
>> UCHAR * 0x09FB18C0 [ -3] "SELECT
>> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int:No" FROM
>> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
>> SDWORD -3
>> IOSDSQL 664-964 EXIT SQLExecDirect with return code -1
>> (SQL_ERROR)
>> HSTMT 0A0B1EC8
>> UCHAR * 0x09FB18C0 [ -3] "SELECT
>> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int:No" FROM
>> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
>> SDWORD -3
>> DIAG [37000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1:
>> Incorrect syntax near '.'. (170)
>>
>
I have given them a new copy of the switchboard but same startup error.
Thank you for your help.
>
> IOSDSQL 664-964 ENTER SQLSetStmtOption
> HSTMT 0A0B1EC8
> UWORD 0 <SQL_QUERY_TIMEOUT>
> SQLPOINTER 0x0000003C
>
> IOSDSQL 664-964 EXIT SQLSetStmtOption with return code 0
> (SQL_SUCCESS)
> HSTMT 0A0B1EC8
> UWORD 0 <SQL_QUERY_TIMEOUT>
> SQLPOINTER 0x0000003C (BADMEM)
>
> IOSDSQL 664-964 ENTER SQLExecDirect
> HSTMT 0A0B1EC8
> UCHAR * 0x09FB18C0 [ -3] "SELECT
> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int:No" FROM
> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
> SDWORD -3
>
> IOSDSQL 664-964 EXIT SQLExecDirect with return code -1
> (SQL_ERROR)
> HSTMT 0A0B1EC8
> UCHAR * 0x09FB18C0 [ -3] "SELECT
> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int:No" FROM
> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
> SDWORD -3
>
> DIAG [37000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1:
> Incorrect syntax near '.'. (170)
>Check to make sure QUOTED_IDENTIFIER is ON.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"BrianMultilLanguage" <brian@.clilang.com> wrote in message
news:12kv1p37855g42@.corp.supernews.com...
> Only one user has the problem.
> I have given them a new copy of the switchboard but same startup error.
> Thank you for your help.
>> IOSDSQL 664-964 ENTER SQLSetStmtOption
>> HSTMT 0A0B1EC8
>> UWORD 0 <SQL_QUERY_TIMEOUT>
>> SQLPOINTER 0x0000003C
>> IOSDSQL 664-964 EXIT SQLSetStmtOption with return code 0
>> (SQL_SUCCESS)
>> HSTMT 0A0B1EC8
>> UWORD 0 <SQL_QUERY_TIMEOUT>
>> SQLPOINTER 0x0000003C (BADMEM)
>> IOSDSQL 664-964 ENTER SQLExecDirect
>> HSTMT 0A0B1EC8
>> UCHAR * 0x09FB18C0 [ -3] "SELECT
>> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int:No" FROM
>> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
>> SDWORD -3
>> IOSDSQL 664-964 EXIT SQLExecDirect with return code -1
>> (SQL_ERROR)
>> HSTMT 0A0B1EC8
>> UCHAR * 0x09FB18C0 [ -3] "SELECT
>> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int:No" FROM
>> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
>> SDWORD -3
>> DIAG [37000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1:
>> Incorrect syntax near '.'. (170)
>|||BINGO~!
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:59C18CE9-04B5-49E1-87AB-4EA2DAD4E977@.microsoft.com...
> Check to make sure QUOTED_IDENTIFIER is ON.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "BrianMultilLanguage" <brian@.clilang.com> wrote in message
> news:12kv1p37855g42@.corp.supernews.com...
>> Only one user has the problem.
>> I have given them a new copy of the switchboard but same startup error.
>> Thank you for your help.
>>
>> IOSDSQL 664-964 ENTER SQLSetStmtOption
>> HSTMT 0A0B1EC8
>> UWORD 0 <SQL_QUERY_TIMEOUT>
>> SQLPOINTER 0x0000003C
>> IOSDSQL 664-964 EXIT SQLSetStmtOption with return code 0
>> (SQL_SUCCESS)
>> HSTMT 0A0B1EC8
>> UWORD 0 <SQL_QUERY_TIMEOUT>
>> SQLPOINTER 0x0000003C (BADMEM)
>> IOSDSQL 664-964 ENTER SQLExecDirect
>> HSTMT 0A0B1EC8
>> UCHAR * 0x09FB18C0 [ -3] "SELECT
>> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int:No" FROM
>> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
>> SDWORD -3
>> IOSDSQL 664-964 EXIT SQLExecDirect with return code -1
>> (SQL_ERROR)
>> HSTMT 0A0B1EC8
>> UCHAR * 0x09FB18C0 [ -3] "SELECT
>> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int:No" FROM
>> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
>> SDWORD -3
>> DIAG [37000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1:
>> Incorrect syntax near '.'. (170)
>>
>
error 3146
Only one user has the problem.
I have given them a new copy of the switchboard but same startup error.
Thank you for your help.
> IOSDSQL 664-964 ENTER SQLSetStmtOption
> HSTMT 0A0B1EC8
> UWORD 0 <SQL_QUERY_TIMEOUT>
> SQLPOINTER 0x0000003C
> IOSDSQL 664-964 EXIT SQLSetStmtOption with return code 0
> (SQL_SUCCESS)
> HSTMT 0A0B1EC8
> UWORD 0 <SQL_QUERY_TIMEOUT>
> SQLPOINTER 0x0000003C (BADMEM)
> IOSDSQL 664-964 ENTER SQLExecDirect
> HSTMT 0A0B1EC8
> UCHAR * 0x09FB18C0 [ -3] "SELECT
> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int: No" FROM
> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
> SDWORD -3
> IOSDSQL 664-964 EXIT SQLExecDirect with return code -1
> (SQL_ERROR)
> HSTMT 0A0B1EC8
> UCHAR * 0x09FB18C0 [ -3] "SELECT
> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int: No" FROM
> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
> SDWORD -3
> DIAG [37000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1:
> Incorrect syntax near '.'. (170)
>
Check to make sure QUOTED_IDENTIFIER is ON.
Hope this helps.
Dan Guzman
SQL Server MVP
"BrianMultilLanguage" <brian@.clilang.com> wrote in message
news:12kv1p37855g42@.corp.supernews.com...
> Only one user has the problem.
> I have given them a new copy of the switchboard but same startup error.
> Thank you for your help.
>
>
|||BINGO~!
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:59C18CE9-04B5-49E1-87AB-4EA2DAD4E977@.microsoft.com...
> Check to make sure QUOTED_IDENTIFIER is ON.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "BrianMultilLanguage" <brian@.clilang.com> wrote in message
> news:12kv1p37855g42@.corp.supernews.com...
>
I have given them a new copy of the switchboard but same startup error.
Thank you for your help.
> IOSDSQL 664-964 ENTER SQLSetStmtOption
> HSTMT 0A0B1EC8
> UWORD 0 <SQL_QUERY_TIMEOUT>
> SQLPOINTER 0x0000003C
> IOSDSQL 664-964 EXIT SQLSetStmtOption with return code 0
> (SQL_SUCCESS)
> HSTMT 0A0B1EC8
> UWORD 0 <SQL_QUERY_TIMEOUT>
> SQLPOINTER 0x0000003C (BADMEM)
> IOSDSQL 664-964 ENTER SQLExecDirect
> HSTMT 0A0B1EC8
> UCHAR * 0x09FB18C0 [ -3] "SELECT
> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int: No" FROM
> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
> SDWORD -3
> IOSDSQL 664-964 EXIT SQLExecDirect with return code -1
> (SQL_ERROR)
> HSTMT 0A0B1EC8
> UCHAR * 0x09FB18C0 [ -3] "SELECT
> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int: No" FROM
> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
> SDWORD -3
> DIAG [37000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1:
> Incorrect syntax near '.'. (170)
>
Check to make sure QUOTED_IDENTIFIER is ON.
Hope this helps.
Dan Guzman
SQL Server MVP
"BrianMultilLanguage" <brian@.clilang.com> wrote in message
news:12kv1p37855g42@.corp.supernews.com...
> Only one user has the problem.
> I have given them a new copy of the switchboard but same startup error.
> Thank you for your help.
>
>
|||BINGO~!
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:59C18CE9-04B5-49E1-87AB-4EA2DAD4E977@.microsoft.com...
> Check to make sure QUOTED_IDENTIFIER is ON.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "BrianMultilLanguage" <brian@.clilang.com> wrote in message
> news:12kv1p37855g42@.corp.supernews.com...
>
error 3146
Only one user has the problem.
I have given them a new copy of the switchboard but same startup error.
Thank you for your help.
> IOSDSQL 664-964 ENTER SQLSetStmtOption
> HSTMT 0A0B1EC8
> UWORD 0 <SQL_QUERY_TIMEOUT>
> SQLPOINTER 0x0000003C
> IOSDSQL 664-964 EXIT SQLSetStmtOption with return code 0
> (SQL_SUCCESS)
> HSTMT 0A0B1EC8
> UWORD 0 <SQL_QUERY_TIMEOUT>
> SQLPOINTER 0x0000003C (BADMEM)
> IOSDSQL 664-964 ENTER SQLExecDirect
> HSTMT 0A0B1EC8
> UCHAR * 0x09FB18C0 [ -3] "SELECT
> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int:No" FROM
> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
> SDWORD -3
> IOSDSQL 664-964 EXIT SQLExecDirect with return code -1
> (SQL_ERROR)
> HSTMT 0A0B1EC8
> UCHAR * 0x09FB18C0 [ -3] "SELECT
> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int:No" FROM
> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
> SDWORD -3
> DIAG [37000] [Microsoft][ODBC SQL Server Driver][SQL Serv
er]Line 1:
> Incorrect syntax near '.'. (170)
>Check to make sure QUOTED_IDENTIFIER is ON.
Hope this helps.
Dan Guzman
SQL Server MVP
"BrianMultilLanguage" <brian@.clilang.com> wrote in message
news:12kv1p37855g42@.corp.supernews.com...
> Only one user has the problem.
> I have given them a new copy of the switchboard but same startup error.
> Thank you for your help.
>
>|||BINGO~!
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:59C18CE9-04B5-49E1-87AB-4EA2DAD4E977@.microsoft.com...
> Check to make sure QUOTED_IDENTIFIER is ON.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "BrianMultilLanguage" <brian@.clilang.com> wrote in message
> news:12kv1p37855g42@.corp.supernews.com...
>
I have given them a new copy of the switchboard but same startup error.
Thank you for your help.
> IOSDSQL 664-964 ENTER SQLSetStmtOption
> HSTMT 0A0B1EC8
> UWORD 0 <SQL_QUERY_TIMEOUT>
> SQLPOINTER 0x0000003C
> IOSDSQL 664-964 EXIT SQLSetStmtOption with return code 0
> (SQL_SUCCESS)
> HSTMT 0A0B1EC8
> UWORD 0 <SQL_QUERY_TIMEOUT>
> SQLPOINTER 0x0000003C (BADMEM)
> IOSDSQL 664-964 ENTER SQLExecDirect
> HSTMT 0A0B1EC8
> UCHAR * 0x09FB18C0 [ -3] "SELECT
> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int:No" FROM
> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
> SDWORD -3
> IOSDSQL 664-964 EXIT SQLExecDirect with return code -1
> (SQL_ERROR)
> HSTMT 0A0B1EC8
> UCHAR * 0x09FB18C0 [ -3] "SELECT
> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int:No" FROM
> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
> SDWORD -3
> DIAG [37000] [Microsoft][ODBC SQL Server Driver][SQL Serv
er]Line 1:
> Incorrect syntax near '.'. (170)
>Check to make sure QUOTED_IDENTIFIER is ON.
Hope this helps.
Dan Guzman
SQL Server MVP
"BrianMultilLanguage" <brian@.clilang.com> wrote in message
news:12kv1p37855g42@.corp.supernews.com...
> Only one user has the problem.
> I have given them a new copy of the switchboard but same startup error.
> Thank you for your help.
>
>|||BINGO~!
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:59C18CE9-04B5-49E1-87AB-4EA2DAD4E977@.microsoft.com...
> Check to make sure QUOTED_IDENTIFIER is ON.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "BrianMultilLanguage" <brian@.clilang.com> wrote in message
> news:12kv1p37855g42@.corp.supernews.com...
>
Friday, February 24, 2012
Error 3: the system cannot find the specified path
Installed SQL Server 2000 Enterprise trial a week ago on XP Pro. Installed new Seagate 80G HD; used Seagate's utility to copy old C: to new drive as new boot drive. All seems to work fine, except, when booting up, SQL server doesn't start. When I try to start it manually I get the following:
Could not start SQLSERVER service on the local computer. Error 3: the system cannot find the specified path.
1. What could be wrong?
2. How do I fix it?
If you are starting via the service, look at services.msc and see what path is pointed to for sqlservr.exe. Check if the file exists at this location. Is this error coming from SQL Server or the OS?
|||I saw nothing in services.msc relating to sql. In fact, the file is dated 8/4/2004. I didn't install SQL until about a week ago. [[NOTE, FYI: I also posted this question in the 'SQL Server Data Access' forum, but no solution there yet, either]]. If I try to manually start SQL Server, the first message just states it's unable to find the path specified. When I click OK, the next message title bar reads 'SQL Server Service Manager', and the message reads, "An error 3 - (The system cannot find the path specified.
) occured while performing this service operation on the MSSQLServer service."
If you're referring to the properties in Services, MSSQLServer, properties, the path is "C:\PROGRA~1\MICROS~4\MSSQL\binn\sqlservr.exe"
If I navigate to C:\Program Files\Microsoft SQL Server\MSSQL\Binn, I can double-click sqlservr.exe and a dos window opens up, etc., but it doesn' t seem to do anything related to the icon in my status bar, which still shows not started. If I enter the ..~ path above into the command prompt, I get the same "The system cannot find the path specified". Looks like I need to change the path to mssql server, but how do I do that?
|||Services.msc is the MMC Services extension. It is an dll that will be loaded and run by MMC.
Change to that path in a cmd.exe window, and run sqlservr.exe -c. It should log to the console and ERRORLOG the error message. You can also try to track the file is searching for with filemon (www.sysinternals.com tool).
|||SQLServer need somewehree a starting point, there for the path to the master mdf is coded in the registry with the appropiate start parameter. The service gathers this information at start up to find the "valid mointing point" for the master database. The key normally is located on the node
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer\Parameters
Changing this is sort of critical, so you better save your registry key first to restore it, if something unexpectly happens.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
Actually, I found that yesterday; changed two path settings in the registry, and that fixed it. Apparently, when I duplicated the hard drive, it somehow used the DOS ~ naming conventions. Once I changed back to the named path, all seemed to work fine. Thanks to all who replied to my question.|||I just ran into the same problem after I migrate (duplicate) the server to another server. I checked the properties under service of mssqlserver and it displayed the shortname. I went into the registry and made modification to a few places under HKLM\system\currentcontrolset....\service\mssqlserver and changed the imagepath parameter to point to the proper long name E:\progam files\microsoft sql server\mssql\binn\sqlsrver.exe. Then I was able to start SQL Server. The properties of SQLserver agent is using the long name so it does not have a problem.
I don't understand why it did not work. I checked the old server and it was using the short name and it worked. I checked some other SQL servers and they all displayed the short name and they have no problem. I thought the system should be able to recognize the short name automatically.
It seems that this problem is only happening on this server.
Any idea?
Thanks.
Error 3: the system cannot find the specified path
Installed SQL Server 2000 Enterprise trial a week ago on XP Pro. Installed new Seagate 80G HD; used Seagate's utility to copy old C: to new drive as new boot drive. All seems to work fine, except, when booting up, SQL server doesn't start. When I try to start it manually I get the following:
Could not start SQLSERVER service on the local computer. Error 3: the system cannot find the specified path.
1. What could be wrong?
2. How do I fix it?
If you are starting via the service, look at services.msc and see what path is pointed to for sqlservr.exe. Check if the file exists at this location. Is this error coming from SQL Server or the OS?
|||I saw nothing in services.msc relating to sql. In fact, the file is dated 8/4/2004. I didn't install SQL until about a week ago. [[NOTE, FYI: I also posted this question in the 'SQL Server Data Access' forum, but no solution there yet, either]]. If I try to manually start SQL Server, the first message just states it's unable to find the path specified. When I click OK, the next message title bar reads 'SQL Server Service Manager', and the message reads, "An error 3 - (The system cannot find the path specified.
) occured while performing this service operation on the MSSQLServer service."
If you're referring to the properties in Services, MSSQLServer, properties, the path is "C:\PROGRA~1\MICROS~4\MSSQL\binn\sqlservr.exe"
If I navigate to C:\Program Files\Microsoft SQL Server\MSSQL\Binn, I can double-click sqlservr.exe and a dos window opens up, etc., but it doesn' t seem to do anything related to the icon in my status bar, which still shows not started. If I enter the ..~ path above into the command prompt, I get the same "The system cannot find the path specified". Looks like I need to change the path to mssql server, but how do I do that?
|||Services.msc is the MMC Services extension. It is an dll that will be loaded and run by MMC.
Change to that path in a cmd.exe window, and run sqlservr.exe -c. It should log to the console and ERRORLOG the error message. You can also try to track the file is searching for with filemon (www.sysinternals.com tool).
|||SQLServer need somewehree a starting point, there for the path to the master mdf is coded in the registry with the appropiate start parameter. The service gathers this information at start up to find the "valid mointing point" for the master database. The key normally is located on the node
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer\Parameters
Changing this is sort of critical, so you better save your registry key first to restore it, if something unexpectly happens.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
Actually, I found that yesterday; changed two path settings in the registry, and that fixed it. Apparently, when I duplicated the hard drive, it somehow used the DOS ~ naming conventions. Once I changed back to the named path, all seemed to work fine. Thanks to all who replied to my question.|||I just ran into the same problem after I migrate (duplicate) the server to another server. I checked the properties under service of mssqlserver and it displayed the shortname. I went into the registry and made modification to a few places under HKLM\system\currentcontrolset....\service\mssqlserver and changed the imagepath parameter to point to the proper long name E:\progam files\microsoft sql server\mssql\binn\sqlsrver.exe. Then I was able to start SQL Server. The properties of SQLserver agent is using the long name so it does not have a problem.
I don't understand why it did not work. I checked the old server and it was using the short name and it worked. I checked some other SQL servers and they all displayed the short name and they have no problem. I thought the system should be able to recognize the short name automatically.
It seems that this problem is only happening on this server.
Any idea?
Thanks.
Subscribe to:
Posts (Atom)