We have distributed a VB6 application to windows 95 clients. It uses ADO and ODBC to connect to the SQL server. An intermittant error is occurring, -2147467259 [DBNMPNTW] Specified SQL Server not found. All users are on a fast link to the network (2mgbits). The application uses disconnected recordsets so is closing the ADO Connection and then reopening, it does not release the Connection object. Any ideas please?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
VB6 app on client unable to find SQL Server
- Thread starter susanma
- Start date
-- Integrated security error occurs because SQL Server cannot find a SQL Server account for the NT account.
Solution: To resolve this problem, check the NT account trying to access the database and make sure it maps to the correct SQL Server account.
If the mapping is okay, check the account name and make sure the SQL Server account is a valid account. For example, SQL Server does not allow the same characters in account names that NT does. If you map the NT account IUSR_Server1 to the SQL Server IUSR_Server1account, users cannot log on because the underscore is not a valid character in a SQL Server account name.
-- Make sure Integrated security is turned off.
To make sure that SQL Server does not use Integrated security, set its security option to Standard. The following steps demonstrate how to make this change for SQL Server 6.5.
To change SQL Server to use Standard security,
Start SQL Server Setup from the SQL Server folder on the Programs menu.
Click Continue until the Microsoft SQL Server Options dialog box is shown.
Click the Set Security Options option button.
Click Continue.
Click the Standard entry.
Click OK.
Continue through the remaining screens, accepting the defaults.
Solution: To resolve this problem, check the NT account trying to access the database and make sure it maps to the correct SQL Server account.
If the mapping is okay, check the account name and make sure the SQL Server account is a valid account. For example, SQL Server does not allow the same characters in account names that NT does. If you map the NT account IUSR_Server1 to the SQL Server IUSR_Server1account, users cannot log on because the underscore is not a valid character in a SQL Server account name.
-- Make sure Integrated security is turned off.
To make sure that SQL Server does not use Integrated security, set its security option to Standard. The following steps demonstrate how to make this change for SQL Server 6.5.
To change SQL Server to use Standard security,
Start SQL Server Setup from the SQL Server folder on the Programs menu.
Click Continue until the Microsoft SQL Server Options dialog box is shown.
Click the Set Security Options option button.
Click Continue.
Click the Standard entry.
Click OK.
Continue through the remaining screens, accepting the defaults.
- Thread starter
- #3
Many thanks for your quick response, but we want to use integrated security and we know that the users can logon because sometimes it works! This error is occurring intermitantly for specific users who have been able to logon to the application and perform other tasks requiring a connection to the database. It may then occur when they try to perform a search function which would open the connection again.
I have seen this problem, but unfortunately I don't remember the resolution. But, it was not resolved by eliminating integrated security.
What version of SQL Server are you using?
I would make sure you have the latest service packs for VB6 and SQL Server, which should give you the latest version of MDAC also.
Also, check for these files, which sometimes don't get installed by PDW(Check that your users have correct version):
DBNETLIB.dll For SQL Server 2000
NTWDBLIB.dll For SQL Server 7
What version of SQL Server are you using?
I would make sure you have the latest service packs for VB6 and SQL Server, which should give you the latest version of MDAC also.
Also, check for these files, which sometimes don't get installed by PDW(Check that your users have correct version):
DBNETLIB.dll For SQL Server 2000
NTWDBLIB.dll For SQL Server 7
- Status
Similar threads
- Question
- Locked
- Question
