Thursday, March 22, 2012
Cannot open user default database. User login failed.
I'm sorry if this is simple, I'm no DBA but have been tasked with solving this problem...
We have a website that connects via ODBC to SQL Server (2k sp1) and at the moment I am getting back about every other time:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open user default database. Login failed.
So this is NOT happening every single time. Now I have seen Microsoft KB - 307864 and I can see that none of the databases are marked as suspect, the database I am trying to connect to does exist and is attached and, I have run the command to switch the database to multi-user mode.
The probable cause of this problem is that a while ago we had a hard-drive failure and I was forced to reattach some old datafiles (mdf,ldf) as the database. This seemed ok and I can view data etc in enterprise manager no problem.
I have checked for orphaned users and the user I am logging in with from the webpage is not listed.
So does anyone have a clue as to why this is happening, and more frustratingly for me, why is it only happening some of the time.
Thanks for your help, appreciated.
James.Edit your odbc connection and check the default database drop down box...it's probably set to master...|||Brett - Thanks for posting.
Have checked the ODBC settings and the database is not set to master as default .|||Originally posted by JDMoore
Brett - Thanks for posting.
Have checked the ODBC settings and the database is not set to master as default .
What ODBC says if you are trying to test data source under this account?
If everything is fine with ODBC - check your application...|||ODBC says that the connection is fine.
The application has not been changed and has worked fine so I'm virtually certainly it's nothing to do with the program code. The code in question is simply opening a connection to the database.
As I say the error is sporadic presumably an ODBC connection string can either be right or wrong?|||Remotely, but possible, that the default database is in single user mode, and if you login successfully, it means that you're the first one to show up, while when you get an error, then someone's already there (that's to attempt to explain the sporadic nature of the error.) But to be proactive, open EM and go to that database (make sure to register the server with sysadmin privileges.) Check the Options tab of the properties to ensure that the database is not in single user mode. Also, go to Security folder, then to Logins and open properties for the account that the app uses to login and set the default database to master. This is to prevent the situation when a different database was renamed to the one that is specified now as default. And finally, speaking about renamed databases, can you check if it happened recently?|||You might also want to check the connection type in the ODBC. There are times when it doesn't matter whether your using Pipes or Ip but it will test just fine then throw sporadic error messages when actually using the application.
I would try going into the client config button (2nd screen in the ODBC) and if it's set to Pipes then make it IP (port 1433 is default but may have to be changed depending on network) or vice versa.|||Run sql profiler to see what logins are attempting to connect - I am curious to see if the problem is that the iuser account is failing to connect ...|||Thanks for all the suggestions. I am not in until Monday now but when I get in, I will try everything and then get back to you all.
Thanks for posting.|||As always it turned out to be pretty simple...
As I looked further through the code it turned out that the program was looking at this database and then looking at a database on a different server.
When I went to the other server it turned out that THIS database was in single-user mode and hence the sporadic nature of the problem was explained.
Thanks very much for everyone's contribution, probably wouldn't have stumbled over this for ages without your suggestions.
James.
Sunday, March 11, 2012
Cannot make ODBC connection to SQL Express 05 Server from Win 2000 Server
ODBC connection to a new SQL Express 2005 server running on Windows Server
2003. Using every logical combination I can think of I cannot make an ODBC
connection from this web server. I've tried this from another server on the
same subnet also running Windows Server 2003 and it connects fine. I can
even make an ODBC connection from my workstation located in a different
subnet. Just not the web server. I get the following error:
Connection failed:
SQLState: '01000'
SQL Server Error: 11004
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpe
n
(gethostbyname()())
Connection failed:
SQLState: '08001'
SQL Server Error: 11
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General netwo
rk error.
Check your network documentation.
I'm specifying the correct port and as far as the network I can connect from
either server to either server via My Network Places so I know the
IP/Subnet/gateway is correct. What's wrong here? Can anyone please provide
some insight on where to look for a solution?
Thanks!"Hiltie" <hiltie@.newasgroups.nospam> wrote in message
news:e1lV8pspGHA.4268@.TK2MSFTNGP04.phx.gbl...
> I've got a web server running Windows 2000 Server that I need to make an
> ODBC connection to a new SQL Express 2005 server running on Windows Server
> 2003. Using every logical combination I can think of I cannot make an ODBC
> connection from this web server. I've tried this from another server on
> the same subnet also running Windows Server 2003 and it connects fine. I
> can even make an ODBC connection from my workstation located in a
> different subnet. Just not the web server. I get the following error:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 11004
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionO
pen
> (gethostbyname()())
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 11
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General net
work error.
> Check your network documentation.
> I'm specifying the correct port and as far as the network I can connect
> from either server to either server via My Network Places so I know the
> IP/Subnet/gateway is correct. What's wrong here? Can anyone please provide
> some insight on where to look for a solution?
BTW, I am able to make a successful telnet connection from the web server to
the SQL Express server, but I cannot make a successful ODBC connection using
the correct port.
Help!|||UPDATE:
I was able to resolve the problem. Thanks anyway.
"Hiltie" <hiltie@.newasgroups.nospam> wrote in message
news:eOW3MV0pGHA.4932@.TK2MSFTNGP05.phx.gbl...
> "Hiltie" <hiltie@.newasgroups.nospam> wrote in message
> news:e1lV8pspGHA.4268@.TK2MSFTNGP04.phx.gbl...
> BTW, I am able to make a successful telnet connection from the web server
> to the SQL Express server, but I cannot make a successful ODBC connection
> using the correct port.
> Help!
>
Thursday, March 8, 2012
Cannot link to SQL tables using ODBC Link table in Access 2003
When trying to link to an SQL table in Access 2003, the software appears to be malfunctioning.
The sequence of events is File - Get External Data - Link Tables - Files of Type: ODBC Databases().
The Problem: On two of my computers, the select data source window does not pop up, preventing me from linking to any ODBC data source.
Observations: This function has worked normally in the recent past and works on other computers running Access 2003. One difference between the computers working and non-working computers is Norton Antivirus 2006 (recent upgrade).
Has anyone experienced anything like this? What's going on?
Yes, I have the same problem and also installed Norton Anti-Virus 2006 recently. My OS is Windows XP Pro SP2. On another PC, where the only difference is that it has Access 2002, the problem does not occur and the dialog box comes up normally. I have floated this question on the UK AUG list processor and the first reply is that there is a Microsoft KB article on it, but my inter locutor does not know its number! Have you askled Norton?|||Here is the solution, from a member of UK AUG.
Alan, you’re a genius; the cure works perfectly.
Catherine, thank you too; I had noticed that Access especially was slow to open, but had no idea why.
Andy Couch, this may come in hand for your next SQL Server course as you may have a Norton victim among your trainees.
I’ll let my Norton 5-user subscription run out and them I’m in the market for something else - anything but Norton.
Timothy Coe.
-
That option scans all Office documents before opening it, but if you have autoprotect on, there shouldn't be any viruses on them in the first place...Regards, Catherine.
-
Timothy,
Downgraded is the correct word! It is awfully slow and my Office documents take ages to open now. I downgraded from Norton Internet Security 2005, which ran reasonably well, to 2006.
Thank you for bringing this up. Now you have, it reminds me that I've posted before on problems with ODBC and NIS2006. I found that if I untick the "Turn Office Plug-in on" box on Miscellaneous on the Antivirus section of NIS2006, my ODBC options reappear and my Office programs, e.g. Word, open a bit quicker. I'm not sure off hand what I may be letting myself in for by turning this thing off though.NIS2006? Yuck. Alan
|||Great Job Alan/Tim! You are fabulous - the fix works. add a system re-start and life is good again!
The fix:
From Nortn Antivirus Home screen:
Select Security Basics, Auto-Protect, and Configure Auto-Protect
Under "Other", select Miscellaneous
Under "How to keep Microsoft Office Documents Protected" which should be renamed to "How to mysteriously destroy database development productivity", uncheck this evil box
Restart and enjoy the functionality you paid for...
Thanks again folks!
Next stop: complain to Symantec!
|||Same Problem with NAV 2007,
1) Bring up Norton Protection Center and Click on Antivirus tab.
2) Click on Settings
3) Basic Security
- Click on Auto-protect
- Click on Configure
- On Left hand side at the bottom, click on MISCELLANEOUS
- At Bottom of Right handside(options for miscellaneous)
Uncheck "How to keep Microsoft Office Documents ProtectedUnder "
- Click OK and close Norton Protection Center
4) Reopen Access DB and you should be good to go!!
Enjoy
|||Thanks everyone, I had the same problem. The Norton Protection center needed:
Norton Antivirus; Settings; Additional Options- Virus and Spyware Options;Miscellaneous; Turn on Scanning for Microsoft Office Documents
When this is unchecked I can get ODBC links again.
Mike
|||ThanksCannot link to SQL tables using ODBC Link table in Access 2003
When trying to link to an SQL table in Access 2003, the software appears to be malfunctioning.
The sequence of events is File - Get External Data - Link Tables - Files of Type: ODBC Databases().
The Problem: On two of my computers, the select data source window does not pop up, preventing me from linking to any ODBC data source.
Observations: This function has worked normally in the recent past and works on other computers running Access 2003. One difference between the computers working and non-working computers is Norton Antivirus 2006 (recent upgrade).
Has anyone experienced anything like this? What's going on?
Yes, I have the same problem and also installed Norton Anti-Virus 2006 recently. My OS is Windows XP Pro SP2. On another PC, where the only difference is that it has Access 2002, the problem does not occur and the dialog box comes up normally. I have floated this question on the UK AUG list processor and the first reply is that there is a Microsoft KB article on it, but my inter locutor does not know its number! Have you askled Norton?|||Here is the solution, from a member of UK AUG.
Alan, you’re a genius; the cure works perfectly.
Catherine, thank you too; I had noticed that Access especially was slow to open, but had no idea why.
Andy Couch, this may come in hand for your next SQL Server course as you may have a Norton victim among your trainees.
I’ll let my Norton 5-user subscription run out and them I’m in the market for something else - anything but Norton.
Timothy Coe.
-
That option scans all Office documents before opening it, but if you have autoprotect on, there shouldn't be any viruses on them in the first place...Regards, Catherine.
-
Timothy,
Downgraded is the correct word! It is awfully slow and my Office documents take ages to open now. I downgraded from Norton Internet Security 2005, which ran reasonably well, to 2006.
Thank you for bringing this up. Now you have, it reminds me that I've posted before on problems with ODBC and NIS2006. I found that if I untick the "Turn Office Plug-in on" box on Miscellaneous on the Antivirus section of NIS2006, my ODBC options reappear and my Office programs, e.g. Word, open a bit quicker. I'm not sure off hand what I may be letting myself in for by turning this thing off though.NIS2006? Yuck. Alan
|||Great Job Alan/Tim! You are fabulous - the fix works. add a system re-start and life is good again!
The fix:
From Nortn Antivirus Home screen:
Select Security Basics, Auto-Protect, and Configure Auto-Protect
Under "Other", select Miscellaneous
Under "How to keep Microsoft Office Documents Protected" which should be renamed to "How to mysteriously destroy database development productivity", uncheck this evil box
Restart and enjoy the functionality you paid for...
Thanks again folks!
Next stop: complain to Symantec!
|||Same Problem with NAV 2007,
1) Bring up Norton Protection Center and Click on Antivirus tab.
2) Click on Settings
3) Basic Security
- Click on Auto-protect
- Click on Configure
- On Left hand side at the bottom, click on MISCELLANEOUS
- At Bottom of Right handside(options for miscellaneous)
Uncheck "How to keep Microsoft Office Documents ProtectedUnder "
- Click OK and close Norton Protection Center
4) Reopen Access DB and you should be good to go!!
Enjoy
|||Thanks everyone, I had the same problem. The Norton Protection center needed:
Norton Antivirus; Settings; Additional Options- Virus and Spyware Options;Miscellaneous; Turn on Scanning for Microsoft Office Documents
When this is unchecked I can get ODBC links again.
Mike
|||ThanksCannot link to SQL tables using ODBC Link table in Access 2003
When trying to link to an SQL table in Access 2003, the software appears to be malfunctioning.
The sequence of events is File - Get External Data - Link Tables - Files of Type: ODBC Databases().
The Problem: On two of my computers, the select data source window does not pop up, preventing me from linking to any ODBC data source.
Observations: This function has worked normally in the recent past and works on other computers running Access 2003. One difference between the computers working and non-working computers is Norton Antivirus 2006 (recent upgrade).
Has anyone experienced anything like this? What's going on?
Yes, I have the same problem and also installed Norton Anti-Virus 2006 recently. My OS is Windows XP Pro SP2. On another PC, where the only difference is that it has Access 2002, the problem does not occur and the dialog box comes up normally. I have floated this question on the UK AUG list processor and the first reply is that there is a Microsoft KB article on it, but my inter locutor does not know its number! Have you askled Norton?|||Here is the solution, from a member of UK AUG.
Alan, you’re a genius; the cure works perfectly.
Catherine, thank you too; I had noticed that Access especially was slow to open, but had no idea why.
Andy Couch, this may come in hand for your next SQL Server course as you may have a Norton victim among your trainees.
I’ll let my Norton 5-user subscription run out and them I’m in the market for something else - anything but Norton.
Timothy Coe.
-
That option scans all Office documents before opening it, but if you have autoprotect on, there shouldn't be any viruses on them in the first place...Regards, Catherine.
-
Timothy,
Downgraded is the correct word! It is awfully slow and my Office documents take ages to open now. I downgraded from Norton Internet Security 2005, which ran reasonably well, to 2006.
Thank you for bringing this up. Now you have, it reminds me that I've posted before on problems with ODBC and NIS2006. I found that if I untick the "Turn Office Plug-in on" box on Miscellaneous on the Antivirus section of NIS2006, my ODBC options reappear and my Office programs, e.g. Word, open a bit quicker. I'm not sure off hand what I may be letting myself in for by turning this thing off though.NIS2006? Yuck. Alan
|||Great Job Alan/Tim! You are fabulous - the fix works. add a system re-start and life is good again!
The fix:
From Nortn Antivirus Home screen:
Select Security Basics, Auto-Protect, and Configure Auto-Protect
Under "Other", select Miscellaneous
Under "How to keep Microsoft Office Documents Protected" which should be renamed to "How to mysteriously destroy database development productivity", uncheck this evil box
Restart and enjoy the functionality you paid for...
Thanks again folks!
Next stop: complain to Symantec!
|||Same Problem with NAV 2007,
1) Bring up Norton Protection Center and Click on Antivirus tab.
2) Click on Settings
3) Basic Security
- Click on Auto-protect
- Click on Configure
- On Left hand side at the bottom, click on MISCELLANEOUS
- At Bottom of Right handside(options for miscellaneous)
Uncheck "How to keep Microsoft Office Documents ProtectedUnder "
- Click OK and close Norton Protection Center
4) Reopen Access DB and you should be good to go!!
Enjoy
|||Thanks everyone, I had the same problem. The Norton Protection center needed:
Norton Antivirus; Settings; Additional Options- Virus and Spyware Options;Miscellaneous; Turn on Scanning for Microsoft Office Documents
When this is unchecked I can get ODBC links again.
Mike
|||ThanksCannot link to SQL tables using ODBC Link table in Access 2003
When trying to link to an SQL table in Access 2003, the software appears to be malfunctioning.
The sequence of events is File - Get External Data - Link Tables - Files of Type: ODBC Databases().
The Problem: On two of my computers, the select data source window does not pop up, preventing me from linking to any ODBC data source.
Observations: This function has worked normally in the recent past and works on other computers running Access 2003. One difference between the computers working and non-working computers is Norton Antivirus 2006 (recent upgrade).
Has anyone experienced anything like this? What's going on?
Yes, I have the same problem and also installed Norton Anti-Virus 2006 recently. My OS is Windows XP Pro SP2. On another PC, where the only difference is that it has Access 2002, the problem does not occur and the dialog box comes up normally. I have floated this question on the UK AUG list processor and the first reply is that there is a Microsoft KB article on it, but my inter locutor does not know its number! Have you askled Norton?|||Here is the solution, from a member of UK AUG.
Alan, you’re a genius; the cure works perfectly.
Catherine, thank you too; I had noticed that Access especially was slow to open, but had no idea why.
Andy Couch, this may come in hand for your next SQL Server course as you may have a Norton victim among your trainees.
I’ll let my Norton 5-user subscription run out and them I’m in the market for something else - anything but Norton.
Timothy Coe.
-
That option scans all Office documents before opening it, but if you have autoprotect on, there shouldn't be any viruses on them in the first place...Regards, Catherine.
-
Timothy,
Downgraded is the correct word! It is awfully slow and my Office documents take ages to open now. I downgraded from Norton Internet Security 2005, which ran reasonably well, to 2006.
Thank you for bringing this up. Now you have, it reminds me that I've posted before on problems with ODBC and NIS2006. I found that if I untick the "Turn Office Plug-in on" box on Miscellaneous on the Antivirus section of NIS2006, my ODBC options reappear and my Office programs, e.g. Word, open a bit quicker. I'm not sure off hand what I may be letting myself in for by turning this thing off though.NIS2006? Yuck. Alan
|||Great Job Alan/Tim! You are fabulous - the fix works. add a system re-start and life is good again!
The fix:
From Nortn Antivirus Home screen:
Select Security Basics, Auto-Protect, and Configure Auto-Protect
Under "Other", select Miscellaneous
Under "How to keep Microsoft Office Documents Protected" which should be renamed to "How to mysteriously destroy database development productivity", uncheck this evil box
Restart and enjoy the functionality you paid for...
Thanks again folks!
Next stop: complain to Symantec!
|||Same Problem with NAV 2007,
1) Bring up Norton Protection Center and Click on Antivirus tab.
2) Click on Settings
3) Basic Security
- Click on Auto-protect
- Click on Configure
- On Left hand side at the bottom, click on MISCELLANEOUS
- At Bottom of Right handside(options for miscellaneous)
Uncheck "How to keep Microsoft Office Documents ProtectedUnder "
- Click OK and close Norton Protection Center
4) Reopen Access DB and you should be good to go!!
Enjoy
|||Thanks everyone, I had the same problem. The Norton Protection center needed:
Norton Antivirus; Settings; Additional Options- Virus and Spyware Options;Miscellaneous; Turn on Scanning for Microsoft Office Documents
When this is unchecked I can get ODBC links again.
Mike
|||ThanksSunday, February 19, 2012
cannot import table in management studio wizard. ODBC Error
Im using the Tasks/Import wizard in Management Studio for a 2005 MSSQL to import a table from another database, same MSSQL server
on my machine im having: mssql 2000 (default instance), mssql 2005. 2000 is not running, only 2005.
(by the way: all .net tools like Management Studio, Database explorer in VS 2005 and so on NEVER find the 2005 instance in the combo for available servers ! i always have to enter it manually)
I am always getting:
Operation stopped...
- Initializing Data Flow Task (Success)
- Initializing Connections (Success)
- Setting SQL Command (Success)
- Setting Source Connection (Error)
Messages
The connection "SourceConnectionOLEDB" is not found. This error is thrown by Connections collection when the specific connection element is not found.
({3A6A6A25-FF8B-4E17-B2A9-C0181A291B5D})
I tried all scenarios:
different databases / tables in same server / different servers, 1 talbe, many....
it always stops there !
What do I have to do ? It is impossible to work like that !
thanks in advance, Michael
Is microsoft going to answer this? I have seen many posts like this but no solution?|||They finally did after some month! in another thread
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=255347&SiteID=1
see: http://support.microsoft.com/kb/913817
hope this helps, good luck
Michael
cannot import table in management studio wizard. ODBC Error
Im using the Tasks/Import wizard in Management Studio for a 2005 MSSQL to import a table from another database, same MSSQL server
on my machine im having: mssql 2000 (default instance), mssql 2005. 2000 is not running, only 2005.
(by the way: all .net tools like Management Studio, Database explorer in VS 2005 and so on NEVER find the 2005 instance in the combo for available servers ! i always have to enter it manually)
I am always getting:
Operation stopped...
- Initializing Data Flow Task (Success)
- Initializing Connections (Success)
- Setting SQL Command (Success)
- Setting Source Connection (Error)
Messages
The connection "SourceConnectionOLEDB" is not found. This error is thrown by Connections collection when the specific connection element is not found.
({3A6A6A25-FF8B-4E17-B2A9-C0181A291B5D})
I tried all scenarios:
different databases / tables in same server / different servers, 1 talbe, many....
it always stops there !
What do I have to do ? It is impossible to work like that !
thanks in advance, Michael
Is microsoft going to answer this? I have seen many posts like this but no solution?|||They finally did after some month! in another thread
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=255347&SiteID=1
see: http://support.microsoft.com/kb/913817
hope this helps, good luck
Michael
Tuesday, February 14, 2012
cannot generate SSPI context
This only happens on a particular user's machine so far. the user is using
ms access, using odbc link to connect to SQL Server 2000 SP3a on W2k server.
With the MS Access running , suddenly the error happend when i ping the sql
server i can get its ip addr
i have checked the ms article on the SSPI but it does not seem to apply for
me in my case
appreciate any advise
tks & rdgs
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...tivity/200512/1One thing to check is the SQL Client Network stack. This is configured in th
e
(SQL Server) Client Network Utility. What you will probably find is that the
working clients either have Named Pipes before TCP/IP, or left out TCP/IP.
While the problem client will have TCP/IP first, or left out Named Pipes.
At a guess, you are running the SQL Server with a Domain Account, but it
does not have the permission to register the SQL Server's SPN (Service
Principal Name). This means that it cannot use delegation, which probably
isn't a problem for you guys. But when someone tries to attach using TCP/IP,
it can't use Kerberos and throws the error.
Clients that connect Named Pipes just by-pass Kerberos and security account
delegation.
I may have gotten a couple of the details mixed up, I'm not 100% on this.
There is a good Trouble Shooting page in the SQL Support and in BOL, under
Administering SQL Server is a page called "Security Account Delegation" that
is worth a read.
Good luck
"maxzsim via droptable.com" wrote:
> Hi,
>
> This only happens on a particular user's machine so far. the user is usin
g
> ms access, using odbc link to connect to SQL Server 2000 SP3a on W2k serve
r.
> With the MS Access running , suddenly the error happend when i ping the s
ql
> server i can get its ip addr
> i have checked the ms article on the SSPI but it does not seem to apply fo
r
> me in my case
> appreciate any advise
> tks & rdgs
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...tivity/200512/1
>
cannot generate SSPI context
This only happens on a particular user's machine so far. the user is using
ms access, using odbc link to connect to SQL Server 2000 SP3a on W2k server.
With the MS Access running , suddenly the error happend when i ping the sql
server i can get its ip addr
i have checked the ms article on the SSPI but it does not seem to apply for
me in my case
appreciate any advise
tks & rdgs
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...ivity/200512/1
One thing to check is the SQL Client Network stack. This is configured in the
(SQL Server) Client Network Utility. What you will probably find is that the
working clients either have Named Pipes before TCP/IP, or left out TCP/IP.
While the problem client will have TCP/IP first, or left out Named Pipes.
At a guess, you are running the SQL Server with a Domain Account, but it
does not have the permission to register the SQL Server's SPN (Service
Principal Name). This means that it cannot use delegation, which probably
isn't a problem for you guys. But when someone tries to attach using TCP/IP,
it can't use Kerberos and throws the error.
Clients that connect Named Pipes just by-pass Kerberos and security account
delegation.
I may have gotten a couple of the details mixed up, I'm not 100% on this.
There is a good Trouble Shooting page in the SQL Support and in BOL, under
Administering SQL Server is a page called "Security Account Delegation" that
is worth a read.
Good luck
"maxzsim via droptable.com" wrote:
> Hi,
>
> This only happens on a particular user's machine so far. the user is using
> ms access, using odbc link to connect to SQL Server 2000 SP3a on W2k server.
> With the MS Access running , suddenly the error happend when i ping the sql
> server i can get its ip addr
> i have checked the ms article on the SSPI but it does not seem to apply for
> me in my case
> appreciate any advise
> tks & rdgs
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...ivity/200512/1
>
Friday, February 10, 2012
Cannot find ODBC drivers
Some third party software may delete all the odbc driver information incorrectly during uninstalling.
Please try run the following four commands to re-register all the default odbc drivers:
odbcconf.exe /S /Lv odbcconf.log /F %systemroot%\system32\mdaccore.rsp
odbcconf.exe /S /Lv odbcconf.log /F %systemroot%\system32\sqlclnt.rsp
odbcconf.exe /S /Lv odbcconf.log /F %systemroot%\system32\odbcconf.rsp
odbcconf.exe /S /Lv odbcconf.log /F %systemroot%\system32\redist.rsp