problem with attaching mdf file

Bob wrote:
> Hi,
> i installed sql server 2005 express on a windows xp prof. sp2 system.
> i also installed the 2005 studio management tool.
> I can connect to the sql server (sqlcmd -S), i can create a new database in
> the 2005 studio management tool, but i can't attach a mdf file. I'm
> administrator so have all rights. I have several mdf (and ldf) files on the
> disc.
> I did this:
> rightclick on Databases, then Attach: i see right an empty windows with an
> ADD button.
> When i click on that button, i get the error:
> c:\myapp\app_data\
> cannot access the specified path or file. Verify that you have the necessary
> privileges ...
> If you know that the service account a specific file, type the path ...
> The sevice account is NT AUTHORITY\NetworkService, but when i see the list
> of the accounts, i can't find it into that list.
>
> Any help would be appreciated.
> Thanks
> Bob
>
>
>
>
Create an actual user to be used as the service account, then make sure
that user has read/write permissions in your data directory.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
Bob wrote:
> Thanks for replying.
> Can you tell me how to do that? Do you mean: a windows xp account? And how
> to link it to NT AUTHORITY\Network? I can't even find it in the list of the
> windows accounts.
>
Yes, a Windows XP account or a domain account, whichever is appropriate
for your environment. You don't "link" this new user to NT
AUTHORITY\Network, you'll configure the SQL Server services to run as
the new user that you create. NT AUTHORITY\Network isn't a real user
account.
You could also configure the SQL Server services to run as "Local
System", which will give SQL system-level access to your machine.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

problem with attaching mdf file

Bob wrote:
> Hi,
> i installed sql server 2005 express on a windows xp prof. sp2 system.
> i also installed the 2005 studio management tool.
> I can connect to the sql server (sqlcmd -S), i can create a new database in
> the 2005 studio management tool, but i can't attach a mdf file. I'm
> administrator so have all rights. I have several mdf (and ldf) files on the
> disc.
> I did this:
> rightclick on Databases, then Attach: i see right an empty windows with an
> ADD button.
> When i click on that button, i get the error:
> c:\myapp\app_data\
> cannot access the specified path or file. Verify that you have the necessary
> privileges ...
> If you know that the service account a specific file, type the path ...
> The sevice account is NT AUTHORITY\NetworkService, but when i see the list
> of the accounts, i can't find it into that list.
>
> Any help would be appreciated.
> Thanks
> Bob
>
>
>
>
Create an actual user to be used as the service account, then make sure
that user has read/write permissions in your data directory.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
Bob wrote:
> Thanks for replying.
> Can you tell me how to do that? Do you mean: a windows xp account? And how
> to link it to NT AUTHORITY\Network? I can't even find it in the list of the
> windows accounts.
>
Yes, a Windows XP account or a domain account, whichever is appropriate
for your environment. You don't "link" this new user to NT
AUTHORITY\Network, you'll configure the SQL Server services to run as
the new user that you create. NT AUTHORITY\Network isn't a real user
account.
You could also configure the SQL Server services to run as "Local
System", which will give SQL system-level access to your machine.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
sql

problem with attaching mdf file

Hi,
i installed sql server 2005 express on a windows xp prof. sp2 system.
i also installed the 2005 studio management tool.
I can connect to the sql server (sqlcmd -S), i can create a new database in
the 2005 studio management tool, but i can't attach a mdf file. I'm
administrator so have all rights. I have several mdf (and ldf) files on the
disc.
I did this:
rightclick on Databases, then Attach: i see right an empty windows with an
ADD button.
When i click on that button, i get the error:
c:\myapp\app_data\
cannot access the specified path or file. Verify that you have the necessary
privileges ...
If you know that the service account a specific file, type the path ...
The sevice account is NT AUTHORITY\NetworkService, but when i see the list
of the accounts, i can't find it into that list.
Any help would be appreciated.
Thanks
BobBob wrote:
> Hi,
> i installed sql server 2005 express on a windows xp prof. sp2 system.
> i also installed the 2005 studio management tool.
> I can connect to the sql server (sqlcmd -S), i can create a new database in
> the 2005 studio management tool, but i can't attach a mdf file. I'm
> administrator so have all rights. I have several mdf (and ldf) files on the
> disc.
> I did this:
> rightclick on Databases, then Attach: i see right an empty windows with an
> ADD button.
> When i click on that button, i get the error:
> c:\myapp\app_data\
> cannot access the specified path or file. Verify that you have the necessary
> privileges ...
> If you know that the service account a specific file, type the path ...
> The sevice account is NT AUTHORITY\NetworkService, but when i see the list
> of the accounts, i can't find it into that list.
>
> Any help would be appreciated.
> Thanks
> Bob
>
>
>
>
Create an actual user to be used as the service account, then make sure
that user has read/write permissions in your data directory.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Thanks for replying.
Can you tell me how to do that? Do you mean: a windows xp account? And how
to link it to NT AUTHORITY\Network? I can't even find it in the list of the
windows accounts.
"Tracy McKibben" <tracy@.realsqlguy.com> schreef in bericht
news:459BF31D.9050605@.realsqlguy.com...
> Bob wrote:
>> Hi,
>> i installed sql server 2005 express on a windows xp prof. sp2 system.
>> i also installed the 2005 studio management tool.
>> I can connect to the sql server (sqlcmd -S), i can create a new database
>> in the 2005 studio management tool, but i can't attach a mdf file. I'm
>> administrator so have all rights. I have several mdf (and ldf) files on
>> the disc.
>> I did this:
>> rightclick on Databases, then Attach: i see right an empty windows with
>> an ADD button.
>> When i click on that button, i get the error:
>> c:\myapp\app_data\
>> cannot access the specified path or file. Verify that you have the
>> necessary privileges ...
>> If you know that the service account a specific file, type the path ...
>> The sevice account is NT AUTHORITY\NetworkService, but when i see the
>> list of the accounts, i can't find it into that list.
>>
>> Any help would be appreciated.
>> Thanks
>> Bob
>>
>>
>>
> Create an actual user to be used as the service account, then make sure
> that user has read/write permissions in your data directory.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Thanks for replying.
I copied mydb.mdf and .ldf to the directory where i created a new database,
but in Management Studio, it's the same: i don't see it in the list of the
databases and can't attach it.
"Hari Prasad" <HariPrasad@.discussions.microsoft.com> schreef in bericht
news:7601E1FD-2A85-496E-A92F-06189BC57855@.microsoft.com...
> Easy way is copy the required MDF and LDF files to the default data
> directory
> (The place where you create the new database)
> using the windows explorer and then try attaching the database. This will
> defenetely work out.
> The issue is you have full access to machine but once you login to SQL
> Server you will have access rights only belong to
> account "NT AUTHORITY\NetworkService". The account may not have access to
> folder c:\myapp\app_data\.
> My best suggestion is copy the file to the folder where the new database
> is
> created and attach it.
> Thanks
> Hari
> "Bob" wrote:
>> Hi,
>> i installed sql server 2005 express on a windows xp prof. sp2 system.
>> i also installed the 2005 studio management tool.
>> I can connect to the sql server (sqlcmd -S), i can create a new database
>> in
>> the 2005 studio management tool, but i can't attach a mdf file. I'm
>> administrator so have all rights. I have several mdf (and ldf) files on
>> the
>> disc.
>> I did this:
>> rightclick on Databases, then Attach: i see right an empty windows with
>> an
>> ADD button.
>> When i click on that button, i get the error:
>> c:\myapp\app_data\
>> cannot access the specified path or file. Verify that you have the
>> necessary
>> privileges ...
>> If you know that the service account a specific file, type the path ...
>> The sevice account is NT AUTHORITY\NetworkService, but when i see the
>> list
>> of the accounts, i can't find it into that list.
>>
>> Any help would be appreciated.
>> Thanks
>> Bob
>>
>>
>>
>>|||Bob wrote:
> Thanks for replying.
> Can you tell me how to do that? Do you mean: a windows xp account? And how
> to link it to NT AUTHORITY\Network? I can't even find it in the list of the
> windows accounts.
>
Yes, a Windows XP account or a domain account, whichever is appropriate
for your environment. You don't "link" this new user to NT
AUTHORITY\Network, you'll configure the SQL Server services to run as
the new user that you create. NT AUTHORITY\Network isn't a real user
account.
You could also configure the SQL Server services to run as "Local
System", which will give SQL system-level access to your machine.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Thanks it works now
"Tracy McKibben" <tracy@.realsqlguy.com> schreef in bericht
news:459C069B.5080403@.realsqlguy.com...
> Bob wrote:
>> Thanks for replying.
>> Can you tell me how to do that? Do you mean: a windows xp account? And
>> how to link it to NT AUTHORITY\Network? I can't even find it in the list
>> of the windows accounts.
> Yes, a Windows XP account or a domain account, whichever is appropriate
> for your environment. You don't "link" this new user to NT
> AUTHORITY\Network, you'll configure the SQL Server services to run as the
> new user that you create. NT AUTHORITY\Network isn't a real user account.
> You could also configure the SQL Server services to run as "Local System",
> which will give SQL system-level access to your machine.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com

problem with attaching mdf file

Hi,
i installed sql server 2005 express on a Windows XP prof. sp2 system.
i also installed the 2005 studio management tool.
I can connect to the sql server (sqlcmd -S), i can create a new database in
the 2005 studio management tool, but i can't attach a mdf file. I'm
administrator so have all rights. I have several mdf (and ldf) files on the
disc.
I did this:
rightclick on Databases, then Attach: i see right an empty windows with an
ADD button.
When i click on that button, i get the error:
c:\myapp\app_data\
cannot access the specified path or file. Verify that you have the necessary
privileges ...
If you know that the service account a specific file, type the path ...
The sevice account is NT AUTHORITY\NetworkService, but when i see the list
of the accounts, i can't find it into that list.
Any help would be appreciated.
Thanks
BobBob wrote:
> Hi,
> i installed sql server 2005 express on a Windows XP prof. sp2 system.
> i also installed the 2005 studio management tool.
> I can connect to the sql server (sqlcmd -S), i can create a new database i
n
> the 2005 studio management tool, but i can't attach a mdf file. I'm
> administrator so have all rights. I have several mdf (and ldf) files on th
e
> disc.
> I did this:
> rightclick on Databases, then Attach: i see right an empty windows with an
> ADD button.
> When i click on that button, i get the error:
> c:\myapp\app_data\
> cannot access the specified path or file. Verify that you have the necessa
ry
> privileges ...
> If you know that the service account a specific file, type the path ...
> The sevice account is NT AUTHORITY\NetworkService, but when i see the list
> of the accounts, i can't find it into that list.
>
> Any help would be appreciated.
> Thanks
> Bob
>
>
>
>
Create an actual user to be used as the service account, then make sure
that user has read/write permissions in your data directory.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Easy way is copy the required MDF and LDF files to the default data director
y
(The place where you create the new database)
using the windows explorer and then try attaching the database. This will
defenetely work out.
The issue is you have full access to machine but once you login to SQL
Server you will have access rights only belong to
account "NT AUTHORITY\NetworkService". The account may not have access to
folder c:\myapp\app_data\.
My best suggestion is copy the file to the folder where the new database is
created and attach it.
Thanks
Hari
"Bob" wrote:

> Hi,
> i installed sql server 2005 express on a Windows XP prof. sp2 system.
> i also installed the 2005 studio management tool.
> I can connect to the sql server (sqlcmd -S), i can create a new database i
n
> the 2005 studio management tool, but i can't attach a mdf file. I'm
> administrator so have all rights. I have several mdf (and ldf) files on th
e
> disc.
> I did this:
> rightclick on Databases, then Attach: i see right an empty windows with an
> ADD button.
> When i click on that button, i get the error:
> c:\myapp\app_data\
> cannot access the specified path or file. Verify that you have the necessa
ry
> privileges ...
> If you know that the service account a specific file, type the path ...
> The sevice account is NT AUTHORITY\NetworkService, but when i see the list
> of the accounts, i can't find it into that list.
>
> Any help would be appreciated.
> Thanks
> Bob
>
>
>
>|||Thanks for replying.
Can you tell me how to do that? Do you mean: a Windows XP account? And how
to link it to NT AUTHORITY\Network? I can't even find it in the list of the
windows accounts.
"Tracy McKibben" <tracy@.realsqlguy.com> schreef in bericht
news:459BF31D.9050605@.realsqlguy.com...
> Bob wrote:
> Create an actual user to be used as the service account, then make sure
> that user has read/write permissions in your data directory.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Thanks for replying.
I copied mydb.mdf and .ldf to the directory where i created a new database,
but in Management Studio, it's the same: i don't see it in the list of the
databases and can't attach it.
"Hari Prasad" <HariPrasad@.discussions.microsoft.com> schreef in bericht
news:7601E1FD-2A85-496E-A92F-06189BC57855@.microsoft.com...[vbcol=seagreen]
> Easy way is copy the required MDF and LDF files to the default data
> directory
> (The place where you create the new database)
> using the windows explorer and then try attaching the database. This will
> defenetely work out.
> The issue is you have full access to machine but once you login to SQL
> Server you will have access rights only belong to
> account "NT AUTHORITY\NetworkService". The account may not have access to
> folder c:\myapp\app_data\.
> My best suggestion is copy the file to the folder where the new database
> is
> created and attach it.
> Thanks
> Hari
> "Bob" wrote:
>|||Bob wrote:
> Thanks for replying.
> Can you tell me how to do that? Do you mean: a Windows XP account? And how
> to link it to NT AUTHORITY\Network? I can't even find it in the list of th
e
> windows accounts.
>
Yes, a Windows XP account or a domain account, whichever is appropriate
for your environment. You don't "link" this new user to NT
AUTHORITY\Network, you'll configure the SQL Server services to run as
the new user that you create. NT AUTHORITY\Network isn't a real user
account.
You could also configure the SQL Server services to run as "Local
System", which will give SQL system-level access to your machine.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Thanks it works now
"Tracy McKibben" <tracy@.realsqlguy.com> schreef in bericht
news:459C069B.5080403@.realsqlguy.com...
> Bob wrote:
> Yes, a Windows XP account or a domain account, whichever is appropriate
> for your environment. You don't "link" this new user to NT
> AUTHORITY\Network, you'll configure the SQL Server services to run as the
> new user that you create. NT AUTHORITY\Network isn't a real user account.
> You could also configure the SQL Server services to run as "Local System",
> which will give SQL system-level access to your machine.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com

problem with ##xp_cmdshell_proxy_account##

Hi,
I was trying to debug a situation where we need to use xp_cmdshell in
SQL2005 SP2 build 3175. I had created the ##xp_cmdshell_proxy_account##
proxy credential and wanted to delete it to see that I was getting a message
about the credential missing. After running the sp_xp_cmdshell_proxy_account
stored proc with NULL I ran it again to re-create the proxy credential but
this time I got message: -
Msg 15137, Level 16, State 1, Procedure sp_xp_cmdshell_proxy_account, Line 1
An error occurred during the execution of sp_xp_cmdshell_proxy_account.
Possible reasons: the provided account was invalid or the
'##xp_cmdshell_proxy_account##' credential could not be created. Error code:
'997'.
This is on a clustered server so do I need to flip the cluster for the
credential to be completed deleted before trying to add it again?
Thanks
ChrisI am having the same issue. I am simply trying to assign xp_cmdshell a proxy
account and its not allowing me to. I know that the username/password is a
valid one.
Any help would be appreciated. Thanks Amir
"Chris Wood" wrote:
> Hi,
> I was trying to debug a situation where we need to use xp_cmdshell in
> SQL2005 SP2 build 3175. I had created the ##xp_cmdshell_proxy_account##
> proxy credential and wanted to delete it to see that I was getting a message
> about the credential missing. After running the sp_xp_cmdshell_proxy_account
> stored proc with NULL I ran it again to re-create the proxy credential but
> this time I got message: -
> Msg 15137, Level 16, State 1, Procedure sp_xp_cmdshell_proxy_account, Line 1
> An error occurred during the execution of sp_xp_cmdshell_proxy_account.
> Possible reasons: the provided account was invalid or the
> '##xp_cmdshell_proxy_account##' credential could not be created. Error code:
> '997'.
> This is on a clustered server so do I need to flip the cluster for the
> credential to be completed deleted before trying to add it again?
> Thanks
> Chris
>
>
>
>|||Amir,
Rather than run the stored proc I just created the proxy credential by using
the create credential T-SQL statement.
Chris
"Amir" <Amir@.discussions.microsoft.com> wrote in message
news:61B89673-4894-419A-9D82-6D99C7559878@.microsoft.com...
>I am having the same issue. I am simply trying to assign xp_cmdshell a
>proxy
> account and its not allowing me to. I know that the username/password is a
> valid one.
> Any help would be appreciated. Thanks Amir
> "Chris Wood" wrote:
>> Hi,
>> I was trying to debug a situation where we need to use xp_cmdshell in
>> SQL2005 SP2 build 3175. I had created the ##xp_cmdshell_proxy_account##
>> proxy credential and wanted to delete it to see that I was getting a
>> message
>> about the credential missing. After running the
>> sp_xp_cmdshell_proxy_account
>> stored proc with NULL I ran it again to re-create the proxy credential
>> but
>> this time I got message: -
>> Msg 15137, Level 16, State 1, Procedure sp_xp_cmdshell_proxy_account,
>> Line 1
>> An error occurred during the execution of sp_xp_cmdshell_proxy_account.
>> Possible reasons: the provided account was invalid or the
>> '##xp_cmdshell_proxy_account##' credential could not be created. Error
>> code:
>> '997'.
>> This is on a clustered server so do I need to flip the cluster for the
>> credential to be completed deleted before trying to add it again?
>> Thanks
>> Chris
>>
>>
>>

Problem using SQL Debugger

Hello. I have only used the Debugger a few times, mostly from within VB. At a
client site, we had used the Debugger from an XP SP2 machine to a
WindowsServer 2000 machine with SQL Server 2000 (unknown service pack level)
without problem. It had not been used for several months, during which time
the server was replaced with a Windows 2003 Server, SQL Server 2000 (SP2+,
but unsure of actual SP level).
The problems? We can't install the VB software on the server to enable the
debugger. So we thought we'd just use the Query Analyzer debugger instead.
But when we try to run it, we get the error: "The debugger interface is not
installed. Please re-run setup and select 'add components to your existing
installation' ..". We did rerun setup (on both the client and server) but
when we ran it on the client it already clearly had the debugger interface
option installed. Verifying files on the server I found that I could not
register the file 'mssdi98.dll', it would error "the file was loaded but the
entry point was not found'". This file was then re-copied from the SQL Server
CD and tried again, same error.
Is there some known issue using the debugger when SQL Server is on a Windows
Server 2003 machine? This stored procedure is particularly nasty and we have
no chance of debugging it without this interface. Please advise.
Thank you,
Brad Ashforth
Hello Brad,
mssdi98.dll is not a Activex control dll. Therefore, you could not regsiter
it by using regsvr32.
This issue can occur if SQLDebugger account does not have the porper
rights. Normally SQLDebugger has "Log on as a batch job" and "Deny logon
locally" user rights. Please run gpedit.msc and go to Computer
Configuration->Windows Settings->Security Settings->Local Policie->User
rights assignments to check if SQLDebugger account has the proper rights.
See: 818374 INF: SQL Server 2000 SP3 Creates a SQLDebugger Windows User
Account
http://support.microsoft.com/?id=818374
Also, the following article shall be a good reference
280101 INF: Transact-SQL Debugger Limitations and Troubleshooting Tips for
SQL
http://support.microsoft.com/?id=280101
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
| Thread-Topic: Problem using SQL Debugger
| thread-index: AcVhOfWOQfF7UKMrR42/aEn39rd3uA==
| X-WBNR-Posting-Host: 71.113.19.127
| From: "=?Utf-8?B?QnJhZCBBc2hmb3J0aA==?=" <banospam@.nospam.nospam>
| Subject: Problem using SQL Debugger
| Date: Wed, 25 May 2005 07:56:41 -0700
| Lines: 25
| Message-ID: <5A3081B3-D52B-46B6-A2BF-E53C9BF35403@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.tools
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA02.phx.gbl!TK2MSF TNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.tools:4469
| X-Tomcat-NG: microsoft.public.sqlserver.tools
|
| Hello. I have only used the Debugger a few times, mostly from within VB.
At a
| client site, we had used the Debugger from an XP SP2 machine to a
| WindowsServer 2000 machine with SQL Server 2000 (unknown service pack
level)
| without problem. It had not been used for several months, during which
time
| the server was replaced with a Windows 2003 Server, SQL Server 2000
(SP2+,
| but unsure of actual SP level).
|
| The problems? We can't install the VB software on the server to enable
the
| debugger. So we thought we'd just use the Query Analyzer debugger
instead.
| But when we try to run it, we get the error: "The debugger interface is
not
| installed. Please re-run setup and select 'add components to your
existing
| installation' ..". We did rerun setup (on both the client and server) but
| when we ran it on the client it already clearly had the debugger
interface
| option installed. Verifying files on the server I found that I could not
| register the file 'mssdi98.dll', it would error "the file was loaded but
the
| entry point was not found'". This file was then re-copied from the SQL
Server
| CD and tried again, same error.
|
| Is there some known issue using the debugger when SQL Server is on a
Windows
| Server 2003 machine? This stored procedure is particularly nasty and we
have
| no chance of debugging it without this interface. Please advise.
|
| Thank you,
|
| Brad Ashforth
|
|||Hi Peter. Thank you for your reply. I checked the machine in question and I
do not see a "SQLDebugger" account. Would this account have been created
automatically during the install? Or do I need to create it manually? I will
review the article you mention but am surprised to find this so difficult to
set up. Perhaps this will be easier in SQL2005?
Brad Ashforth
"Peter Yang [MSFT]" wrote:

> Hello Brad,
> mssdi98.dll is not a Activex control dll. Therefore, you could not regsiter
> it by using regsvr32.
> This issue can occur if SQLDebugger account does not have the porper
> rights. Normally SQLDebugger has "Log on as a batch job" and "Deny logon
> locally" user rights. Please run gpedit.msc and go to Computer
> Configuration->Windows Settings->Security Settings->Local Policie->User
> rights assignments to check if SQLDebugger account has the proper rights.
> See: 818374 INF: SQL Server 2000 SP3 Creates a SQLDebugger Windows User
> Account
> http://support.microsoft.com/?id=818374
> Also, the following article shall be a good reference
> 280101 INF: Transact-SQL Debugger Limitations and Troubleshooting Tips for
> SQL
> http://support.microsoft.com/?id=280101
> Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> --
> | Thread-Topic: Problem using SQL Debugger
> | thread-index: AcVhOfWOQfF7UKMrR42/aEn39rd3uA==
> | X-WBNR-Posting-Host: 71.113.19.127
> | From: "=?Utf-8?B?QnJhZCBBc2hmb3J0aA==?=" <banospam@.nospam.nospam>
> | Subject: Problem using SQL Debugger
> | Date: Wed, 25 May 2005 07:56:41 -0700
> | Lines: 25
> | Message-ID: <5A3081B3-D52B-46B6-A2BF-E53C9BF35403@.microsoft.com>
> | MIME-Version: 1.0
> | Content-Type: text/plain;
> | charset="Utf-8"
> | Content-Transfer-Encoding: 7bit
> | X-Newsreader: Microsoft CDO for Windows 2000
> | Content-Class: urn:content-classes:message
> | Importance: normal
> | Priority: normal
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> | Newsgroups: microsoft.public.sqlserver.tools
> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA02.phx.gbl!TK2MSF TNGXA03.phx.gbl
> | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.tools:4469
> | X-Tomcat-NG: microsoft.public.sqlserver.tools
> |
> | Hello. I have only used the Debugger a few times, mostly from within VB.
> At a
> | client site, we had used the Debugger from an XP SP2 machine to a
> | WindowsServer 2000 machine with SQL Server 2000 (unknown service pack
> level)
> | without problem. It had not been used for several months, during which
> time
> | the server was replaced with a Windows 2003 Server, SQL Server 2000
> (SP2+,
> | but unsure of actual SP level).
> |
> | The problems? We can't install the VB software on the server to enable
> the
> | debugger. So we thought we'd just use the Query Analyzer debugger
> instead.
> | But when we try to run it, we get the error: "The debugger interface is
> not
> | installed. Please re-run setup and select 'add components to your
> existing
> | installation' ..". We did rerun setup (on both the client and server) but
> | when we ran it on the client it already clearly had the debugger
> interface
> | option installed. Verifying files on the server I found that I could not
> | register the file 'mssdi98.dll', it would error "the file was loaded but
> the
> | entry point was not found'". This file was then re-copied from the SQL
> Server
> | CD and tried again, same error.
> |
> | Is there some known issue using the debugger when SQL Server is on a
> Windows
> | Server 2003 machine? This stored procedure is particularly nasty and we
> have
> | no chance of debugging it without this interface. Please advise.
> |
> | Thank you,
> |
> | Brad Ashforth
> |
>
|||Hello Brad,
The account shall be created automatically. You may want to install SP4 to
see if it fixes this problem
How to obtain the latest SQL Server 2000 service pack
http://support.microsoft.com/?kbid=290211
SQL Server 2000 Service Pack 4
http://www.microsoft.com/sql/downloads/2000/sp4.asp
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
| Thread-Topic: Problem using SQL Debugger
| thread-index: AcVmqY2l2xUiQ0dvSSeg0vsuxcXaRA==
| X-WBNR-Posting-Host: 71.113.19.127
| From: "=?Utf-8?B?QnJhZCBBc2hmb3J0aA==?=" <banospam@.nospam.nospam>
| References: <5A3081B3-D52B-46B6-A2BF-E53C9BF35403@.microsoft.com>
<eW4WbbbYFHA.2184@.TK2MSFTNGXA01.phx.gbl>
| Subject: RE: Problem using SQL Debugger
| Date: Wed, 1 Jun 2005 05:58:06 -0700
| Lines: 114
| Message-ID: <6FC66EE3-C581-4503-95A9-B1A467D93F32@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.tools
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.tools:4517
| X-Tomcat-NG: microsoft.public.sqlserver.tools
|
| Hi Peter. Thank you for your reply. I checked the machine in question and
I
| do not see a "SQLDebugger" account. Would this account have been created
| automatically during the install? Or do I need to create it manually? I
will
| review the article you mention but am surprised to find this so difficult
to
| set up. Perhaps this will be easier in SQL2005?
| --
| Brad Ashforth
|
|
| "Peter Yang [MSFT]" wrote:
|
| > Hello Brad,
| >
| > mssdi98.dll is not a Activex control dll. Therefore, you could not
regsiter
| > it by using regsvr32.
| >
| > This issue can occur if SQLDebugger account does not have the porper
| > rights. Normally SQLDebugger has "Log on as a batch job" and "Deny
logon
| > locally" user rights. Please run gpedit.msc and go to Computer
| > Configuration->Windows Settings->Security Settings->Local Policie->User
| > rights assignments to check if SQLDebugger account has the proper
rights.
| >
| > See: 818374 INF: SQL Server 2000 SP3 Creates a SQLDebugger Windows User
| > Account
| > http://support.microsoft.com/?id=818374
| >
| > Also, the following article shall be a good reference
| >
| > 280101 INF: Transact-SQL Debugger Limitations and Troubleshooting Tips
for
| > SQL
| > http://support.microsoft.com/?id=280101
| >
| > Regards,
| >
| > Peter Yang
| > MCSE2000/2003, MCSA, MCDBA
| > Microsoft Online Partner Support
| >
| > When responding to posts, please "Reply to Group" via your newsreader
so
| > that others may learn and benefit from your issue.
| >
| > ================================================== ===
| >
| >
| > This posting is provided "AS IS" with no warranties, and confers no
rights.
| >
| >
| >
| >
| > --
| > | Thread-Topic: Problem using SQL Debugger
| > | thread-index: AcVhOfWOQfF7UKMrR42/aEn39rd3uA==
| > | X-WBNR-Posting-Host: 71.113.19.127
| > | From: "=?Utf-8?B?QnJhZCBBc2hmb3J0aA==?=" <banospam@.nospam.nospam>
| > | Subject: Problem using SQL Debugger
| > | Date: Wed, 25 May 2005 07:56:41 -0700
| > | Lines: 25
| > | Message-ID: <5A3081B3-D52B-46B6-A2BF-E53C9BF35403@.microsoft.com>
| > | MIME-Version: 1.0
| > | Content-Type: text/plain;
| > | charset="Utf-8"
| > | Content-Transfer-Encoding: 7bit
| > | X-Newsreader: Microsoft CDO for Windows 2000
| > | Content-Class: urn:content-classes:message
| > | Importance: normal
| > | Priority: normal
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| > | Newsgroups: microsoft.public.sqlserver.tools
| > | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| > | Path:
TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA02.phx.gbl!TK2MSF TNGXA03.phx.gbl
| > | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.tools:4469
| > | X-Tomcat-NG: microsoft.public.sqlserver.tools
| > |
| > | Hello. I have only used the Debugger a few times, mostly from within
VB.
| > At a
| > | client site, we had used the Debugger from an XP SP2 machine to a
| > | WindowsServer 2000 machine with SQL Server 2000 (unknown service pack
| > level)
| > | without problem. It had not been used for several months, during
which
| > time
| > | the server was replaced with a Windows 2003 Server, SQL Server 2000
| > (SP2+,
| > | but unsure of actual SP level).
| > |
| > | The problems? We can't install the VB software on the server to
enable
| > the
| > | debugger. So we thought we'd just use the Query Analyzer debugger
| > instead.
| > | But when we try to run it, we get the error: "The debugger interface
is
| > not
| > | installed. Please re-run setup and select 'add components to your
| > existing
| > | installation' ..". We did rerun setup (on both the client and server)
but
| > | when we ran it on the client it already clearly had the debugger
| > interface
| > | option installed. Verifying files on the server I found that I could
not
| > | register the file 'mssdi98.dll', it would error "the file was loaded
but
| > the
| > | entry point was not found'". This file was then re-copied from the
SQL
| > Server
| > | CD and tried again, same error.
| > |
| > | Is there some known issue using the debugger when SQL Server is on a
| > Windows
| > | Server 2003 machine? This stored procedure is particularly nasty and
we
| > have
| > | no chance of debugging it without this interface. Please advise.
| > |
| > | Thank you,
| > |
| > | Brad Ashforth
| > |
| >
| >
|