Hello, my VB app fails to connects to a SQL Server.
Server side info
SQL Server is installed in a W2000 PC configured for IIS use. It is not a PDC.
Client side info
W2000, no Access app installed.
Situation:
System DSN created with ODBC config utility works fine and connects succesfully to the server. But when a connection is tried to be made through app it fail: "Login failed, ... user(null)... Not associated with a trusted SQL Server connection"
Any suggestions ?
Thanks
Arnaldo
Arnaldo,
See if this helps
'PRB: ASP/ODBC/SQL Server Error 0x80040E4D "Login Failed for User '(Null)'"'
http://support.microsoft.com/?id=307002
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"Arnaldo" <anonymous@.discussions.microsoft.com> wrote in message
news:ADBEE679-C4F6-486C-96CB-1588892D7283@.microsoft.com...
> Hello, my VB app fails to connects to a SQL Server.
> Server side info
> SQL Server is installed in a W2000 PC configured for IIS use. It is not a
PDC.
> Client side info
> W2000, no Access app installed.
> Situation:
> System DSN created with ODBC config utility works fine and connects
succesfully to the server. But when a connection is tried to be made through
app it fail: "Login failed, ... user(null)... Not associated with a trusted
SQL Server connection"
> Any suggestions ?
> Thanks
> Arnaldo
>
>
>
Showing posts with label configured. Show all posts
Showing posts with label configured. Show all posts
Friday, March 23, 2012
ODBC Connection SQL Server Error
Hello, my VB app fails to connects to a SQL Server.
Server side info
SQL Server is installed in a W2000 PC configured for IIS use. It is not a PD
C.
Client side info
W2000, no Access app installed.
Situation:
System DSN created with ODBC config utility works fine and connects succesfu
lly to the server. But when a connection is tried to be made through app it
fail: "Login failed, ... user(null)... Not associated with a trusted SQL Ser
ver connection"
Any suggestions ?
Thanks
ArnaldoArnaldo,
See if this helps
'PRB: ASP/ODBC/SQL Server Error 0x80040E4D "Login Failed for User '(Null)'"'
http://support.microsoft.com/?id=307002
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Arnaldo" <anonymous@.discussions.microsoft.com> wrote in message
news:ADBEE679-C4F6-486C-96CB-1588892D7283@.microsoft.com...
> Hello, my VB app fails to connects to a SQL Server.
> Server side info
> SQL Server is installed in a W2000 PC configured for IIS use. It is not a
PDC.
> Client side info
> W2000, no Access app installed.
> Situation:
> System DSN created with ODBC config utility works fine and connects
succesfully to the server. But when a connection is tried to be made through
app it fail: "Login failed, ... user(null)... Not associated with a trusted
SQL Server connection"
> Any suggestions ?
> Thanks
> Arnaldo
>
>
>
Server side info
SQL Server is installed in a W2000 PC configured for IIS use. It is not a PD
C.
Client side info
W2000, no Access app installed.
Situation:
System DSN created with ODBC config utility works fine and connects succesfu
lly to the server. But when a connection is tried to be made through app it
fail: "Login failed, ... user(null)... Not associated with a trusted SQL Ser
ver connection"
Any suggestions ?
Thanks
ArnaldoArnaldo,
See if this helps
'PRB: ASP/ODBC/SQL Server Error 0x80040E4D "Login Failed for User '(Null)'"'
http://support.microsoft.com/?id=307002
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Arnaldo" <anonymous@.discussions.microsoft.com> wrote in message
news:ADBEE679-C4F6-486C-96CB-1588892D7283@.microsoft.com...
> Hello, my VB app fails to connects to a SQL Server.
> Server side info
> SQL Server is installed in a W2000 PC configured for IIS use. It is not a
PDC.
> Client side info
> W2000, no Access app installed.
> Situation:
> System DSN created with ODBC config utility works fine and connects
succesfully to the server. But when a connection is tried to be made through
app it fail: "Login failed, ... user(null)... Not associated with a trusted
SQL Server connection"
> Any suggestions ?
> Thanks
> Arnaldo
>
>
>
Monday, March 19, 2012
ODBC changes at random...help
Hi All,
Strange thing going on here.....I have an application that uses 2 ODBC
connections, 1 for SQL and 1 for an Access Database. They are configured as
System ODBCs that connect to the databases through a mapped drive to the
server. Everything works fine on all users except 4 of them....whose ODBC
for the Access database will randomly (maybe once a month or less) change
from the one mapped drive to another...where there is no database. 3 of
these users are running XP pro and the other is running Win 2000.
I have deleted the ODBCs and recreated them, disconnected the drives and
re-mapped them....it still does it periodically.
Any idea why this is happening and how to stop it?
Thanks!!
Troubleshooting random events that you can't repro is very difficult.
I'd suggest getting rid of the DSNs you are using and connect
programmatically by supplying the ODBC connection string information
in code when the user connects. You can get the syntax for valid ODBC
connection strings for both Access and SQL Server at
http://able-consulting.com/ADO_Conn.htm and
http://www.connectionstrings.com. DSN's are notoriously difficult to
support and troubleshoot.
--Mary
On Wed, 23 Feb 2005 11:32:40 -0700, "Dan B" <none@.none.com> wrote:
>Hi All,
>Strange thing going on here.....I have an application that uses 2 ODBC
>connections, 1 for SQL and 1 for an Access Database. They are configured as
>System ODBCs that connect to the databases through a mapped drive to the
>server. Everything works fine on all users except 4 of them....whose ODBC
>for the Access database will randomly (maybe once a month or less) change
>from the one mapped drive to another...where there is no database. 3 of
>these users are running XP pro and the other is running Win 2000.
>I have deleted the ODBCs and recreated them, disconnected the drives and
>re-mapped them....it still does it periodically.
>Any idea why this is happening and how to stop it?
>Thanks!!
>
Strange thing going on here.....I have an application that uses 2 ODBC
connections, 1 for SQL and 1 for an Access Database. They are configured as
System ODBCs that connect to the databases through a mapped drive to the
server. Everything works fine on all users except 4 of them....whose ODBC
for the Access database will randomly (maybe once a month or less) change
from the one mapped drive to another...where there is no database. 3 of
these users are running XP pro and the other is running Win 2000.
I have deleted the ODBCs and recreated them, disconnected the drives and
re-mapped them....it still does it periodically.
Any idea why this is happening and how to stop it?
Thanks!!
Troubleshooting random events that you can't repro is very difficult.
I'd suggest getting rid of the DSNs you are using and connect
programmatically by supplying the ODBC connection string information
in code when the user connects. You can get the syntax for valid ODBC
connection strings for both Access and SQL Server at
http://able-consulting.com/ADO_Conn.htm and
http://www.connectionstrings.com. DSN's are notoriously difficult to
support and troubleshoot.
--Mary
On Wed, 23 Feb 2005 11:32:40 -0700, "Dan B" <none@.none.com> wrote:
>Hi All,
>Strange thing going on here.....I have an application that uses 2 ODBC
>connections, 1 for SQL and 1 for an Access Database. They are configured as
>System ODBCs that connect to the databases through a mapped drive to the
>server. Everything works fine on all users except 4 of them....whose ODBC
>for the Access database will randomly (maybe once a month or less) change
>from the one mapped drive to another...where there is no database. 3 of
>these users are running XP pro and the other is running Win 2000.
>I have deleted the ODBCs and recreated them, disconnected the drives and
>re-mapped them....it still does it periodically.
>Any idea why this is happening and how to stop it?
>Thanks!!
>
ODBC changes at random...help
Hi All,
Strange thing going on here.....I have an application that uses 2 ODBC
connections, 1 for SQL and 1 for an Access Database. They are configured as
System ODBCs that connect to the databases through a mapped drive to the
server. Everything works fine on all users except 4 of them....whose ODBC
for the Access database will randomly (maybe once a month or less) change
from the one mapped drive to another...where there is no database. 3 of
these users are running XP pro and the other is running Win 2000.
I have deleted the ODBCs and recreated them, disconnected the drives and
re-mapped them....it still does it periodically.
Any idea why this is happening and how to stop it?
Thanks!!Troubleshooting random events that you can't repro is very difficult.
I'd suggest getting rid of the DSNs you are using and connect
programmatically by supplying the ODBC connection string information
in code when the user connects. You can get the syntax for valid ODBC
connection strings for both Access and SQL Server at
http://able-consulting.com/ADO_Conn.htm and
http://www.connectionstrings.com. DSN's are notoriously difficult to
support and troubleshoot.
--Mary
On Wed, 23 Feb 2005 11:32:40 -0700, "Dan B" <none@.none.com> wrote:
>Hi All,
>Strange thing going on here.....I have an application that uses 2 ODBC
>connections, 1 for SQL and 1 for an Access Database. They are configured a
s
>System ODBCs that connect to the databases through a mapped drive to the
>server. Everything works fine on all users except 4 of them....whose ODBC
>for the Access database will randomly (maybe once a month or less) change
>from the one mapped drive to another...where there is no database. 3 of
>these users are running XP pro and the other is running Win 2000.
>I have deleted the ODBCs and recreated them, disconnected the drives and
>re-mapped them....it still does it periodically.
>Any idea why this is happening and how to stop it?
>Thanks!!
>
Strange thing going on here.....I have an application that uses 2 ODBC
connections, 1 for SQL and 1 for an Access Database. They are configured as
System ODBCs that connect to the databases through a mapped drive to the
server. Everything works fine on all users except 4 of them....whose ODBC
for the Access database will randomly (maybe once a month or less) change
from the one mapped drive to another...where there is no database. 3 of
these users are running XP pro and the other is running Win 2000.
I have deleted the ODBCs and recreated them, disconnected the drives and
re-mapped them....it still does it periodically.
Any idea why this is happening and how to stop it?
Thanks!!Troubleshooting random events that you can't repro is very difficult.
I'd suggest getting rid of the DSNs you are using and connect
programmatically by supplying the ODBC connection string information
in code when the user connects. You can get the syntax for valid ODBC
connection strings for both Access and SQL Server at
http://able-consulting.com/ADO_Conn.htm and
http://www.connectionstrings.com. DSN's are notoriously difficult to
support and troubleshoot.
--Mary
On Wed, 23 Feb 2005 11:32:40 -0700, "Dan B" <none@.none.com> wrote:
>Hi All,
>Strange thing going on here.....I have an application that uses 2 ODBC
>connections, 1 for SQL and 1 for an Access Database. They are configured a
s
>System ODBCs that connect to the databases through a mapped drive to the
>server. Everything works fine on all users except 4 of them....whose ODBC
>for the Access database will randomly (maybe once a month or less) change
>from the one mapped drive to another...where there is no database. 3 of
>these users are running XP pro and the other is running Win 2000.
>I have deleted the ODBCs and recreated them, disconnected the drives and
>re-mapped them....it still does it periodically.
>Any idea why this is happening and how to stop it?
>Thanks!!
>
Monday, March 12, 2012
ODBC - System DSN window is blank
We've run into a few XP machines in our organization that have some interesting quirk going on. We have several ODBC connections configured on the machines. However, when you go to ODBC connections, then click on the System DSN tab, it's empty. If we try to manually create a "missing" odbc, it says it already exists, do you want to overwrite, etc. We say yes, but it still doesn't appear. The main program being used has a dropdown box at the login screen that shows the various ODBC names to choose from. The ones from the System DSN tab (which is blank anyway) are not listed. However, if you manually type in the name of the ODBC that is supposedly configured but doesn't show up, it works. So, it sees the ODBC, but it won't display it to the human eye in the settings or drop down lists. What's up with that? We've tried reinstalling MDAC, java, windows updates, etc, etc. Only some machines are affected. I am unable to tell you what's been done to all these machines. The users are all set as admins on their machines. They all run similar software, etc. The only thing that happened around the time we started noticing this is that we added a couple new ODBCs and changed the settings in an existing one. We sent an exe to all users in the organization that auto configures these ODBC's so we don't have to do it manually. It works awesome, but I don't see how that exe could have caused this problem especially when the problem seems to have only shown up on about 1% of the PCs it was applied to.Found this at: http://www.dbforums.com/t1055278.html
01-01-05, 01:37
wconner50
Registered User
Join Date: Jan 2005
Posts: 2
System DSN not in ODBC Manager
You should export the registry entries for the ODBC.INI Data source and DataSet Names. Then edit the .reg exported file and see if there are any odd lines of text. I found a corrupt entry in the ODBC Data Source registry entry, all the missing system DSN's were right after the corrupt line. Delete corrupt line and deleted ODBC Data Source registry entry, then imported .reg file.
Problem was resolved.
01-01-05, 01:37
wconner50
Registered User
Join Date: Jan 2005
Posts: 2
System DSN not in ODBC Manager
You should export the registry entries for the ODBC.INI Data source and DataSet Names. Then edit the .reg exported file and see if there are any odd lines of text. I found a corrupt entry in the ODBC Data Source registry entry, all the missing system DSN's were right after the corrupt line. Delete corrupt line and deleted ODBC Data Source registry entry, then imported .reg file.
Problem was resolved.
Subscribe to:
Posts (Atom)