I was able to connect to a SQL Server 2000 instance using ODBC on a Windows
2000 workstation (Service Pack 4). But after installing several security
updates and rollups, I am no longer able to connect to SQL Server.
The drivers tab in the ODBC Administrator lists SQL Server as Not marked
under Version and Company. Another machine that was not as updated lists
Version as 3.70.06.90 and Company as Microsoft.
Have you run component checker to verify your MDAC
installation? You could also try reinstalling MDAC - sounds
like the issue is likely with once of the MDAC components.
You can download component checker and mdac versions from:
http://msdn.microsoft.com/data/mdac/...s/default.aspx
-Sue
On Mon, 3 Oct 2005 10:42:01 -0700, "Alton Chinn" <Alton
Chinn@.discussions.microsoft.com> wrote:
>I was able to connect to a SQL Server 2000 instance using ODBC on a Windows
>2000 workstation (Service Pack 4). But after installing several security
>updates and rollups, I am no longer able to connect to SQL Server.
>The drivers tab in the ODBC Administrator lists SQL Server as Not marked
>under Version and Company. Another machine that was not as updated lists
>Version as 3.70.06.90 and Company as Microsoft.
|||I used it to determine that the various windows updates and hotfixes may have
knocked my MDAC version down to 2.5 SP3. For the SQL Server connection to
work, the version has to be at least 2.6 RTM, I think.
I tried to bring the version up to 2.8 but the rollback would always fail.
I tried to rename ODBCCONF.DLL and run unmgrt, then re-run mdac_type, but
that did not seem to work.
Alton
"Sue Hoegemeier" wrote:
> Have you run component checker to verify your MDAC
> installation? You could also try reinstalling MDAC - sounds
> like the issue is likely with once of the MDAC components.
> You can download component checker and mdac versions from:
> http://msdn.microsoft.com/data/mdac/...s/default.aspx
> -Sue
> On Mon, 3 Oct 2005 10:42:01 -0700, "Alton Chinn" <Alton
> Chinn@.discussions.microsoft.com> wrote:
>
>
|||You're going to have to get that MDAC updated. Don't try a rollback. Just
install the latest MDAC over the top. If you get an error try rebooting. If
that doesn't work, post the error and we'll help you out from there.
MeanOldDBA
derrickleggett@.hotmail.com
http://weblogs.sqlteam.com/derrickl
When life gives you a lemon, fire the DBA.
"Alton Chinn" wrote:
[vbcol=seagreen]
> I used it to determine that the various windows updates and hotfixes may have
> knocked my MDAC version down to 2.5 SP3. For the SQL Server connection to
> work, the version has to be at least 2.6 RTM, I think.
> I tried to bring the version up to 2.8 but the rollback would always fail.
> I tried to rename ODBCCONF.DLL and run unmgrt, then re-run mdac_type, but
> that did not seem to work.
> Alton
> "Sue Hoegemeier" wrote:
|||I tried running mdac_type.exe for version 2.8 sp1. After copying the new
files, it starts rolling back components automatically. Then I get a message
saying the setup failed to complete. After restarting, I ran the checker and
it lists the verison as 2.5 sp3.
Alton
"MeanOldDBA" wrote:
[vbcol=seagreen]
> You're going to have to get that MDAC updated. Don't try a rollback. Just
> install the latest MDAC over the top. If you get an error try rebooting. If
> that doesn't work, post the error and we'll help you out from there.
> --
> MeanOldDBA
> derrickleggett@.hotmail.com
> http://weblogs.sqlteam.com/derrickl
> When life gives you a lemon, fire the DBA.
>
> "Alton Chinn" wrote:
|||First try reading through the MDAC setup troubleshooting
guide:
http://support.microsoft.com/?id=232060
Typically you get more information in the error than just
setup failed to complete - that may provide more pointers to
what is going on.
I remember an issue with automatic rollbacks with other
versions of MDAC - see the info in the following:
http://support.microsoft.com/?id=286442
You may want to check the event logs to see if you have
something similar going on.
-Sue
On Tue, 4 Oct 2005 11:22:02 -0700, "Alton Chinn"
<AltonChinn@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>I tried running mdac_type.exe for version 2.8 sp1. After copying the new
>files, it starts rolling back components automatically. Then I get a message
>saying the setup failed to complete. After restarting, I ran the checker and
>it lists the verison as 2.5 sp3.
>Alton
>
>"MeanOldDBA" wrote:
|||According to dasetup, installation fails at the ODBC configuration:
************************************************** *****
ODBCConf called with arguments: '/S /Lv C:\WINNT\dasetup.log /F
C:\WINNT\system32\sqlclnt.rsp'
Data Struct:
Reboot First : 0
Use Response File : 1
Response File : 'C:\WINNT\system32\sqlclnt.rsp'
Erase Response File: 0
Silent : 1
Continue on Error : 0
Log Mode : 2
Log File : 'C:\WINNT\dasetup.log'
Actions:
5, 'SQL Server|Driver=SQLSRV32.dll||', '(null)', '"SQL
Server|Driver=SQLSRV32.dll||"'
1, 'SQL Server', 'CPTimeout=60', '"SQL Server" "CPTimeout=60"'
2, 'SQL Server', 'DSN=MQIS|Server=(Local)|Description=SQL
Server|Database=MQIS||', '"SQL Server"
"DSN=MQIS|Server=(Local)|Description=SQL Server|Database=MQIS||"'
EXECUTING ACTIONS
Executing Action: INSTALLDRIVER
arg1: 'SQL Server|Driver=SQLSRV32.dll||'
arg2: '(null)'
args: '"SQL Server|Driver=SQLSRV32.dll||"'
INSTALLDRIVER SQLInstallDriverEx succeeded
Return HR: 0x0
Executing Action: CONFIGDRIVER
arg1: 'SQL Server'
arg2: 'CPTimeout=60'
args: '"SQL Server" "CPTimeout=60"'
CONFIGDRIVER SQLConfigDriver succeeded
Return HR: 0x0
Executing Action: CONFIGDSN
arg1: 'SQL Server'
arg2: 'DSN=MQIS|Server=(Local)|Description=SQL Server|Database=MQIS||'
args: '"SQL Server" "DSN=MQIS|Server=(Local)|Description=SQL
Server|Database=MQIS||"'
CONFIGDSN Unable to create a data source for the 'SQL Server' driver:
Could not load the setup or translator library
Return HR: 0x80004005
Error Executing Action: CONFIGDSN
Unable to create a data source for the 'SQL Server' driver:
Could not load the setup or translator library with error code -2147467259
Debug: Loaded string resource: 4. Characters = 23
Debug: Loaded string resource: 6. Characters = 16
Calling function: RestoreCatalog
RestoreCatalog: Success.
Entering function: ExecuteInstall()
Parameters:
nDirective = 5
hWnd = 0x00090042
pwcsInfFile = C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP\SQLODB C.INF
pwcsCabFile = (null)
pwcsSection = DefaultInstall
pwcsExtractPath = C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP
dwSetupFlags = 64
pContext = 0x0012B450
************************************************** *****
After that, the program starts to execute UNREGW2KMIGRATION.
|||Don't know what else to tell you. If you get an error, it
should be listed in the bottom of the log you posted -
that's the relevant part - where it goes into the
Entering function: ExecuteInstall()
-Sue
On Wed, 5 Oct 2005 10:26:14 -0700, "Alton Chinn"
<AltonChinn@.discussions.microsoft.com> wrote:
>According to dasetup, installation fails at the ODBC configuration:
>************************************************* ******
>ODBCConf called with arguments: '/S /Lv C:\WINNT\dasetup.log /F
>C:\WINNT\system32\sqlclnt.rsp'
>Data Struct:
>Reboot First : 0
>Use Response File : 1
>Response File : 'C:\WINNT\system32\sqlclnt.rsp'
>Erase Response File: 0
>Silent : 1
>Continue on Error : 0
>Log Mode : 2
>Log File : 'C:\WINNT\dasetup.log'
>Actions:
>5, 'SQL Server|Driver=SQLSRV32.dll||', '(null)', '"SQL
>Server|Driver=SQLSRV32.dll||"'
>1, 'SQL Server', 'CPTimeout=60', '"SQL Server" "CPTimeout=60"'
>2, 'SQL Server', 'DSN=MQIS|Server=(Local)|Description=SQL
>Server|Database=MQIS||', '"SQL Server"
>"DSN=MQIS|Server=(Local)|Description=SQL Server|Database=MQIS||"'
>EXECUTING ACTIONS
>Executing Action: INSTALLDRIVER
> arg1: 'SQL Server|Driver=SQLSRV32.dll||'
> arg2: '(null)'
> args: '"SQL Server|Driver=SQLSRV32.dll||"'
>INSTALLDRIVER SQLInstallDriverEx succeeded
> Return HR: 0x0
>Executing Action: CONFIGDRIVER
> arg1: 'SQL Server'
> arg2: 'CPTimeout=60'
> args: '"SQL Server" "CPTimeout=60"'
>CONFIGDRIVER SQLConfigDriver succeeded
> Return HR: 0x0
>Executing Action: CONFIGDSN
> arg1: 'SQL Server'
> arg2: 'DSN=MQIS|Server=(Local)|Description=SQL Server|Database=MQIS||'
> args: '"SQL Server" "DSN=MQIS|Server=(Local)|Description=SQL
>Server|Database=MQIS||"'
>CONFIGDSN Unable to create a data source for the 'SQL Server' driver:
>Could not load the setup or translator library
> Return HR: 0x80004005
>Error Executing Action: CONFIGDSN
>Unable to create a data source for the 'SQL Server' driver:
>Could not load the setup or translator library with error code -2147467259
>Debug: Loaded string resource: 4. Characters = 23
>Debug: Loaded string resource: 6. Characters = 16
>Calling function: RestoreCatalog
>RestoreCatalog: Success.
>Entering function: ExecuteInstall()
>Parameters:
>nDirective = 5
>hWnd = 0x00090042
>pwcsInfFile = C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP\SQLODB C.INF
>pwcsCabFile = (null)
>pwcsSection = DefaultInstall
>pwcsExtractPath = C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP
>dwSetupFlags = 64
>pContext = 0x0012B450
>************************************************* ******
>After that, the program starts to execute UNREGW2KMIGRATION.
>
|||HERE ARE THE VARIOUS CALLS TO ExecuteFunction():
Entering function: CJob::InitializeJobQueues()
Parameters:
hHive = 0x80000002
szRoot = Software\Microsoft\dasetup\jobs
Exiting function: CJob::InitializeJobQueues()
Return value: (HRESULT) 0x00000000
Debug: Loaded string resource: 3. Characters = 21
Debug: Loaded string resource: 5. Characters = 14
Calling function: BackupCatalog
BackupCatalog Result : Backup Catalog directory already exists for this
component.
Entering function: ExecuteInstall()
Parameters:
nDirective = 4
hWnd = 0x0004014C
pwcsInfFile = C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP\MDACXP AK.INF
pwcsCabFile = (null)
pwcsSection = DefaultInstall
pwcsExtractPath = C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP
dwSetupFlags = 32
pContext = 0x0012B450
INSTALLW2KMIGRATIONPACK Getting OS Version Info
INSTALLW2KMIGRATIONPACK Testing
C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP\MDACXP AK.INF for existance
INSTALLW2KMIGRATIONPACK Get the ComponentID
INSTALLW2KMIGRATIONPACK Setting SysSetup Function Pointers
INSTALLW2KMIGRATIONPACK HINSTANCE: 1727987712
INSTALLW2KMIGRATIONPACK SetupRegisterOsComponent ProcAddress: 1728218877
INSTALLW2KMIGRATIONPACK SetupUnRegisterOsComponent ProcAddress: 1728219747
INSTALLW2KMIGRATIONPACK SetupQueryRegisteredOsComponent ProcAddress:
1728220575
INSTALLW2KMIGRATIONPACK SetupQueryRegisteredOsComponent Failed with Error : 2
************
Executing Action: REGTYPELIB
arg1: 'simpdata.tlb'
arg2: '(null)'
args: '"simpdata.tlb"'
Return HR: 0x0
Debug: Loaded string resource: 3. Characters = 21
Debug: Loaded string resource: 5. Characters = 14
Calling function: BackupCatalog
BackupCatalog Result : Backup Catalog directory already exists for this
component.
Entering function: ExecuteInstall()
Parameters:
nDirective = 4
hWnd = 0x0004014C
pwcsInfFile = C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP\MSXMLX .inf
pwcsCabFile = (null)
pwcsSection = DefaultInstall
pwcsExtractPath = C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP
dwSetupFlags = 32
pContext = 0x0012B450
INSTALLW2KMIGRATIONPACK Getting OS Version Info
INSTALLW2KMIGRATIONPACK Testing
C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP\MSXMLX .inf for existance
INSTALLW2KMIGRATIONPACK Get the ComponentID
INSTALLW2KMIGRATIONPACK SetupQueryRegisteredOsComponent Failed with Error : 2
*************
Calling function: BackupCatalog
BackupCatalog Result : Backup Catalog directory already exists for this
component.
Entering function: ExecuteInstall()
Parameters:
nDirective = 4
hWnd = 0x0004014C
pwcsInfFile = C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP\SQLXML XP.inf
pwcsCabFile = (null)
pwcsSection = DefaultInstall
pwcsExtractPath = C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP
dwSetupFlags = 32
pContext = 0x0012B450
INSTALLW2KMIGRATIONPACK Getting OS Version Info
INSTALLW2KMIGRATIONPACK Testing
C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP\SQLXML XP.inf for existance
INSTALLW2KMIGRATIONPACK Get the ComponentID
INSTALLW2KMIGRATIONPACK SetupQueryRegisteredOsComponent Failed with Error : 2
*************
Calling function: BackupCatalog
BackupCatalog Result : Backup Catalog directory already exists for this
component.
Entering function: ExecuteInstall()
Parameters:
nDirective = 4
hWnd = 0x0004014C
pwcsInfFile = C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP\SQLNET .INF
pwcsCabFile = (null)
pwcsSection = DefaultInstall
pwcsExtractPath = C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP
dwSetupFlags = 32
pContext = 0x0012B450
INSTALLW2KMIGRATIONPACK Getting OS Version Info
INSTALLW2KMIGRATIONPACK Testing
C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP\SQLNET .INF for existance
INSTALLW2KMIGRATIONPACK Get the ComponentID
INSTALLW2KMIGRATIONPACK SetupQueryRegisteredOsComponent Failed with Error : 2
**************
Calling function: BackupCatalog
BackupCatalog Result : Backup Catalog directory already exists for this
component.
Entering function: ExecuteInstall()
Parameters:
nDirective = 4
hWnd = 0x0004014C
pwcsInfFile = C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP\SQLODB C.INF
pwcsCabFile = (null)
pwcsSection = DefaultInstall
pwcsExtractPath = C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP
dwSetupFlags = 32
pContext = 0x0012B450
INSTALLW2KMIGRATIONPACK Getting OS Version Info
INSTALLW2KMIGRATIONPACK Testing
C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP\SQLODB C.INF for existance
INSTALLW2KMIGRATIONPACK Get the ComponentID
INSTALLW2KMIGRATIONPACK SetupQueryRegisteredOsComponent Failed with Error : 2
***************
|||Don't know...looks like you have other issues related to the
OS.
-Sue
On Tue, 11 Oct 2005 11:52:03 -0700, "Alton Chinn"
<AltonChinn@.discussions.microsoft.com> wrote:
>HERE ARE THE VARIOUS CALLS TO ExecuteFunction():
>Entering function: CJob::InitializeJobQueues()
>Parameters:
>hHive = 0x80000002
>szRoot = Software\Microsoft\dasetup\jobs
>Exiting function: CJob::InitializeJobQueues()
>Return value: (HRESULT) 0x00000000
>Debug: Loaded string resource: 3. Characters = 21
>Debug: Loaded string resource: 5. Characters = 14
>Calling function: BackupCatalog
>BackupCatalog Result : Backup Catalog directory already exists for this
>component.
>Entering function: ExecuteInstall()
>Parameters:
>nDirective = 4
>hWnd = 0x0004014C
>pwcsInfFile = C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP\MDACXP AK.INF
>pwcsCabFile = (null)
>pwcsSection = DefaultInstall
>pwcsExtractPath = C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP
>dwSetupFlags = 32
>pContext = 0x0012B450
>INSTALLW2KMIGRATIONPACK Getting OS Version Info
>INSTALLW2KMIGRATIONPACK Testing
>C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP\MDACX PAK.INF for existance
>INSTALLW2KMIGRATIONPACK Get the ComponentID
>INSTALLW2KMIGRATIONPACK Setting SysSetup Function Pointers
>INSTALLW2KMIGRATIONPACK HINSTANCE: 1727987712
>INSTALLW2KMIGRATIONPACK SetupRegisterOsComponent ProcAddress: 1728218877
>INSTALLW2KMIGRATIONPACK SetupUnRegisterOsComponent ProcAddress: 1728219747
>INSTALLW2KMIGRATIONPACK SetupQueryRegisteredOsComponent ProcAddress:
>1728220575
>INSTALLW2KMIGRATIONPACK SetupQueryRegisteredOsComponent Failed with Error : 2
>************
>Executing Action: REGTYPELIB
> arg1: 'simpdata.tlb'
> arg2: '(null)'
> args: '"simpdata.tlb"'
> Return HR: 0x0
>Debug: Loaded string resource: 3. Characters = 21
>Debug: Loaded string resource: 5. Characters = 14
>Calling function: BackupCatalog
>BackupCatalog Result : Backup Catalog directory already exists for this
>component.
>Entering function: ExecuteInstall()
>Parameters:
>nDirective = 4
>hWnd = 0x0004014C
>pwcsInfFile = C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP\MSXMLX .inf
>pwcsCabFile = (null)
>pwcsSection = DefaultInstall
>pwcsExtractPath = C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP
>dwSetupFlags = 32
>pContext = 0x0012B450
>INSTALLW2KMIGRATIONPACK Getting OS Version Info
>INSTALLW2KMIGRATIONPACK Testing
>C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP\MSXML X.inf for existance
>INSTALLW2KMIGRATIONPACK Get the ComponentID
>INSTALLW2KMIGRATIONPACK SetupQueryRegisteredOsComponent Failed with Error : 2
>*************
>Calling function: BackupCatalog
>BackupCatalog Result : Backup Catalog directory already exists for this
>component.
>Entering function: ExecuteInstall()
>Parameters:
>nDirective = 4
>hWnd = 0x0004014C
>pwcsInfFile = C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP\SQLXML XP.inf
>pwcsCabFile = (null)
>pwcsSection = DefaultInstall
>pwcsExtractPath = C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP
>dwSetupFlags = 32
>pContext = 0x0012B450
>INSTALLW2KMIGRATIONPACK Getting OS Version Info
>INSTALLW2KMIGRATIONPACK Testing
>C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP\SQLXM LXP.inf for existance
>INSTALLW2KMIGRATIONPACK Get the ComponentID
>INSTALLW2KMIGRATIONPACK SetupQueryRegisteredOsComponent Failed with Error : 2
>*************
>Calling function: BackupCatalog
>BackupCatalog Result : Backup Catalog directory already exists for this
>component.
>Entering function: ExecuteInstall()
>Parameters:
>nDirective = 4
>hWnd = 0x0004014C
>pwcsInfFile = C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP\SQLNET .INF
>pwcsCabFile = (null)
>pwcsSection = DefaultInstall
>pwcsExtractPath = C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP
>dwSetupFlags = 32
>pContext = 0x0012B450
>INSTALLW2KMIGRATIONPACK Getting OS Version Info
>INSTALLW2KMIGRATIONPACK Testing
>C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP\SQLNE T.INF for existance
>INSTALLW2KMIGRATIONPACK Get the ComponentID
>INSTALLW2KMIGRATIONPACK SetupQueryRegisteredOsComponent Failed with Error : 2
>**************
>Calling function: BackupCatalog
>BackupCatalog Result : Backup Catalog directory already exists for this
>component.
>Entering function: ExecuteInstall()
>Parameters:
>nDirective = 4
>hWnd = 0x0004014C
>pwcsInfFile = C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP\SQLODB C.INF
>pwcsCabFile = (null)
>pwcsSection = DefaultInstall
>pwcsExtractPath = C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP
>dwSetupFlags = 32
>pContext = 0x0012B450
>INSTALLW2KMIGRATIONPACK Getting OS Version Info
>INSTALLW2KMIGRATIONPACK Testing
>C:\DOCUME~1\achinn\LOCALS~1\Temp\IXP000.TMP\SQLOD BC.INF for existance
>INSTALLW2KMIGRATIONPACK Get the ComponentID
>INSTALLW2KMIGRATIONPACK SetupQueryRegisteredOsComponent Failed with Error : 2
>***************
>
sqlsql
Showing posts with label workstation. Show all posts
Showing posts with label workstation. Show all posts
Tuesday, March 20, 2012
Monday, March 19, 2012
Connection issue with named instance
Hi all,
Since the replacement of new client workstation I've trouble for connection
of these new machines ot My different SQL Servers. On this configuration we
only speak of client/server connected on the same LAN without any antivirus
enabled.
When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
to my server via for example ODBC and in this case when they browse network
they can't see named instance (only default instance is displayed (port 1433)
!). Next to it if they force the name in the connection string they still
can't connect ot the server, because of the port resolution. My workaround
today is to force the port in the connection string of each client (quite
heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
enable.
I've performed different test of connection (telnet 1433 work, PortQRY
return that 1433 and 1434 are working (but it didn't return all the instances
name), ping OK, tracert ok,...)
Any help would be appreciated, thanks in advance
SylvainCan you please follow below links and let us know if it was helpful for you.
http://sqljunkies.com/How%20To/2E1101E0-D5C1-4DBD-A398-FE485DFA439B.scuk
&
http://support.microsoft.com/default.aspx?scid=kb;en-us;287932
Regards
Surajit
"Sylvain" wrote:
> Hi all,
> Since the replacement of new client workstation I've trouble for connection
> of these new machines ot My different SQL Servers. On this configuration we
> only speak of client/server connected on the same LAN without any antivirus
> enabled.
> When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
> to my server via for example ODBC and in this case when they browse network
> they can't see named instance (only default instance is displayed (port 1433)
> !). Next to it if they force the name in the connection string they still
> can't connect ot the server, because of the port resolution. My workaround
> today is to force the port in the connection string of each client (quite
> heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
> enable.
> I've performed different test of connection (telnet 1433 work, PortQRY
> return that 1433 and 1434 are working (but it didn't return all the instances
> name), ping OK, tracert ok,...)
> Any help would be appreciated, thanks in advance
> Sylvain|||Thanks for your reply.
Concerning the first link, after checking all cases the result is the same
than before, the only workaround is to create an alias (force port number).
All my clients even set on dynamically determine port, can't find an instance
other than the default except if I set manually the expected port by the
server.
For the second link, after checking with my network team we have validate
that no firewall are placed between clients and servers.
Thanks for your help
Sylvain
"surajits" wrote:
> Can you please follow below links and let us know if it was helpful for you.
> http://sqljunkies.com/How%20To/2E1101E0-D5C1-4DBD-A398-FE485DFA439B.scuk
> &
> http://support.microsoft.com/default.aspx?scid=kb;en-us;287932
>
> Regards
> Surajit
>
>
> "Sylvain" wrote:
> > Hi all,
> >
> > Since the replacement of new client workstation I've trouble for connection
> > of these new machines ot My different SQL Servers. On this configuration we
> > only speak of client/server connected on the same LAN without any antivirus
> > enabled.
> > When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
> > to my server via for example ODBC and in this case when they browse network
> > they can't see named instance (only default instance is displayed (port 1433)
> > !). Next to it if they force the name in the connection string they still
> > can't connect ot the server, because of the port resolution. My workaround
> > today is to force the port in the connection string of each client (quite
> > heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
> > enable.
> > I've performed different test of connection (telnet 1433 work, PortQRY
> > return that 1433 and 1434 are working (but it didn't return all the instances
> > name), ping OK, tracert ok,...)
> >
> > Any help would be appreciated, thanks in advance
> > Sylvain
Since the replacement of new client workstation I've trouble for connection
of these new machines ot My different SQL Servers. On this configuration we
only speak of client/server connected on the same LAN without any antivirus
enabled.
When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
to my server via for example ODBC and in this case when they browse network
they can't see named instance (only default instance is displayed (port 1433)
!). Next to it if they force the name in the connection string they still
can't connect ot the server, because of the port resolution. My workaround
today is to force the port in the connection string of each client (quite
heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
enable.
I've performed different test of connection (telnet 1433 work, PortQRY
return that 1433 and 1434 are working (but it didn't return all the instances
name), ping OK, tracert ok,...)
Any help would be appreciated, thanks in advance
SylvainCan you please follow below links and let us know if it was helpful for you.
http://sqljunkies.com/How%20To/2E1101E0-D5C1-4DBD-A398-FE485DFA439B.scuk
&
http://support.microsoft.com/default.aspx?scid=kb;en-us;287932
Regards
Surajit
"Sylvain" wrote:
> Hi all,
> Since the replacement of new client workstation I've trouble for connection
> of these new machines ot My different SQL Servers. On this configuration we
> only speak of client/server connected on the same LAN without any antivirus
> enabled.
> When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
> to my server via for example ODBC and in this case when they browse network
> they can't see named instance (only default instance is displayed (port 1433)
> !). Next to it if they force the name in the connection string they still
> can't connect ot the server, because of the port resolution. My workaround
> today is to force the port in the connection string of each client (quite
> heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
> enable.
> I've performed different test of connection (telnet 1433 work, PortQRY
> return that 1433 and 1434 are working (but it didn't return all the instances
> name), ping OK, tracert ok,...)
> Any help would be appreciated, thanks in advance
> Sylvain|||Thanks for your reply.
Concerning the first link, after checking all cases the result is the same
than before, the only workaround is to create an alias (force port number).
All my clients even set on dynamically determine port, can't find an instance
other than the default except if I set manually the expected port by the
server.
For the second link, after checking with my network team we have validate
that no firewall are placed between clients and servers.
Thanks for your help
Sylvain
"surajits" wrote:
> Can you please follow below links and let us know if it was helpful for you.
> http://sqljunkies.com/How%20To/2E1101E0-D5C1-4DBD-A398-FE485DFA439B.scuk
> &
> http://support.microsoft.com/default.aspx?scid=kb;en-us;287932
>
> Regards
> Surajit
>
>
> "Sylvain" wrote:
> > Hi all,
> >
> > Since the replacement of new client workstation I've trouble for connection
> > of these new machines ot My different SQL Servers. On this configuration we
> > only speak of client/server connected on the same LAN without any antivirus
> > enabled.
> > When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
> > to my server via for example ODBC and in this case when they browse network
> > they can't see named instance (only default instance is displayed (port 1433)
> > !). Next to it if they force the name in the connection string they still
> > can't connect ot the server, because of the port resolution. My workaround
> > today is to force the port in the connection string of each client (quite
> > heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
> > enable.
> > I've performed different test of connection (telnet 1433 work, PortQRY
> > return that 1433 and 1434 are working (but it didn't return all the instances
> > name), ping OK, tracert ok,...)
> >
> > Any help would be appreciated, thanks in advance
> > Sylvain
Connection issue with named instance
Hi all,
Since the replacement of new client workstation I've trouble for connection
of these new machines ot My different SQL Servers. On this configuration we
only speak of client/server connected on the same LAN without any antivirus
enabled.
When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
to my server via for example ODBC and in this case when they browse network
they can't see named instance (only default instance is displayed (port 1433)
!). Next to it if they force the name in the connection string they still
can't connect ot the server, because of the port resolution. My workaround
today is to force the port in the connection string of each client (quite
heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
enable.
I've performed different test of connection (telnet 1433 work, PortQRY
return that 1433 and 1434 are working (but it didn't return all the instances
name), ping OK, tracert ok,...)
Any help would be appreciated, thanks in advance
Sylvain
Can you please follow below links and let us know if it was helpful for you.
http://sqljunkies.com/How%20To/2E110...85DFA439B.scuk
&
http://support.microsoft.com/default...b;en-us;287932
Regards
Surajit
"Sylvain" wrote:
> Hi all,
> Since the replacement of new client workstation I've trouble for connection
> of these new machines ot My different SQL Servers. On this configuration we
> only speak of client/server connected on the same LAN without any antivirus
> enabled.
> When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
> to my server via for example ODBC and in this case when they browse network
> they can't see named instance (only default instance is displayed (port 1433)
> !). Next to it if they force the name in the connection string they still
> can't connect ot the server, because of the port resolution. My workaround
> today is to force the port in the connection string of each client (quite
> heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
> enable.
> I've performed different test of connection (telnet 1433 work, PortQRY
> return that 1433 and 1434 are working (but it didn't return all the instances
> name), ping OK, tracert ok,...)
> Any help would be appreciated, thanks in advance
> Sylvain
|||Thanks for your reply.
Concerning the first link, after checking all cases the result is the same
than before, the only workaround is to create an alias (force port number).
All my clients even set on dynamically determine port, can't find an instance
other than the default except if I set manually the expected port by the
server.
For the second link, after checking with my network team we have validate
that no firewall are placed between clients and servers.
Thanks for your help
Sylvain
"surajits" wrote:
[vbcol=seagreen]
> Can you please follow below links and let us know if it was helpful for you.
> http://sqljunkies.com/How%20To/2E110...85DFA439B.scuk
> &
> http://support.microsoft.com/default...b;en-us;287932
>
> Regards
> Surajit
>
>
> "Sylvain" wrote:
Since the replacement of new client workstation I've trouble for connection
of these new machines ot My different SQL Servers. On this configuration we
only speak of client/server connected on the same LAN without any antivirus
enabled.
When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
to my server via for example ODBC and in this case when they browse network
they can't see named instance (only default instance is displayed (port 1433)
!). Next to it if they force the name in the connection string they still
can't connect ot the server, because of the port resolution. My workaround
today is to force the port in the connection string of each client (quite
heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
enable.
I've performed different test of connection (telnet 1433 work, PortQRY
return that 1433 and 1434 are working (but it didn't return all the instances
name), ping OK, tracert ok,...)
Any help would be appreciated, thanks in advance
Sylvain
Can you please follow below links and let us know if it was helpful for you.
http://sqljunkies.com/How%20To/2E110...85DFA439B.scuk
&
http://support.microsoft.com/default...b;en-us;287932
Regards
Surajit
"Sylvain" wrote:
> Hi all,
> Since the replacement of new client workstation I've trouble for connection
> of these new machines ot My different SQL Servers. On this configuration we
> only speak of client/server connected on the same LAN without any antivirus
> enabled.
> When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
> to my server via for example ODBC and in this case when they browse network
> they can't see named instance (only default instance is displayed (port 1433)
> !). Next to it if they force the name in the connection string they still
> can't connect ot the server, because of the port resolution. My workaround
> today is to force the port in the connection string of each client (quite
> heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
> enable.
> I've performed different test of connection (telnet 1433 work, PortQRY
> return that 1433 and 1434 are working (but it didn't return all the instances
> name), ping OK, tracert ok,...)
> Any help would be appreciated, thanks in advance
> Sylvain
|||Thanks for your reply.
Concerning the first link, after checking all cases the result is the same
than before, the only workaround is to create an alias (force port number).
All my clients even set on dynamically determine port, can't find an instance
other than the default except if I set manually the expected port by the
server.
For the second link, after checking with my network team we have validate
that no firewall are placed between clients and servers.
Thanks for your help
Sylvain
"surajits" wrote:
[vbcol=seagreen]
> Can you please follow below links and let us know if it was helpful for you.
> http://sqljunkies.com/How%20To/2E110...85DFA439B.scuk
> &
> http://support.microsoft.com/default...b;en-us;287932
>
> Regards
> Surajit
>
>
> "Sylvain" wrote:
Connection issue with named instance
Hi all,
Since the replacement of new client workstation I've trouble for connection
of these new machines ot My different SQL Servers. On this configuration we
only speak of client/server connected on the same LAN without any antivirus
enabled.
When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
to my server via for example ODBC and in this case when they browse network
they can't see named instance (only default instance is displayed (port 1433
)
!). Next to it if they force the name in the connection string they still
can't connect ot the server, because of the port resolution. My workaround
today is to force the port in the connection string of each client (quite
heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
enable.
I've performed different test of connection (telnet 1433 work, PortQRY
return that 1433 and 1434 are working (but it didn't return all the instance
s
name), ping OK, tracert ok,...)
Any help would be appreciated, thanks in advance
SylvainCan you please follow below links and let us know if it was helpful for you.
http://sqljunkies.com/How%20To/2E11...485DFA439B.scuk
&
http://support.microsoft.com/defaul...kb;en-us;287932
Regards
Surajit
"Sylvain" wrote:
> Hi all,
> Since the replacement of new client workstation I've trouble for connectio
n
> of these new machines ot My different SQL Servers. On this configuration w
e
> only speak of client/server connected on the same LAN without any antiviru
s
> enabled.
> When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
> to my server via for example ODBC and in this case when they browse networ
k
> they can't see named instance (only default instance is displayed (port 14
33)
> !). Next to it if they force the name in the connection string they still
> can't connect ot the server, because of the port resolution. My workaround
> today is to force the port in the connection string of each client (quite
> heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
> enable.
> I've performed different test of connection (telnet 1433 work, PortQRY
> return that 1433 and 1434 are working (but it didn't return all the instan
ces
> name), ping OK, tracert ok,...)
> Any help would be appreciated, thanks in advance
> Sylvain|||Thanks for your reply.
Concerning the first link, after checking all cases the result is the same
than before, the only workaround is to create an alias (force port number).
All my clients even set on dynamically determine port, can't find an instanc
e
other than the default except if I set manually the expected port by the
server.
For the second link, after checking with my network team we have validate
that no firewall are placed between clients and servers.
Thanks for your help
Sylvain
"surajits" wrote:
[vbcol=seagreen]
> Can you please follow below links and let us know if it was helpful for yo
u.
> http://sqljunkies.com/How%20To/2E11...485DFA439B.scuk
> &
> http://support.microsoft.com/defaul...kb;en-us;287932
>
> Regards
> Surajit
>
>
> "Sylvain" wrote:
>
Since the replacement of new client workstation I've trouble for connection
of these new machines ot My different SQL Servers. On this configuration we
only speak of client/server connected on the same LAN without any antivirus
enabled.
When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
to my server via for example ODBC and in this case when they browse network
they can't see named instance (only default instance is displayed (port 1433
)
!). Next to it if they force the name in the connection string they still
can't connect ot the server, because of the port resolution. My workaround
today is to force the port in the connection string of each client (quite
heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
enable.
I've performed different test of connection (telnet 1433 work, PortQRY
return that 1433 and 1434 are working (but it didn't return all the instance
s
name), ping OK, tracert ok,...)
Any help would be appreciated, thanks in advance
SylvainCan you please follow below links and let us know if it was helpful for you.
http://sqljunkies.com/How%20To/2E11...485DFA439B.scuk
&
http://support.microsoft.com/defaul...kb;en-us;287932
Regards
Surajit
"Sylvain" wrote:
> Hi all,
> Since the replacement of new client workstation I've trouble for connectio
n
> of these new machines ot My different SQL Servers. On this configuration w
e
> only speak of client/server connected on the same LAN without any antiviru
s
> enabled.
> When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
> to my server via for example ODBC and in this case when they browse networ
k
> they can't see named instance (only default instance is displayed (port 14
33)
> !). Next to it if they force the name in the connection string they still
> can't connect ot the server, because of the port resolution. My workaround
> today is to force the port in the connection string of each client (quite
> heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
> enable.
> I've performed different test of connection (telnet 1433 work, PortQRY
> return that 1433 and 1434 are working (but it didn't return all the instan
ces
> name), ping OK, tracert ok,...)
> Any help would be appreciated, thanks in advance
> Sylvain|||Thanks for your reply.
Concerning the first link, after checking all cases the result is the same
than before, the only workaround is to create an alias (force port number).
All my clients even set on dynamically determine port, can't find an instanc
e
other than the default except if I set manually the expected port by the
server.
For the second link, after checking with my network team we have validate
that no firewall are placed between clients and servers.
Thanks for your help
Sylvain
"surajits" wrote:
[vbcol=seagreen]
> Can you please follow below links and let us know if it was helpful for yo
u.
> http://sqljunkies.com/How%20To/2E11...485DFA439B.scuk
> &
> http://support.microsoft.com/defaul...kb;en-us;287932
>
> Regards
> Surajit
>
>
> "Sylvain" wrote:
>
Connection Issue
I am a novice and have SQL 2k5 installed on my server running windows SBS 2003. I am able to connect to the database from my workstation and I am able to view all the fields of the database but I am not able to view any of the records contained in the database. Can someone please guide me. I need to be able to view add and delete records using Access as a front end program to SQL. Thank you.
How are you connecting to the server? What 'client tool' are you using? (Visual Studio, SSMS, QA, etc.)
|||I am connecting to the server via an intranet enviroment and I am logged on with administrator properties.|||The most important thing to note is how you are connecting, like windows Authentication or with a SQL username and password.
If you can connect to the SQL Server and see some of the fields, and schema, then depending on the way you are connecting it could be that the user does not have access to SELECT from the tables.
If you are using Access to connect, you should be able to do what you want to do if you are using the appropriate permissions inside SQL for your tables.
Ben Miller
|||Thank you!
I reset all the ODBC connections and I was able to view the data. Your response was very helpful. Thank you once more.
Wednesday, March 7, 2012
Connection Error SQL Server Error 10060 / 17
Hello,
I have the following error from one workstation connecting to a sql server :
SQL Server Error 10060 [Microsof][ODBCSQL Server Driver][TCP/IP
sockets]Connection Open (Connect())
SQL Server Error 17 [Microsof][ODBCSQL Server Driver][TCP/IP sockets]SQL
Server does not exist or Access Denied.
My Server runs Windows 2003 with SQL Server 2000.
I used to have 4 Windows 2000 workstations connecting to the SQL server,
plus Windows 98 workstations and everything worked fine. Recently, the
server was 'hardened' and since then, two out of the 4 Windows 2000
workstations cannot connect to the SQL Server, giving me the error message
mentioned above. No problem has been experienced on the Windows 98
workstation.
Since only two Windows 2000 workstations (out of 4) are experiencing
problem, I cannot pinpoint the server as being 'faulty', it has to be the
machines but where could the problem lie? Of course, I could not install the
critical update patch (mentioned in this forum) on the workstations since it
is meant for the server and anyway, the server is not really the issue here
since other workstations can connect to the sql server.
I tried installing MDAC 2.8 on the 'faulty' workstations, changed nothing.
Is it a dll issue? a security issue?
Please help, this problem has lasted for nearly three weeks and is a real
handicap for the work.
Thanking you in advanceNanou wrote:
> Hello,
> I have the following error from one workstation connecting to a sql server :
> SQL Server Error 10060 [Microsof][ODBCSQL Server Driver][TCP/IP
> sockets]Connection Open (Connect())
> SQL Server Error 17 [Microsof][ODBCSQL Server Driver][TCP/IP sockets]SQL
> Server does not exist or Access Denied.
> My Server runs Windows 2003 with SQL Server 2000.
> I used to have 4 Windows 2000 workstations connecting to the SQL server,
> plus Windows 98 workstations and everything worked fine. Recently, the
> server was 'hardened' and since then, two out of the 4 Windows 2000
How was the server "hardened"? Was a firewall rule established that is
only allowing the two workstations to connect? Was TCP/IP disabled?|||Thanks Tracy for your answer.
Yes a firewall is established but, no there is no limitation in the number
of workstations connecting to the server. TCP/IP is enabled.
Actually, I found the solution to the problem on the net itself. It seems
this connection problem can occur after a firewall is put into place.
http://www.dbforums.com/printthread.php?t=976301
The fix that worked was to delete the entry for the SQL Server in the
following registry location:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ Client\ConnectTo\DSQUERY
See http://support.microsoft.com/default.aspx?kbid=328306
cheers,
nanou
"Tracy McKibben" wrote:
> Nanou wrote:
> > Hello,
> >
> > I have the following error from one workstation connecting to a sql server :
> > SQL Server Error 10060 [Microsof][ODBCSQL Server Driver][TCP/IP
> > sockets]Connection Open (Connect())
> > SQL Server Error 17 [Microsof][ODBCSQL Server Driver][TCP/IP sockets]SQL
> > Server does not exist or Access Denied.
> >
> > My Server runs Windows 2003 with SQL Server 2000.
> >
> > I used to have 4 Windows 2000 workstations connecting to the SQL server,
> > plus Windows 98 workstations and everything worked fine. Recently, the
> > server was 'hardened' and since then, two out of the 4 Windows 2000
> How was the server "hardened"? Was a firewall rule established that is
> only allowing the two workstations to connect? Was TCP/IP disabled?
>
I have the following error from one workstation connecting to a sql server :
SQL Server Error 10060 [Microsof][ODBCSQL Server Driver][TCP/IP
sockets]Connection Open (Connect())
SQL Server Error 17 [Microsof][ODBCSQL Server Driver][TCP/IP sockets]SQL
Server does not exist or Access Denied.
My Server runs Windows 2003 with SQL Server 2000.
I used to have 4 Windows 2000 workstations connecting to the SQL server,
plus Windows 98 workstations and everything worked fine. Recently, the
server was 'hardened' and since then, two out of the 4 Windows 2000
workstations cannot connect to the SQL Server, giving me the error message
mentioned above. No problem has been experienced on the Windows 98
workstation.
Since only two Windows 2000 workstations (out of 4) are experiencing
problem, I cannot pinpoint the server as being 'faulty', it has to be the
machines but where could the problem lie? Of course, I could not install the
critical update patch (mentioned in this forum) on the workstations since it
is meant for the server and anyway, the server is not really the issue here
since other workstations can connect to the sql server.
I tried installing MDAC 2.8 on the 'faulty' workstations, changed nothing.
Is it a dll issue? a security issue?
Please help, this problem has lasted for nearly three weeks and is a real
handicap for the work.
Thanking you in advanceNanou wrote:
> Hello,
> I have the following error from one workstation connecting to a sql server :
> SQL Server Error 10060 [Microsof][ODBCSQL Server Driver][TCP/IP
> sockets]Connection Open (Connect())
> SQL Server Error 17 [Microsof][ODBCSQL Server Driver][TCP/IP sockets]SQL
> Server does not exist or Access Denied.
> My Server runs Windows 2003 with SQL Server 2000.
> I used to have 4 Windows 2000 workstations connecting to the SQL server,
> plus Windows 98 workstations and everything worked fine. Recently, the
> server was 'hardened' and since then, two out of the 4 Windows 2000
How was the server "hardened"? Was a firewall rule established that is
only allowing the two workstations to connect? Was TCP/IP disabled?|||Thanks Tracy for your answer.
Yes a firewall is established but, no there is no limitation in the number
of workstations connecting to the server. TCP/IP is enabled.
Actually, I found the solution to the problem on the net itself. It seems
this connection problem can occur after a firewall is put into place.
http://www.dbforums.com/printthread.php?t=976301
The fix that worked was to delete the entry for the SQL Server in the
following registry location:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ Client\ConnectTo\DSQUERY
See http://support.microsoft.com/default.aspx?kbid=328306
cheers,
nanou
"Tracy McKibben" wrote:
> Nanou wrote:
> > Hello,
> >
> > I have the following error from one workstation connecting to a sql server :
> > SQL Server Error 10060 [Microsof][ODBCSQL Server Driver][TCP/IP
> > sockets]Connection Open (Connect())
> > SQL Server Error 17 [Microsof][ODBCSQL Server Driver][TCP/IP sockets]SQL
> > Server does not exist or Access Denied.
> >
> > My Server runs Windows 2003 with SQL Server 2000.
> >
> > I used to have 4 Windows 2000 workstations connecting to the SQL server,
> > plus Windows 98 workstations and everything worked fine. Recently, the
> > server was 'hardened' and since then, two out of the 4 Windows 2000
> How was the server "hardened"? Was a firewall rule established that is
> only allowing the two workstations to connect? Was TCP/IP disabled?
>
Connection Error SQL Server Error 10060 / 17
Hello,
I have the following error from one workstation connecting to a sql server :
SQL Server Error 10060 [Microsof][ODBCSQL Server Driver][TCP/IP
sockets]Connection Open (Connect())
SQL Server Error 17 [Microsof][ODBCSQL Server Driver][TCP/IP soc
kets]SQL
Server does not exist or Access Denied.
My Server runs Windows 2003 with SQL Server 2000.
I used to have 4 Windows 2000 workstations connecting to the SQL server,
plus Windows 98 workstations and everything worked fine. Recently, the
server was 'hardened' and since then, two out of the 4 Windows 2000
workstations cannot connect to the SQL Server, giving me the error message
mentioned above. No problem has been experienced on the Windows 98
workstation.
Since only two Windows 2000 workstations (out of 4) are experiencing
problem, I cannot pinpoint the server as being 'faulty', it has to be the
machines but where could the problem lie? Of course, I could not install the
critical update patch (mentioned in this forum) on the workstations since it
is meant for the server and anyway, the server is not really the issue here
since other workstations can connect to the sql server.
I tried installing MDAC 2.8 on the 'faulty' workstations, changed nothing.
Is it a dll issue? a security issue?
Please help, this problem has lasted for nearly three weeks and is a real
handicap for the work.
Thanking you in advanceNanou wrote:
> Hello,
> I have the following error from one workstation connecting to a sql server
:
> SQL Server Error 10060 [Microsof][ODBCSQL Server Driver][TCP/I
P
> sockets]Connection Open (Connect())
> SQL Server Error 17 [Microsof][ODBCSQL Server Driver][TCP/IP s
ockets]SQL
> Server does not exist or Access Denied.
> My Server runs Windows 2003 with SQL Server 2000.
> I used to have 4 Windows 2000 workstations connecting to the SQL server,
> plus Windows 98 workstations and everything worked fine. Recently, the
> server was 'hardened' and since then, two out of the 4 Windows 2000
How was the server "hardened"? Was a firewall rule established that is
only allowing the two workstations to connect? Was TCP/IP disabled?|||Nanou wrote:
> Hello,
> I have the following error from one workstation connecting to a sql server
:
> SQL Server Error 10060 [Microsof][ODBCSQL Server Driver][TCP/I
P
> sockets]Connection Open (Connect())
> SQL Server Error 17 [Microsof][ODBCSQL Server Driver][TCP/IP s
ockets]SQL
> Server does not exist or Access Denied.
> My Server runs Windows 2003 with SQL Server 2000.
> I used to have 4 Windows 2000 workstations connecting to the SQL server,
> plus Windows 98 workstations and everything worked fine. Recently, the
> server was 'hardened' and since then, two out of the 4 Windows 2000
How was the server "hardened"? Was a firewall rule established that is
only allowing the two workstations to connect? Was TCP/IP disabled?|||Thanks Tracy for your answer.
Yes a firewall is established but, no there is no limitation in the number
of workstations connecting to the server. TCP/IP is enabled.
Actually, I found the solution to the problem on the net itself. It seems
this connection problem can occur after a firewall is put into place.
http://www.webservertalk.com/printthread.php?t=976301
The fix that worked was to delete the entry for the SQL Server in the
following registry location:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\ Client\ConnectTo\DSQUERY
See http://support.microsoft.com/default.aspx?kbid=328306
cheers,
nanou
"Tracy McKibben" wrote:
> Nanou wrote:
> How was the server "hardened"? Was a firewall rule established that is
> only allowing the two workstations to connect? Was TCP/IP disabled?
>
I have the following error from one workstation connecting to a sql server :
SQL Server Error 10060 [Microsof][ODBCSQL Server Driver][TCP/IP
sockets]Connection Open (Connect())
SQL Server Error 17 [Microsof][ODBCSQL Server Driver][TCP/IP soc
kets]SQL
Server does not exist or Access Denied.
My Server runs Windows 2003 with SQL Server 2000.
I used to have 4 Windows 2000 workstations connecting to the SQL server,
plus Windows 98 workstations and everything worked fine. Recently, the
server was 'hardened' and since then, two out of the 4 Windows 2000
workstations cannot connect to the SQL Server, giving me the error message
mentioned above. No problem has been experienced on the Windows 98
workstation.
Since only two Windows 2000 workstations (out of 4) are experiencing
problem, I cannot pinpoint the server as being 'faulty', it has to be the
machines but where could the problem lie? Of course, I could not install the
critical update patch (mentioned in this forum) on the workstations since it
is meant for the server and anyway, the server is not really the issue here
since other workstations can connect to the sql server.
I tried installing MDAC 2.8 on the 'faulty' workstations, changed nothing.
Is it a dll issue? a security issue?
Please help, this problem has lasted for nearly three weeks and is a real
handicap for the work.
Thanking you in advanceNanou wrote:
> Hello,
> I have the following error from one workstation connecting to a sql server
:
> SQL Server Error 10060 [Microsof][ODBCSQL Server Driver][TCP/I
P
> sockets]Connection Open (Connect())
> SQL Server Error 17 [Microsof][ODBCSQL Server Driver][TCP/IP s
ockets]SQL
> Server does not exist or Access Denied.
> My Server runs Windows 2003 with SQL Server 2000.
> I used to have 4 Windows 2000 workstations connecting to the SQL server,
> plus Windows 98 workstations and everything worked fine. Recently, the
> server was 'hardened' and since then, two out of the 4 Windows 2000
How was the server "hardened"? Was a firewall rule established that is
only allowing the two workstations to connect? Was TCP/IP disabled?|||Nanou wrote:
> Hello,
> I have the following error from one workstation connecting to a sql server
:
> SQL Server Error 10060 [Microsof][ODBCSQL Server Driver][TCP/I
P
> sockets]Connection Open (Connect())
> SQL Server Error 17 [Microsof][ODBCSQL Server Driver][TCP/IP s
ockets]SQL
> Server does not exist or Access Denied.
> My Server runs Windows 2003 with SQL Server 2000.
> I used to have 4 Windows 2000 workstations connecting to the SQL server,
> plus Windows 98 workstations and everything worked fine. Recently, the
> server was 'hardened' and since then, two out of the 4 Windows 2000
How was the server "hardened"? Was a firewall rule established that is
only allowing the two workstations to connect? Was TCP/IP disabled?|||Thanks Tracy for your answer.
Yes a firewall is established but, no there is no limitation in the number
of workstations connecting to the server. TCP/IP is enabled.
Actually, I found the solution to the problem on the net itself. It seems
this connection problem can occur after a firewall is put into place.
http://www.webservertalk.com/printthread.php?t=976301
The fix that worked was to delete the entry for the SQL Server in the
following registry location:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\ Client\ConnectTo\DSQUERY
See http://support.microsoft.com/default.aspx?kbid=328306
cheers,
nanou
"Tracy McKibben" wrote:
> Nanou wrote:
> How was the server "hardened"? Was a firewall rule established that is
> only allowing the two workstations to connect? Was TCP/IP disabled?
>
Saturday, February 25, 2012
Connection Error
What the problem of this error. For information, please check code as below,
ProtectedConst SQL_CONNECTION_STRINGAsString = "workstation id=LOCALHOST; size=4096;integrated security=SSPI;initial catalog=VIVAM;persist security info=False;User ID=sa"
below is the error command
Login failed for user 'BST-FAIROZ\ASPNET'.
Description:An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details:System.Data.SqlClient.SqlException: Login failed for user 'BST-FAIROZ\ASPNET'.
Subscribe to:
Posts (Atom)