Is there any way to install a System DSN to all the pcs on my 2003 network?
(clients running xp)
either by a GPO or something else?]
i dont want to have to go around every pc doing itSystem DSN's are stored in the registry. making it somewhat difficult to
distribute.
You could change ther registry on one computer, save the registry to .reg
file, distrubute to all computers, and execute a custom script to import the
value.
ODBC entries are located in the registry in two spots. Both are under the
HKEY_Local_Machine\Software\ODBC
The first is found in the ODBC Data Sources subkey
The second set of registry entries go in the ODBC.INI subkey.
there are applications to help you do this as well...
http://www.freevbcode.com/ShowCode.asp?ID=3369
If it was me I would try my hardest to change the Datasource on the
application level before changing alot of computers.
--
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
*/
"MatthewWilsonAPD" <MatthewWilsonAPD@.discussions.microsoft.com> wrote in
message news:2DF39EDF-40A9-4FAB-9E72-7BEB554A7FAA@.microsoft.com...
> Is there any way to install a System DSN to all the pcs on my 2003
> network?
> (clients running xp)
> either by a GPO or something else?]
> i dont want to have to go around every pc doing it|||DSNs are just registry entries so you could create a
VBScript to deploy or call from login scripts...whichever.
Take a look at the following example:
http://www.databasejournal.com/feat...cle.php/2238221
-Sue
On Fri, 8 Sep 2006 08:24:02 -0700, MatthewWilsonAPD
<MatthewWilsonAPD@.discussions.microsoft.com> wrote:
>Is there any way to install a System DSN to all the pcs on my 2003 network?
>(clients running xp)
>either by a GPO or something else?]
>i dont want to have to go around every pc doing it
Showing posts with label installing. Show all posts
Showing posts with label installing. Show all posts
Friday, March 23, 2012
Wednesday, March 7, 2012
Remote Debugging Problems w/ VS.net 2005 SP1
I have done through all the MSDN documentation and Googled everything I could
on the errors I am receiving about installing and configuring remote
debugging. I believe it is communications related. This is the scenario:
The Visual Studio 2005 Remote Debugger service is started on the remote
database server that I want to debug SQL code on as Local System. I am a
member of the local administrators group on that server and a member of the
sa role in SQL Server. I configured all the DCOM settings on both the remote
server and my local workstation, which is running XP SP2, and opened the
firewall exceptions on my workstation.
When I attempt to step into a procedure, the message " Unable to start T-SQL
Debugging. Could not attach to SQL Server process on 'daysqltest02'. Remote
calls are not allowed for this process." displays. If I manually run the
Visual Studio Remote Debugging Monitor interactively on the remote server,
when I attempt to step into a procedure, an entry is displayed in the monitor
that a connection from my workstation has been made and the following message
is displayed "Unable to start T-SQL Debugging. Could not connect to computer
'daysqltest02'. The Microsoft Visual Studio Remote Debugging Monitor on the
remote computer does not have permission to connect to this computer. Please
see Help for assistance."
Other people in my office on the same network or other networks can
successfully debug and there is not firewall between my workstation and the
remote server so I know it is something with my security or communications
configuration. Any assistance would be much appreciated. Thanks in advance.
Ken
Hi Parch,
I suggest you try the tool SQL Ultimate Debugger:
http://lakesidesql.com/downloads/PFD/1_0_2007_809/PFDebugger_Setup_08-09-2007.zip.
This tool is a post factum debugger and allows you to trace and
debug obejcts (SP's Triggers, FN's, etc.) that had been executed. It's
waaaay better than the T-SQL debugger in VS. Also, since this software has
not yet been officially realeased, I would not recommend (YET) to use it in
a production environment.
You can learn more about it here:
http://208.75.249.50/products/sql-ultimate-debugger/screenshots.html. If you
want a copy of its documentation. shoot me an email and i can send it to
you.
I hope that helps.
"parchk" <parchk@.discussions.microsoft.com> wrote in message
news:F5E08E79-2BC6-4991-904A-A87465073520@.microsoft.com...
>I have done through all the MSDN documentation and Googled everything I
>could
> on the errors I am receiving about installing and configuring remote
> debugging. I believe it is communications related. This is the scenario:
> The Visual Studio 2005 Remote Debugger service is started on the remote
> database server that I want to debug SQL code on as Local System. I am a
> member of the local administrators group on that server and a member of
> the
> sa role in SQL Server. I configured all the DCOM settings on both the
> remote
> server and my local workstation, which is running XP SP2, and opened the
> firewall exceptions on my workstation.
> When I attempt to step into a procedure, the message " Unable to start
> T-SQL
> Debugging. Could not attach to SQL Server process on 'daysqltest02'.
> Remote
> calls are not allowed for this process." displays. If I manually run the
> Visual Studio Remote Debugging Monitor interactively on the remote server,
> when I attempt to step into a procedure, an entry is displayed in the
> monitor
> that a connection from my workstation has been made and the following
> message
> is displayed "Unable to start T-SQL Debugging. Could not connect to
> computer
> 'daysqltest02'. The Microsoft Visual Studio Remote Debugging Monitor on
> the
> remote computer does not have permission to connect to this computer.
> Please
> see Help for assistance."
> Other people in my office on the same network or other networks can
> successfully debug and there is not firewall between my workstation and
> the
> remote server so I know it is something with my security or communications
> configuration. Any assistance would be much appreciated. Thanks in
> advance.
> Ken
|||Hi Parch,
I suggest you try the tool SQL Ultimate Debugger:
http://lakesidesql.com/downloads/PFD/1_0_2007_809/PFDebugger_Setup_08-09-2007.zip.
This tool is a post factum debugger and allows you to trace and
debug obejcts (SP's Triggers, FN's, etc.) that had been executed. It's
waaaay better than the T-SQL debugger in VS. Also, since this software has
not yet been officially realeased, I would not recommend (YET) to use it in
a production environment.
You can learn more about it here:
http://208.75.249.50/products/sql-ultimate-debugger/screenshots.html. If you
want a copy of its documentation. shoot me an email and i can send it to
you.
I hope that helps.
"parchk" <parchk@.discussions.microsoft.com> wrote in message
news:F5E08E79-2BC6-4991-904A-A87465073520@.microsoft.com...
>I have done through all the MSDN documentation and Googled everything I
>could
> on the errors I am receiving about installing and configuring remote
> debugging. I believe it is communications related. This is the scenario:
> The Visual Studio 2005 Remote Debugger service is started on the remote
> database server that I want to debug SQL code on as Local System. I am a
> member of the local administrators group on that server and a member of
> the
> sa role in SQL Server. I configured all the DCOM settings on both the
> remote
> server and my local workstation, which is running XP SP2, and opened the
> firewall exceptions on my workstation.
> When I attempt to step into a procedure, the message " Unable to start
> T-SQL
> Debugging. Could not attach to SQL Server process on 'daysqltest02'.
> Remote
> calls are not allowed for this process." displays. If I manually run the
> Visual Studio Remote Debugging Monitor interactively on the remote server,
> when I attempt to step into a procedure, an entry is displayed in the
> monitor
> that a connection from my workstation has been made and the following
> message
> is displayed "Unable to start T-SQL Debugging. Could not connect to
> computer
> 'daysqltest02'. The Microsoft Visual Studio Remote Debugging Monitor on
> the
> remote computer does not have permission to connect to this computer.
> Please
> see Help for assistance."
> Other people in my office on the same network or other networks can
> successfully debug and there is not firewall between my workstation and
> the
> remote server so I know it is something with my security or communications
> configuration. Any assistance would be much appreciated. Thanks in
> advance.
> Ken
|||Thanks for the information. I will definitely look at this product and would
appreciate a copy of the documentation for review.
With this product, can stored procedures be interactiely debugged?
"The DBA" wrote:
> Hi Parch,
> I suggest you try the tool SQL Ultimate Debugger:
> http://lakesidesql.com/downloads/PFD/1_0_2007_809/PFDebugger_Setup_08-09-2007.zip.
> This tool is a post factum debugger and allows you to trace and
> debug obejcts (SP's Triggers, FN's, etc.) that had been executed. It's
> waaaay better than the T-SQL debugger in VS. Also, since this software has
> not yet been officially realeased, I would not recommend (YET) to use it in
> a production environment.
> You can learn more about it here:
> http://208.75.249.50/products/sql-ultimate-debugger/screenshots.html. If you
> want a copy of its documentation. shoot me an email and i can send it to
> you.
> I hope that helps.
>
>
> "parchk" <parchk@.discussions.microsoft.com> wrote in message
> news:F5E08E79-2BC6-4991-904A-A87465073520@.microsoft.com...
>
on the errors I am receiving about installing and configuring remote
debugging. I believe it is communications related. This is the scenario:
The Visual Studio 2005 Remote Debugger service is started on the remote
database server that I want to debug SQL code on as Local System. I am a
member of the local administrators group on that server and a member of the
sa role in SQL Server. I configured all the DCOM settings on both the remote
server and my local workstation, which is running XP SP2, and opened the
firewall exceptions on my workstation.
When I attempt to step into a procedure, the message " Unable to start T-SQL
Debugging. Could not attach to SQL Server process on 'daysqltest02'. Remote
calls are not allowed for this process." displays. If I manually run the
Visual Studio Remote Debugging Monitor interactively on the remote server,
when I attempt to step into a procedure, an entry is displayed in the monitor
that a connection from my workstation has been made and the following message
is displayed "Unable to start T-SQL Debugging. Could not connect to computer
'daysqltest02'. The Microsoft Visual Studio Remote Debugging Monitor on the
remote computer does not have permission to connect to this computer. Please
see Help for assistance."
Other people in my office on the same network or other networks can
successfully debug and there is not firewall between my workstation and the
remote server so I know it is something with my security or communications
configuration. Any assistance would be much appreciated. Thanks in advance.
Ken
Hi Parch,
I suggest you try the tool SQL Ultimate Debugger:
http://lakesidesql.com/downloads/PFD/1_0_2007_809/PFDebugger_Setup_08-09-2007.zip.
This tool is a post factum debugger and allows you to trace and
debug obejcts (SP's Triggers, FN's, etc.) that had been executed. It's
waaaay better than the T-SQL debugger in VS. Also, since this software has
not yet been officially realeased, I would not recommend (YET) to use it in
a production environment.
You can learn more about it here:
http://208.75.249.50/products/sql-ultimate-debugger/screenshots.html. If you
want a copy of its documentation. shoot me an email and i can send it to
you.
I hope that helps.
"parchk" <parchk@.discussions.microsoft.com> wrote in message
news:F5E08E79-2BC6-4991-904A-A87465073520@.microsoft.com...
>I have done through all the MSDN documentation and Googled everything I
>could
> on the errors I am receiving about installing and configuring remote
> debugging. I believe it is communications related. This is the scenario:
> The Visual Studio 2005 Remote Debugger service is started on the remote
> database server that I want to debug SQL code on as Local System. I am a
> member of the local administrators group on that server and a member of
> the
> sa role in SQL Server. I configured all the DCOM settings on both the
> remote
> server and my local workstation, which is running XP SP2, and opened the
> firewall exceptions on my workstation.
> When I attempt to step into a procedure, the message " Unable to start
> T-SQL
> Debugging. Could not attach to SQL Server process on 'daysqltest02'.
> Remote
> calls are not allowed for this process." displays. If I manually run the
> Visual Studio Remote Debugging Monitor interactively on the remote server,
> when I attempt to step into a procedure, an entry is displayed in the
> monitor
> that a connection from my workstation has been made and the following
> message
> is displayed "Unable to start T-SQL Debugging. Could not connect to
> computer
> 'daysqltest02'. The Microsoft Visual Studio Remote Debugging Monitor on
> the
> remote computer does not have permission to connect to this computer.
> Please
> see Help for assistance."
> Other people in my office on the same network or other networks can
> successfully debug and there is not firewall between my workstation and
> the
> remote server so I know it is something with my security or communications
> configuration. Any assistance would be much appreciated. Thanks in
> advance.
> Ken
|||Hi Parch,
I suggest you try the tool SQL Ultimate Debugger:
http://lakesidesql.com/downloads/PFD/1_0_2007_809/PFDebugger_Setup_08-09-2007.zip.
This tool is a post factum debugger and allows you to trace and
debug obejcts (SP's Triggers, FN's, etc.) that had been executed. It's
waaaay better than the T-SQL debugger in VS. Also, since this software has
not yet been officially realeased, I would not recommend (YET) to use it in
a production environment.
You can learn more about it here:
http://208.75.249.50/products/sql-ultimate-debugger/screenshots.html. If you
want a copy of its documentation. shoot me an email and i can send it to
you.
I hope that helps.
"parchk" <parchk@.discussions.microsoft.com> wrote in message
news:F5E08E79-2BC6-4991-904A-A87465073520@.microsoft.com...
>I have done through all the MSDN documentation and Googled everything I
>could
> on the errors I am receiving about installing and configuring remote
> debugging. I believe it is communications related. This is the scenario:
> The Visual Studio 2005 Remote Debugger service is started on the remote
> database server that I want to debug SQL code on as Local System. I am a
> member of the local administrators group on that server and a member of
> the
> sa role in SQL Server. I configured all the DCOM settings on both the
> remote
> server and my local workstation, which is running XP SP2, and opened the
> firewall exceptions on my workstation.
> When I attempt to step into a procedure, the message " Unable to start
> T-SQL
> Debugging. Could not attach to SQL Server process on 'daysqltest02'.
> Remote
> calls are not allowed for this process." displays. If I manually run the
> Visual Studio Remote Debugging Monitor interactively on the remote server,
> when I attempt to step into a procedure, an entry is displayed in the
> monitor
> that a connection from my workstation has been made and the following
> message
> is displayed "Unable to start T-SQL Debugging. Could not connect to
> computer
> 'daysqltest02'. The Microsoft Visual Studio Remote Debugging Monitor on
> the
> remote computer does not have permission to connect to this computer.
> Please
> see Help for assistance."
> Other people in my office on the same network or other networks can
> successfully debug and there is not firewall between my workstation and
> the
> remote server so I know it is something with my security or communications
> configuration. Any assistance would be much appreciated. Thanks in
> advance.
> Ken
|||Thanks for the information. I will definitely look at this product and would
appreciate a copy of the documentation for review.
With this product, can stored procedures be interactiely debugged?
"The DBA" wrote:
> Hi Parch,
> I suggest you try the tool SQL Ultimate Debugger:
> http://lakesidesql.com/downloads/PFD/1_0_2007_809/PFDebugger_Setup_08-09-2007.zip.
> This tool is a post factum debugger and allows you to trace and
> debug obejcts (SP's Triggers, FN's, etc.) that had been executed. It's
> waaaay better than the T-SQL debugger in VS. Also, since this software has
> not yet been officially realeased, I would not recommend (YET) to use it in
> a production environment.
> You can learn more about it here:
> http://208.75.249.50/products/sql-ultimate-debugger/screenshots.html. If you
> want a copy of its documentation. shoot me an email and i can send it to
> you.
> I hope that helps.
>
>
> "parchk" <parchk@.discussions.microsoft.com> wrote in message
> news:F5E08E79-2BC6-4991-904A-A87465073520@.microsoft.com...
>
Subscribe to:
Posts (Atom)