Showing posts with label program. Show all posts
Showing posts with label program. Show all posts

Sunday, March 25, 2012

Can't find the server management studio

hey,

i did the installation, everything went well.

when i want to start the server management studio it isn't in the program files listed.

is there something i can do about it. i did the installation three times now and it didn't change a thing.

all comments are welcome

greetz

TjAnNeHi,

seems you did not insta′ll the client components. If you have another edition than SQL Server Express

(because this does not come with any clients components, unless you install the SQL Server Express Advanced Edition, but as for the non.-Advanced edition you can download the Express Management Studio from here: http://msdn.microsoft.com/vstudio/express/sql/download/)

you can simply rerun the installer and select the client components as well. If this does not solve the problem, please provide some more details about the edition of SQL Server and the SP level.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

During the setup screen process you can choose custom installation and select 'entire feature to be installed on hard drive'. That takes care the installation of required components of tools.

Also explain the steps you are taking to install the tools in this case.

|||I've the developper edition 2005

in fact there're no clients to check

service pack 2

where can i find these

TjAnNE|||the problem is solved
i installed the client and everything works fine,

thx for the tip

TjAnNesql

Thursday, March 22, 2012

can't find database when trying to restore

Hi I am trying to copy a complete database and did the following.
backup database, saved file at location
C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\database.bak
on machine 1-source machine.
I then copied this to
C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\
on machine two-destination machine.
I was thinking I could then use the restore from EM connected to the
destination machine but when I select restore the database name does not show
up as one of the databases that can be selected.
Thanks.
Paul G
Software engineer.
No it wont show the database in Restore database window. It will shoe only
the current database. Use have to use "From Device" option and select the bak
file from there and type the name of database.
Thanks
Ravi
"Paul" wrote:

> Hi I am trying to copy a complete database and did the following.
> backup database, saved file at location
> C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\database.bak
> on machine 1-source machine.
> I then copied this to
> C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\
> on machine two-destination machine.
> I was thinking I could then use the restore from EM connected to the
> destination machine but when I select restore the database name does not show
> up as one of the databases that can be selected.
> Thanks.
> --
> Paul G
> Software engineer.
|||ok thanks it worked!.
Paul G
Software engineer.
"Ravi" wrote:
[vbcol=seagreen]
> No it wont show the database in Restore database window. It will shoe only
> the current database. Use have to use "From Device" option and select the bak
> file from there and type the name of database.
>
> --
> Thanks
> Ravi
>
> "Paul" wrote:

can't find database when trying to restore

Hi I am trying to copy a complete database and did the following.
backup database, saved file at location
C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\database.bak
on machine 1-source machine.
I then copied this to
C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\
on machine two-destination machine.
I was thinking I could then use the restore from EM connected to the
destination machine but when I select restore the database name does not sho
w
up as one of the databases that can be selected.
Thanks.
--
Paul G
Software engineer.No it wont show the database in Restore database window. It will shoe only
the current database. Use have to use "From Device" option and select the ba
k
file from there and type the name of database.
Thanks
Ravi
"Paul" wrote:

> Hi I am trying to copy a complete database and did the following.
> backup database, saved file at location
> C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\database.bak
> on machine 1-source machine.
> I then copied this to
> C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\
> on machine two-destination machine.
> I was thinking I could then use the restore from EM connected to the
> destination machine but when I select restore the database name does not s
how
> up as one of the databases that can be selected.
> Thanks.
> --
> Paul G
> Software engineer.|||ok thanks it worked!.
--
Paul G
Software engineer.
"Ravi" wrote:
[vbcol=seagreen]
> No it wont show the database in Restore database window. It will shoe only
> the current database. Use have to use "From Device" option and select the
bak
> file from there and type the name of database.
>
> --
> Thanks
> Ravi
>
> "Paul" wrote:
>sql

can't find database when trying to restore

Hi I am trying to copy a complete database and did the following.
backup database, saved file at location
C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\database.bak
on machine 1-source machine.
I then copied this to
C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\
on machine two-destination machine.
I was thinking I could then use the restore from EM connected to the
destination machine but when I select restore the database name does not show
up as one of the databases that can be selected.
Thanks.
--
Paul G
Software engineer.No it wont show the database in Restore database window. It will shoe only
the current database. Use have to use "From Device" option and select the bak
file from there and type the name of database.
Thanks
Ravi
"Paul" wrote:
> Hi I am trying to copy a complete database and did the following.
> backup database, saved file at location
> C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\database.bak
> on machine 1-source machine.
> I then copied this to
> C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\
> on machine two-destination machine.
> I was thinking I could then use the restore from EM connected to the
> destination machine but when I select restore the database name does not show
> up as one of the databases that can be selected.
> Thanks.
> --
> Paul G
> Software engineer.|||ok thanks it worked!.
--
Paul G
Software engineer.
"Ravi" wrote:
> No it wont show the database in Restore database window. It will shoe only
> the current database. Use have to use "From Device" option and select the bak
> file from there and type the name of database.
>
> --
> Thanks
> Ravi
>
> "Paul" wrote:
> > Hi I am trying to copy a complete database and did the following.
> > backup database, saved file at location
> > C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\database.bak
> > on machine 1-source machine.
> > I then copied this to
> > C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\
> > on machine two-destination machine.
> > I was thinking I could then use the restore from EM connected to the
> > destination machine but when I select restore the database name does not show
> > up as one of the databases that can be selected.
> > Thanks.
> > --
> > Paul G
> > Software engineer.

Tuesday, March 20, 2012

Can't drop SQL Mobile subscription at Publisher

I have a program running on Pocket PCs that synchronizes with a desktop SQL database using SQL Mobile. My problem is that I can't delete old subscriptions from the publication; now the publication has 25 subscriptions and won't accept any more (limit of SQL Workgroup edition). I can delete non-SQL Mobile subcriptions just fine.

Running sp_replmonitorhelpsubscription provides this information:

subscriber: LVCONTACTSMERGE - 5FA305234F0C
subscriber_db: Program Files\PocketLVContacts\LVContacts.sdf
publisher_db: LVContacts
publication: LVContactsMerge

So I set up this bit of code:

USE LVContacts
EXEC sp_dropmergesubscription
@.publication = 'LVContactsMerge',
@.subscriber = 'LVCONTACTSMERGE - 5FA305234F0C',
@.subscriber_db = 'Program Files\PocketLVContacts\LVContacts.sdf',
@.subscription_type='all';
GO

No errors are reported, but the subscription doesn't get deleted.

I've tried shutting down SQL Server Agent (mentioned in another thread); makes no difference.

Any ideas?

--Evan

If you query sysmergesubscriptions, do you get the same values returned as|||

If you query sysmergesubscriptions, do you get the same values returned as sp_replmonitorhelpsubscription? I'm just wondering if the subscriber_db name returned is correct or not.

|||

Yes, both sysmergesubscriptions and sp_replmonitorhelpsubscription give the same subscriber_db name. Note that the name returned, i.e. 'Program Files\PocketLVContacts\LVContactsData.sdf', is the path on the mobile device.

I wonder if it is safe to manually delete a row from sysmergesubscriptions. It seems to work, but no Distributor clean-up is done.

|||

I've found where I was going wrong. The code I cited in my original post DOES work, but to see the changes you must use sysmergesubscriptions, NOT sp_replmonitorhelpsubscription. The latter apparently reflects the distribution database, which is not cleaned up when you use sp_dropmergesubscription.

When you use SQL Server Management Studio to delete a subscription on a mobile device running SQL Mobile, the subscription on the Publisher is NOT also deleted; you must do it manually (or wait until the subscription expires). But it is difficult to determine which subscription on the Publisher corresponds to the one you want to delete on the mobile Subscriber. What I did was first query the mobile Subscriber system table __sysMergeSubscriptions, note the SubscriptionID field, then query the sysmergesubscriptions on the Publisher database, and find the row with a SubID that matches. Then you can run sp_dropmergesubscription using the subscriber_server field as @.subscriber and the db_name field as @.subscriber_db.

Sunday, March 11, 2012

cant delete odbc tracing file..

Hi all
I can not delete the odbc manager tracing file.
Even after disabling tracing (in the odbc manager)
i get a windows massage saing another program is using the odbc tracing
file...
Can i stop the odbc manager service?
What other programs may be using this log?
There is no other runing programm or sql server job.
Please help, this file is growing so fast!
TIA
Rea
Rea,
Refer the below snippet from :
'PRB: ODBC Tracing to SQL.LOG Can Slow SQL Server or Consume All Disk Space'
http://support.microsoft.com/?id=268591
<start quote>
To turn off ODBC Tracing and remove the associated file, follow these steps:
1.. To disable ODBC Tracing:
1.. For Microsoft Windows NT 4.0:
a.. On the Start menu, click on Control Panel, and then click on Data
Sources(ODBC).
b.. Click on the Tracing tab, and choose Stop Tracing Now.
2.. For Microsoft Windows 2000:
a.. On the Start menu, click on Control Panel, click on Administrative
Tools, and then click on Data Sources (ODBC).
b.. Click on the Tracing tab, and choose Stop Tracing Now.
2.. Stop all ODBC applications, and stop SQL Server. In some cases it may
be necessary to reboot the server to free up the file so that it can be
deleted.
3.. Delete the ODBC Tracing file, usually called "C:\SQL.LOG."
4.. Restart SQL Server.
<end quote>
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"Rea Peleg" <rea_p@.afek.co.il> wrote in message
news:eKbGsGHTEHA.1472@.TK2MSFTNGP09.phx.gbl...
> Hi all
> I can not delete the odbc manager tracing file.
> Even after disabling tracing (in the odbc manager)
> i get a windows massage saing another program is using the odbc tracing
> file...
> Can i stop the odbc manager service?
> What other programs may be using this log?
> There is no other runing programm or sql server job.
> Please help, this file is growing so fast!
> TIA
> Rea
>
|||Thanks alot !
"Dinesh T.K" <tkdinesh@.nospam.mail.tkdinesh.com> wrote in message
news:uaDVzOHTEHA.1732@.TK2MSFTNGP09.phx.gbl...
> Rea,
> Refer the below snippet from :
> 'PRB: ODBC Tracing to SQL.LOG Can Slow SQL Server or Consume All Disk
Space'
> http://support.microsoft.com/?id=268591
> <start quote>
> To turn off ODBC Tracing and remove the associated file, follow these
steps:
> 1.. To disable ODBC Tracing:
> 1.. For Microsoft Windows NT 4.0:
> a.. On the Start menu, click on Control Panel, and then click on
Data
> Sources(ODBC).
> b.. Click on the Tracing tab, and choose Stop Tracing Now.
> 2.. For Microsoft Windows 2000:
> a.. On the Start menu, click on Control Panel, click on
Administrative
> Tools, and then click on Data Sources (ODBC).
> b.. Click on the Tracing tab, and choose Stop Tracing Now.
> 2.. Stop all ODBC applications, and stop SQL Server. In some cases it
may
> be necessary to reboot the server to free up the file so that it can be
> deleted.
> 3.. Delete the ODBC Tracing file, usually called "C:\SQL.LOG."
> 4.. Restart SQL Server.
> <end quote>
> --
> Dinesh
> SQL Server MVP
> --
> --
> SQL Server FAQ at
> http://www.tkdinesh.com
> "Rea Peleg" <rea_p@.afek.co.il> wrote in message
> news:eKbGsGHTEHA.1472@.TK2MSFTNGP09.phx.gbl...
>

cant delete odbc tracing file..

Hi all
I can not delete the odbc manager tracing file.
Even after disabling tracing (in the odbc manager)
i get a windows massage saing another program is using the odbc tracing
file...
Can i stop the odbc manager service'
What other programs may be using this log?
There is no other runing programm or sql server job.
Please help, this file is growing so fast!
TIA
ReaRea,
Refer the below snippet from :
'PRB: ODBC Tracing to SQL.LOG Can Slow SQL Server or Consume All Disk Space'
http://support.microsoft.com/?id=268591
<start quote>
To turn off ODBC Tracing and remove the associated file, follow these steps:
1.. To disable ODBC Tracing:
1.. For Microsoft Windows NT 4.0:
a.. On the Start menu, click on Control Panel, and then click on Data
Sources(ODBC).
b.. Click on the Tracing tab, and choose Stop Tracing Now.
2.. For Microsoft Windows 2000:
a.. On the Start menu, click on Control Panel, click on Administrative
Tools, and then click on Data Sources (ODBC).
b.. Click on the Tracing tab, and choose Stop Tracing Now.
2.. Stop all ODBC applications, and stop SQL Server. In some cases it may
be necessary to reboot the server to free up the file so that it can be
deleted.
3.. Delete the ODBC Tracing file, usually called "C:\SQL.LOG."
4.. Restart SQL Server.
<end quote>
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Rea Peleg" <rea_p@.afek.co.il> wrote in message
news:eKbGsGHTEHA.1472@.TK2MSFTNGP09.phx.gbl...
> Hi all
> I can not delete the odbc manager tracing file.
> Even after disabling tracing (in the odbc manager)
> i get a windows massage saing another program is using the odbc tracing
> file...
> Can i stop the odbc manager service'
> What other programs may be using this log?
> There is no other runing programm or sql server job.
> Please help, this file is growing so fast!
> TIA
> Rea
>|||Thanks alot !
"Dinesh T.K" <tkdinesh@.nospam.mail.tkdinesh.com> wrote in message
news:uaDVzOHTEHA.1732@.TK2MSFTNGP09.phx.gbl...
> Rea,
> Refer the below snippet from :
> 'PRB: ODBC Tracing to SQL.LOG Can Slow SQL Server or Consume All Disk
Space'
> http://support.microsoft.com/?id=268591
> <start quote>
> To turn off ODBC Tracing and remove the associated file, follow these
steps:
> 1.. To disable ODBC Tracing:
> 1.. For Microsoft Windows NT 4.0:
> a.. On the Start menu, click on Control Panel, and then click on
Data
> Sources(ODBC).
> b.. Click on the Tracing tab, and choose Stop Tracing Now.
> 2.. For Microsoft Windows 2000:
> a.. On the Start menu, click on Control Panel, click on
Administrative
> Tools, and then click on Data Sources (ODBC).
> b.. Click on the Tracing tab, and choose Stop Tracing Now.
> 2.. Stop all ODBC applications, and stop SQL Server. In some cases it
may
> be necessary to reboot the server to free up the file so that it can be
> deleted.
> 3.. Delete the ODBC Tracing file, usually called "C:\SQL.LOG."
> 4.. Restart SQL Server.
> <end quote>
> --
> Dinesh
> SQL Server MVP
> --
> --
> SQL Server FAQ at
> http://www.tkdinesh.com
> "Rea Peleg" <rea_p@.afek.co.il> wrote in message
> news:eKbGsGHTEHA.1472@.TK2MSFTNGP09.phx.gbl...
>

Saturday, February 25, 2012

cant connect xp pro sp2 to database on ntserver 4

We have a program using sqlserver7, bde 5.01, msde, which works fine on the
98se machines we have connecting to ntserver4, however we got a new xp pro
machine with sp2, I have mapped the exe to the network and it goes to a login
screen, where it then fails to connect to the database with a generic cannot
connect to database error. I have turned the firewall in xp off to see if
that helps, I have also included the exe and the instance of sql server on
the list of exceptions
in the firewall
any ideas what I'm missing?
managed to fix the problem ourselves, looked in the registry settings for
borland, turns out the config file was looking at the server but the dll was
looking locally, so we repointed the dll to the server borland folder and hey
presto program connects and works fine
another side point, I was able to export the borland registry key from a
98se machine into the xp pro machine to enable quick setup of borland on xp
"seatzie" wrote:

> We have a program using sqlserver7, bde 5.01, msde, which works fine on the
> 98se machines we have connecting to ntserver4, however we got a new xp pro
> machine with sp2, I have mapped the exe to the network and it goes to a login
> screen, where it then fails to connect to the database with a generic cannot
> connect to database error. I have turned the firewall in xp off to see if
> that helps, I have also included the exe and the instance of sql server on
> the list of exceptions
> in the firewall
> any ideas what I'm missing?

cant connect xp pro sp2 to database on ntserver 4

We have a program using sqlserver7, bde 5.01, msde, which works fine on the
98se machines we have connecting to ntserver4, however we got a new xp pro
machine with sp2, I have mapped the exe to the network and it goes to a logi
n
screen, where it then fails to connect to the database with a generic cannot
connect to database error. I have turned the firewall in xp off to see if
that helps, I have also included the exe and the instance of sql server on
the list of exceptions
in the firewall
any ideas what I'm missing?managed to fix the problem ourselves, looked in the registry settings for
borland, turns out the config file was looking at the server but the dll was
looking locally, so we repointed the dll to the server borland folder and he
y
presto program connects and works fine
another side point, I was able to export the borland registry key from a
98se machine into the xp pro machine to enable quick setup of borland on xp
"seatzie" wrote:

> We have a program using sqlserver7, bde 5.01, msde, which works fine on th
e
> 98se machines we have connecting to ntserver4, however we got a new xp pro
> machine with sp2, I have mapped the exe to the network and it goes to a lo
gin
> screen, where it then fails to connect to the database with a generic cann
ot
> connect to database error. I have turned the firewall in xp off to see if
> that helps, I have also included the exe and the instance of sql server on
> the list of exceptions
> in the firewall
> any ideas what I'm missing?

Friday, February 24, 2012

can't connect to the ODBC database named aspol54

can any one provide any suggestions to help this error i installed automation studion 5.4 and the program will not run on my laptop.

i traced the data below when i try to start the program.

AsProjet db0-b5c ENTER SQLAllocEnv
HENV * 015CF6B0

AsProjet db0-b5c EXIT SQLAllocEnv with return code 0 (SQL_SUCCESS)
HENV * 0x015CF6B0 ( 0x015e1540)

AsProjet db0-b5c ENTER SQLGetEnvAttr
SQLHENV 015E1540
SQLINTEGER 201 <unknown>
SQLPOINTER [Unknown attribute 201]
SQLINTEGER 4
SQLINTEGER * 0x0013E380

AsProjet db0-b5c EXIT SQLGetEnvAttr with return code 0 (SQL_SUCCESS)
SQLHENV 015E1540
SQLINTEGER 201 <unknown>
SQLPOINTER [Unknown attribute 201]
SQLINTEGER 4
SQLINTEGER * 0x0013E380 (1567744)
any help would be great.

tks

I don't know how much help this is, but the '201' attribute is for 'SQL_ATTR_CONNECTION_POOLING'. The weird thing is that the return value seems to be 1567744. It should be returning '0' in this case. Here are possible values (from SQLEXT.H):

/* values for SQL_ATTR_CONNECTION_POOLING */
#define SQL_CP_OFF 0UL
#define SQL_CP_ONE_PER_DRIVER 1UL
#define SQL_CP_ONE_PER_HENV 2UL
#define SQL_CP_DEFAULT SQL_CP_OFF

It looks like you're receiving invalid data, but I don't know why or how. Sorry I can't be of more help.

Perhaps someone else on the alias can shed some light on this?

|||

Hi,

In addition to Warren's comments - what you see in the ODBC trace doesn't indicate an error. Simply an Environment handle was allocated and GetEnvAttr was called to retrieve the Environment's connection pooling attribute setting. Both calls appear to have succeeded. The fact that we get a strange value, probably means that the ODBC driver doesn't support it (it's an ODBC 3.0 attribute). Is the application using the driver directly (without Driver Manager)? Could you post the actual error that you get or is there any additional information in the ODBC trace?

HTH,

Jivko Dobrev - MSFT


This posting is provided "AS IS" with no warranties, and confers no rights.

Tuesday, February 14, 2012

Cant connect to MSDE on XPSP1

We are writing a setup program for a customer that requires a MSDE
installation.
Using the following flags for the MSDE setup.exe:
SAPWD = "password" SECURITYMODE=SQL
The setup complete successfully, we are restarting the installed machine
(SQL services restarts as well)
But we cannot connect to the MSDE from any enterprise manager (Enterprise,
Developer versions)
This happens only when the MSDE installed on a WindowsXP SP1 machine.
Can someone help us solve this problem?
Thanks,
Shif
It may be that you don't have any network protocols enabled for MSDE. Run
the tool svrnetcn.exe (you'll find it in C:\Program Files\Microsoft SQL
Server\80\Tools\Binn) and check to make sure that you have the necessary
protocols enabled.
Jim
"Shif Arad" <shif@.inter.net.il> wrote in message
news:Om8nd%23vJEHA.2604@.tk2msftngp13.phx.gbl...
> We are writing a setup program for a customer that requires a MSDE
> installation.
> Using the following flags for the MSDE setup.exe:
> SAPWD = "password" SECURITYMODE=SQL
>
> The setup complete successfully, we are restarting the installed machine
> (SQL services restarts as well)
> But we cannot connect to the MSDE from any enterprise manager (Enterprise,
> Developer versions)
> This happens only when the MSDE installed on a WindowsXP SP1 machine.
>
> Can someone help us solve this problem?
> Thanks,
> Shif
>

Cant connect to MSDE on XPSP1

We are writing a setup program for a customer that requires a MSDE
installation.
Using the following flags for the MSDE setup.exe:
SAPWD = "password" SECURITYMODE=SQL
The setup complete successfully, we are restarting the installed machine
(SQL services restarts as well)
But we cannot connect to the MSDE from any enterprise manager
(Enterprise,Developer versions)
This happens only when the MSDE installed on a WindowsXP SP1 machine.
Can someone help us solve this problem?
Thanks,
Shif
Verify that the MSDE is listening on TCP/IP. Check the NT Application logs
after MSDE is started.
If it's only listening on Shared Memory, then only local connections will
succeed.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||Hi,
How can i change this option AND in what menu should i look for it ?
Thank
Javier A. Junca Barreto.
Desarrollo de Sistemas
SICyA Software.
Web: www.sicya.com
Mail: desarrollo@.sicya.com
Tel: (57 1) 272 0738
|||MSDE doesn't ship with any utilities. So, you could change this via the
registry.
Check the following registry key on your server:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSDE Name Here
\MSSQLServer\SuperSocketNetLib
Add np and or tcp to the ProtocolList value.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Cant connect to MSDE on XPSP1

We are writing a setup program for a customer that requires a MSDE
installation.
Using the following flags for the MSDE setup.exe:
SAPWD = "password" SECURITYMODE=SQL
The setup complete successfully, we are restarting the installed machine
(SQL services restarts as well)
But we cannot connect to the MSDE from any enterprise manager
(Enterprise,Developer versions)
This happens only when the MSDE installed on a WindowsXP SP1 machine.
Can someone help us solve this problem?
Thanks,
ShifVerify that the MSDE is listening on TCP/IP. Check the NT Application logs
after MSDE is started.
If it's only listening on Shared Memory, then only local connections will
succeed.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Hi,
How can i change this option AND in what menu should i look for it ?
Thank
Javier A. Junca Barreto.
Desarrollo de Sistemas
SICyA Software.
Web: www.sicya.com
Mail: desarrollo@.sicya.com
Tel: (57 1) 272 0738|||MSDE doesn't ship with any utilities. So, you could change this via the
registry.
Check the following registry key on your server:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Mi
crosoft SQL Server\MSDE Name Here
\MSSQLServer\SuperSocketNetLib
Add np and or tcp to the ProtocolList value.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.