Objects related to DB: fails

Showing posts with label fails. Show all posts

Friday, March 30, 2012

ODBC Error

I am trying to reinstall MSQL Server 2000, but the
installation fails. The sqlstp.log has the message
below. I have reinstalled MDAC and the error persists. Can someone tell me
what is wrong and how to fix
it?
Sincerely,
Alvin
Starting Service ...
SQL_Latin1_General_CP1_CI_AS
-m -Q -T4022 -T3659
Connecting to Server ...
driver={sql
server};server=DENISPUTNAMTOSH;UID=sa;PWD=;databas e=master
[Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle
on SQL_HANDLE_ENV failed
driver={sql
server};server=DENISPUTNAMTOSH;UID=sa;PWD=;databas e=master
[Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle
on SQL_HANDLE_ENV failed
driver={sql
server};server=DENISPUTNAMTOSH;UID=sa;PWD=;databas e=master
[Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle
on SQL_HANDLE_ENV failed
SQL Server configuration failed.Hi
What OS and Edition are you trying to install SQL Server on? Do you have
admin rights on the machine?
Regards
Mike
"Alvin" wrote:
> I am trying to reinstall MSQL Server 2000, but the
> installation fails. The sqlstp.log has the message
> below. I have reinstalled MDAC and the error persists. Can someone tell me
> what is wrong and how to fix
> it?
> Sincerely,
> Alvin
> Starting Service ...
> SQL_Latin1_General_CP1_CI_AS
> -m -Q -T4022 -T3659
> Connecting to Server ...
> driver={sql
> server};server=DENISPUTNAMTOSH;UID=sa;PWD=;databas e=master
> [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle
> on SQL_HANDLE_ENV failed
> driver={sql
> server};server=DENISPUTNAMTOSH;UID=sa;PWD=;databas e=master
> [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle
> on SQL_HANDLE_ENV failed
> driver={sql
> server};server=DENISPUTNAMTOSH;UID=sa;PWD=;databas e=master
> [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle
> on SQL_HANDLE_ENV failed
> SQL Server configuration failed.
>|||I am installing it on Server 2003 and yes, I have admin rights.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> What OS and Edition are you trying to install SQL Server on? Do you have
> admin rights on the machine?
> Regards
> Mike
> "Alvin" wrote:
> > I am trying to reinstall MSQL Server 2000, but the
> > installation fails. The sqlstp.log has the message
> > below. I have reinstalled MDAC and the error persists. Can someone tell me
> > what is wrong and how to fix
> > it?
> >
> > Sincerely,
> > Alvin
> >
> > Starting Service ...
> >
> > SQL_Latin1_General_CP1_CI_AS
> >
> > -m -Q -T4022 -T3659
> >
> > Connecting to Server ...
> >
> > driver={sql
> > server};server=DENISPUTNAMTOSH;UID=sa;PWD=;databas e=master
> >
> > [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle
> > on SQL_HANDLE_ENV failed
> >
> > driver={sql
> > server};server=DENISPUTNAMTOSH;UID=sa;PWD=;databas e=master
> >
> > [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle
> > on SQL_HANDLE_ENV failed
> >
> > driver={sql
> > server};server=DENISPUTNAMTOSH;UID=sa;PWD=;databas e=master
> >
> > [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle
> > on SQL_HANDLE_ENV failed
> >
> > SQL Server configuration failed.
> >
> >

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 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
>
>
>

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
>
>
>

Wednesday, March 21, 2012

ODBC Connection Fails from cluster node

I had a stand alone sql server that I upgraded to a cluster. I have an odbc connection called my_connection. The odbc test works fine. When I call the dsn from a php script it fails with this message:

Warning: odbc_connect(): SQL error: [Microsoft][ODBC SQL Server Driver][DBNETLIB
]SQL Server does not exist or access denied., SQL state 08001 in SQLConnect in D
:\storage\test.php on line 3
Could not connect to my_connection!

This same script works fine from any other computer. Is there an issue with connecting to a virtual server from the node via ODBC? Is there something I need to change in the client protocols?

Thanks in advance.

What's your connection string? The server name must have been changed (from the machine name to cluster network name resource name). Have you changed it in your conn string? Is it a default instance and named instance?|||

I also like to add that when I run Component Checker 2.0 I get

The following product releases were matched:

UNKNOWN

I'm wondering if this is the culprit.

|||

Its a system dsn, with SQL Server driver. The server is my virtual server name, and it uses sql authentication.

Does that answer your question? My odbc connection by itself works fine, but it doesn't when called from another app.

|||hmm, If you are able to connect when you test the DSN but fails in your app, I'm not sure what I can do. There are probably some issue with your app. I hope you test your app and DSN under same account.|||

This issue appears to be MDAC. Uninstalling and reinstalling SQL to enable clustering must have caused the problem.

What I did to figure this out was change the connection from dsn to dsn-less and it worked.

ODBC connection fails

I'm running SQL 2000/SP3 on a W2k server. I have a database with a standard
user (dbo rights). From any of my workstations I can create an ODBC
connection using SQL authentication.
When I try to create an ODBC connection on the server itself with the same
credentials, I get an error msg "login failed, username is not associated
with a trusted server connection". Using Windows authentication with another
user that has access to the SQL server works fine.
This doesn't make sense to me. What am I overlooking here? Any help/hint
would be appreciated.
Thanks
Claus"cjobes" <cjobes@.nova-tech.org> wrote in message
news:O6t6OxyBEHA.3928@.TK2MSFTNGP11.phx.gbl...
> I'm running SQL 2000/SP3 on a W2k server. I have a database with a
standard
> user (dbo rights). From any of my workstations I can create an ODBC
> connection using SQL authentication.
> When I try to create an ODBC connection on the server itself with the same
> credentials, I get an error msg "login failed, username is not associated
> with a trusted server connection". Using Windows authentication with
another
> user that has access to the SQL server works fine.
> This doesn't make sense to me. What am I overlooking here? Any help/hint
> would be appreciated.
The user account itself needs to have access to the server running SQL
Server. One way to verify, temporarily enable (don't leave it that way ;)
the server GUEST account.
Steve|||Hello,
Define user id "sa" and set pwd for sa account on sql server and try to
login that account on odbc connection.
i hope it will working fine.
Thanks,
Warm Regards,
Ayaz Ahmed
Software Engineer & Web Developer
Creative Chaos (Pvt.) Ltd.
"Managing Your Digital Risk"
http://www.csquareonline.com
Karachi, Pakistan
Mobile +92 300 2280950
Office +92 21 455 2414
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!|||Actually that is a not a good idea (at least as a permanent solution) as sql
security is sent over the network in clear text.
Steve
"Ayaz Ahmed" <ayaz@.csquareonline.com> wrote in message
news:e4EAqBkDEHA.2712@.TK2MSFTNGP10.phx.gbl...
> Hello,
> Define user id "sa" and set pwd for sa account on sql server and try to
> login that account on odbc connection.
> i hope it will working fine.
>
> Thanks,
> Warm Regards,
> Ayaz Ahmed
> Software Engineer & Web Developer
> Creative Chaos (Pvt.) Ltd.
> "Managing Your Digital Risk"
> http://www.csquareonline.com
> Karachi, Pakistan
> Mobile +92 300 2280950
> Office +92 21 455 2414
> *** Sent via Developersdex http://www.examnotes.net ***
> Don't just participate in USENET...get rewarded for it!

ODBC connection failing on 64 version of Windows 2003 server

I have an application that talks to a SQL backend using an ODBC DSN connection. It works fine when running on a 32bit machine but fails in the 64bit environment. The DSN is setup properly on the 64bit box and the Test Connection returns sucess. However when my application tries to use the DSN to connect to the database I recieve the following error.

IM002 - Data source name not found and no default driver specified.

The data source name does exist, it's in the ODBC.INI and in registry. As mentioned above the Test Connection succeeds in the ODBC Administrator so logic would dictate that it's setup correctly.

Any help would be appreciated.

Is your application 64-bit or 32-bit?

One possibility is that the Test Connection dialog uses 64-bit version of the driver and yoru application looks for a 32-bit version (or vice-versa).

|||Yeah, I thought of that too but both my application and MDAC are 32 bit.|||

DSN’s for 32bit and 64bit are stored separately in registry, those in HKLM/HKCR are for 64bit, 32bit DSN’s are stored in WOW registry.

You need to use the 32bit odbc admin tool (from windows\syswow64) to create 32bit DSN’s for your 32bit application.

|||thank you so muchhhhhhh|||Thank you, Thank you, Thank you, Thank you!|||

Question - after created System DSN using 32bit odbc, I created a linked server using the DSN,

sp_addlinkedserver 'MyLinkedSrv', ' ', 'MSDASQL', 'MyDSN'

and run a open-query in the SQL Management Studio to the linked server, i get error returns, - The OLE DB provider "MSDASQL" has not been registered. This error is because of SQL Native Client but when I created a LinkedServer with SQLNCLI, I get an error - OLE DB provider "SQLNCLI" for linked server "MAMSLS1" returned message "Login timeout expired".
OLE DB provider "SQLNCLI" for linked server "MAMSLS1" returned message "An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.".
Msg 53, Level 16, State 1, Line 0
Named Pipes Provider: Could not open a connection to SQL Server [53].

I am thinking because of the SQL management studio is 64bit, it won't use 32bit DSN.. Is there any way to run a query against to the linked server?

My system is Win2003 Enterprise 64bit running on Itenium and SQL 2005 server 64bit Enterprise edition. From this SQL server, I am trying to make a LinkedServer to InterBase database system. -- No problem with 32bit SQL 2005 (development) but this 64bit (production). Any insight would be appreciated.

Regards,

Sunny

|||

If you are setting up a linked server a connection is made from one SQL Server to another. If the first SQL Server is 64-bit then you need to create a 64-bit DSN. If it is 32-bit you need a 32-bit DSN.

|||

did anyone succeed in this on this with a sql2005 EE x64 sp1 to sql2000sp3a ?

Or it states the is an NCLI problem

- connectiontimeout (again and again and ......)

- OLE DB provider "SQLNCLI" for linked server "MySQl2000sp3a_03" returned message "Unspecified error".

OLE DB provider "SQLNCLI" for linked server "MySQl2000sp3a_03" returned message "The stored procedure required to complete this operation could not be found on the server. Please contact your system administrator.".

Msg 7311, Level 16, State 2, Line 3

Cannot obtain the schema rowset "DBSCHEMA_TABLES_INFO" for OLE DB provider "SQLNCLI" for linked server "MySQl2000sp3a_03". The provider supports the interface, but returns a failure code when it is used.

or it says :
Msg 7403, Level 16, State 1, Line 3

The OLE DB provider "MSDASQL" has not been registered.

None of the folowing definitions work :

|||

I just discouvered this thread with a KB link that may do the trick : http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=62887&SiteID=1

kb906954 did the trick

|||

I'm having similar issues

There is no equivalent of MSDASQL within 64 bit SQL, and from what i've read SQL Native client is meant to be used.

However I can't get this to see the 64 bit IBM ISeries ODBC DSN that I've configured within the 64bit ODBC setup

Anybody else having these problems?

|||

YES !!!

And the solution is: Execute odbccad32.exe in WOW directory. That's it !

www.mcfly.dj

|||

Hi,

I'm running SQL 2005 64 bit on the windows 2003 (64 bit box)

I'm trying to create a linked server using an ODBC driver which has a corresponding DSN

Using odbccad32.exe will work if you are using a 32 bit install of SQL 2005 on Windows 2003 (64bit)

but this doesn't work with a 64 bit instance of SQL 2005 as there is no MSDASQL provider to work with.

Has anybody managed to get the SQL native client provider SQLNCLI

in 64 bit SQL 2005 connected through a DSN (32bit or 64bit)?

Thanks, Richard

|||

Richard...see the following thread.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1239339&SiteID=1

|||

hey guys,

i have C# windows application which calles ODBC 32 bit provider. it is working very well with the 32 bit operating systems. My application is compiled targetting to any operating system.

When i install our application on the 64 bit operating systems, i am unable to connect to the 32 ODBC. Any one have idea how to call 32 bit ODBC from the 64 bit applications on the 64 bit operating systems

Please help in this.

regards

ODBC connection failing on 64 version of Windows 2003 server

IM002 - Data source name not found and no default driver specified.

The data source name does exist, it's in the ODBC.INI and in registry. As mentioned above the Test Connection succeeds in the ODBC Administrator so logic would dictate that it's setup correctly.

Any help would be appreciated.

Is your application 64-bit or 32-bit?

One possibility is that the Test Connection dialog uses 64-bit version of the driver and yoru application looks for a 32-bit version (or vice-versa).

|||Yeah, I thought of that too but both my application and MDAC are 32 bit.|||

DSN’s for 32bit and 64bit are stored separately in registry, those in HKLM/HKCR are for 64bit, 32bit DSN’s are stored in WOW registry.

You need to use the 32bit odbc admin tool (from windows\syswow64) to create 32bit DSN’s for your 32bit application.

|||thank you so muchhhhhhh|||Thank you, Thank you, Thank you, Thank you!|||

Question - after created System DSN using 32bit odbc, I created a linked server using the DSN,

sp_addlinkedserver 'MyLinkedSrv', ' ', 'MSDASQL', 'MyDSN'

I am thinking because of the SQL management studio is 64bit, it won't use 32bit DSN.. Is there any way to run a query against to the linked server?

Regards,

Sunny

|||

did anyone succeed in this on this with a sql2005 EE x64 sp1 to sql2000sp3a ?

Or it states the is an NCLI problem

- connectiontimeout (again and again and ......)

- OLE DB provider "SQLNCLI" for linked server "MySQl2000sp3a_03" returned message "Unspecified error".

Msg 7311, Level 16, State 2, Line 3

or it says :
Msg 7403, Level 16, State 1, Line 3

The OLE DB provider "MSDASQL" has not been registered.

None of the folowing definitions work :

|||

I just discouvered this thread with a KB link that may do the trick : http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=62887&SiteID=1

kb906954 did the trick

|||

I'm having similar issues

There is no equivalent of MSDASQL within 64 bit SQL, and from what i've read SQL Native client is meant to be used.

However I can't get this to see the 64 bit IBM ISeries ODBC DSN that I've configured within the 64bit ODBC setup

Anybody else having these problems?

|||

YES !!!

And the solution is: Execute odbccad32.exe in WOW directory. That's it !

www.mcfly.dj

|||

Hi,

I'm running SQL 2005 64 bit on the windows 2003 (64 bit box)

I'm trying to create a linked server using an ODBC driver which has a corresponding DSN

Using odbccad32.exe will work if you are using a 32 bit install of SQL 2005 on Windows 2003 (64bit)

but this doesn't work with a 64 bit instance of SQL 2005 as there is no MSDASQL provider to work with.

Has anybody managed to get the SQL native client provider SQLNCLI

in 64 bit SQL 2005 connected through a DSN (32bit or 64bit)?

Thanks, Richard

|||

Richard...see the following thread.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1239339&SiteID=1

|||

hey guys,

i have C# windows application which calles ODBC 32 bit provider. it is working very well with the 32 bit operating systems. My application is compiled targetting to any operating system.

Please help in this.

regards

ODBC connection failing on 64 version of Windows 2003 server

IM002 - Data source name not found and no default driver specified.

The data source name does exist, it's in the ODBC.INI and in registry. As mentioned above the Test Connection succeeds in the ODBC Administrator so logic would dictate that it's setup correctly.

Any help would be appreciated.

Is your application 64-bit or 32-bit?

One possibility is that the Test Connection dialog uses 64-bit version of the driver and yoru application looks for a 32-bit version (or vice-versa).

|||Yeah, I thought of that too but both my application and MDAC are 32 bit.|||

DSN’s for 32bit and 64bit are stored separately in registry, those in HKLM/HKCR are for 64bit, 32bit DSN’s are stored in WOW registry.

You need to use the 32bit odbc admin tool (from windows\syswow64) to create 32bit DSN’s for your 32bit application.

|||thank you so muchhhhhhh|||Thank you, Thank you, Thank you, Thank you!|||

Question - after created System DSN using 32bit odbc, I created a linked server using the DSN,

sp_addlinkedserver'MyLinkedSrv',' ','MSDASQL','MyDSN'

I am thinking because of the SQL management studio is 64bit, it won't use 32bit DSN.. Is there any way to run a query against to the linked server?

Regards,

Sunny

|||

did anyone succeed in this on this with a sql2005 EE x64 sp1 to sql2000sp3a ?

Or it states the is an NCLI problem

- connectiontimeout (again and again and ......)

- OLE DB provider "SQLNCLI" for linked server "MySQl2000sp3a_03" returned message "Unspecified error".

Msg 7311, Level 16, State 2, Line 3

or it says :
Msg 7403, Level 16, State 1, Line 3

The OLE DB provider "MSDASQL" has not been registered.

None of the folowing definitions work :

|||

I just discouvered this thread with a KB link that may do the trick : http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=62887&SiteID=1

kb906954 did the trick

|||

I'm having similar issues

There is no equivalent of MSDASQL within 64 bit SQL, and from what i've read SQL Native client is meant to be used.

However I can't get this to see the 64 bit IBM ISeries ODBC DSN that I've configured within the 64bit ODBC setup

Anybody else having these problems?

|||

YES !!!

And the solution is: Execute odbccad32.exe in WOW directory. That's it !

www.mcfly.dj

|||

Hi,

I'm running SQL 2005 64 bit on the windows 2003 (64 bit box)

I'm trying to create a linked server using an ODBC driver which has a corresponding DSN

Using odbccad32.exe will work if you are using a 32 bit install of SQL 2005 on Windows 2003 (64bit)

but this doesn't work with a 64 bit instance of SQL 2005 as there is no MSDASQL provider to work with.

Has anybody managed to get the SQL native client provider SQLNCLI

in 64 bit SQL 2005 connected through a DSN (32bit or 64bit)?

Thanks, Richard

|||

Richard...see the following thread.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1239339&SiteID=1

|||

hey guys,

i have C# windows application which calles ODBC 32 bit provider. it is working very well with the 32 bit operating systems. My application is compiled targetting to any operating system.

Please help in this.

regards

sql

ODBC connection failing on 64 version of Windows 2003 server

IM002 - Data source name not found and no default driver specified.

The data source name does exist, it's in the ODBC.INI and in registry. As mentioned above the Test Connection succeeds in the ODBC Administrator so logic would dictate that it's setup correctly.

Any help would be appreciated.

Is your application 64-bit or 32-bit?

One possibility is that the Test Connection dialog uses 64-bit version of the driver and yoru application looks for a 32-bit version (or vice-versa).

|||Yeah, I thought of that too but both my application and MDAC are 32 bit.|||

DSN’s for 32bit and 64bit are stored separately in registry, those in HKLM/HKCR are for 64bit, 32bit DSN’s are stored in WOW registry.

You need to use the 32bit odbc admin tool (from windows\syswow64) to create 32bit DSN’s for your 32bit application.

|||thank you so muchhhhhhh|||Thank you, Thank you, Thank you, Thank you!|||

Question - after created System DSN using 32bit odbc, I created a linked server using the DSN,

sp_addlinkedserver'MyLinkedSrv',' ','MSDASQL','MyDSN'

I am thinking because of the SQL management studio is 64bit, it won't use 32bit DSN.. Is there any way to run a query against to the linked server?

Regards,

Sunny

|||

did anyone succeed in this on this with a sql2005 EE x64 sp1 to sql2000sp3a ?

Or it states the is an NCLI problem

- connectiontimeout (again and again and ......)

- OLE DB provider "SQLNCLI" for linked server "MySQl2000sp3a_03" returned message "Unspecified error".

Msg 7311, Level 16, State 2, Line 3

or it says :
Msg 7403, Level 16, State 1, Line 3

The OLE DB provider "MSDASQL" has not been registered.

None of the folowing definitions work :

|||

I just discouvered this thread with a KB link that may do the trick : http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=62887&SiteID=1

kb906954 did the trick

|||

I'm having similar issues

There is no equivalent of MSDASQL within 64 bit SQL, and from what i've read SQL Native client is meant to be used.

However I can't get this to see the 64 bit IBM ISeries ODBC DSN that I've configured within the 64bit ODBC setup

Anybody else having these problems?

|||

YES !!!

And the solution is: Execute odbccad32.exe in WOW directory. That's it !

www.mcfly.dj

|||

Hi,

I'm running SQL 2005 64 bit on the windows 2003 (64 bit box)

I'm trying to create a linked server using an ODBC driver which has a corresponding DSN

Using odbccad32.exe will work if you are using a 32 bit install of SQL 2005 on Windows 2003 (64bit)

but this doesn't work with a 64 bit instance of SQL 2005 as there is no MSDASQL provider to work with.

Has anybody managed to get the SQL native client provider SQLNCLI

in 64 bit SQL 2005 connected through a DSN (32bit or 64bit)?

Thanks, Richard

|||

Richard...see the following thread.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1239339&SiteID=1

|||

hey guys,

i have C# windows application which calles ODBC 32 bit provider. it is working very well with the 32 bit operating systems. My application is compiled targetting to any operating system.

Please help in this.

regards

ODBC connection failing on 64 version of Windows 2003 server

IM002 - Data source name not found and no default driver specified.

The data source name does exist, it's in the ODBC.INI and in registry. As mentioned above the Test Connection succeeds in the ODBC Administrator so logic would dictate that it's setup correctly.

Any help would be appreciated.

Is your application 64-bit or 32-bit?

One possibility is that the Test Connection dialog uses 64-bit version of the driver and yoru application looks for a 32-bit version (or vice-versa).

|||Yeah, I thought of that too but both my application and MDAC are 32 bit.|||

DSN’s for 32bit and 64bit are stored separately in registry, those in HKLM/HKCR are for 64bit, 32bit DSN’s are stored in WOW registry.

You need to use the 32bit odbc admin tool (from windows\syswow64) to create 32bit DSN’s for your 32bit application.

|||thank you so muchhhhhhh|||Thank you, Thank you, Thank you, Thank you!|||

Question - after created System DSN using 32bit odbc, I created a linked server using the DSN,

sp_addlinkedserver 'MyLinkedSrv', ' ', 'MSDASQL', 'MyDSN'

I am thinking because of the SQL management studio is 64bit, it won't use 32bit DSN.. Is there any way to run a query against to the linked server?

Regards,

Sunny

|||

did anyone succeed in this on this with a sql2005 EE x64 sp1 to sql2000sp3a ?

Or it states the is an NCLI problem

- connectiontimeout (again and again and ......)

- OLE DB provider "SQLNCLI" for linked server "MySQl2000sp3a_03" returned message "Unspecified error".

Msg 7311, Level 16, State 2, Line 3

or it says :
Msg 7403, Level 16, State 1, Line 3

The OLE DB provider "MSDASQL" has not been registered.

None of the folowing definitions work :

|||

I just discouvered this thread with a KB link that may do the trick : http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=62887&SiteID=1

kb906954 did the trick

|||

I'm having similar issues

There is no equivalent of MSDASQL within 64 bit SQL, and from what i've read SQL Native client is meant to be used.

However I can't get this to see the 64 bit IBM ISeries ODBC DSN that I've configured within the 64bit ODBC setup

Anybody else having these problems?

|||

YES !!!

And the solution is: Execute odbccad32.exe in WOW directory. That's it !

www.mcfly.dj

|||

Hi,

I'm running SQL 2005 64 bit on the windows 2003 (64 bit box)

I'm trying to create a linked server using an ODBC driver which has a corresponding DSN

Using odbccad32.exe will work if you are using a 32 bit install of SQL 2005 on Windows 2003 (64bit)

but this doesn't work with a 64 bit instance of SQL 2005 as there is no MSDASQL provider to work with.

Has anybody managed to get the SQL native client provider SQLNCLI

in 64 bit SQL 2005 connected through a DSN (32bit or 64bit)?

Thanks, Richard

|||

Richard...see the following thread.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1239339&SiteID=1

|||

hey guys,

i have C# windows application which calles ODBC 32 bit provider. it is working very well with the 32 bit operating systems. My application is compiled targetting to any operating system.

Please help in this.

regards

ODBC connection failing on 64 version of Windows 2003 server

IM002 - Data source name not found and no default driver specified.

The data source name does exist, it's in the ODBC.INI and in registry. As mentioned above the Test Connection succeeds in the ODBC Administrator so logic would dictate that it's setup correctly.

Any help would be appreciated.

Is your application 64-bit or 32-bit?

One possibility is that the Test Connection dialog uses 64-bit version of the driver and yoru application looks for a 32-bit version (or vice-versa).

|||Yeah, I thought of that too but both my application and MDAC are 32 bit.|||

DSN’s for 32bit and 64bit are stored separately in registry, those in HKLM/HKCR are for 64bit, 32bit DSN’s are stored in WOW registry.

You need to use the 32bit odbc admin tool (from windows\syswow64) to create 32bit DSN’s for your 32bit application.

|||thank you so muchhhhhhh|||Thank you, Thank you, Thank you, Thank you!|||

Question - after created System DSN using 32bit odbc, I created a linked server using the DSN,

sp_addlinkedserver 'MyLinkedSrv', ' ', 'MSDASQL', 'MyDSN'

I am thinking because of the SQL management studio is 64bit, it won't use 32bit DSN.. Is there any way to run a query against to the linked server?

Regards,

Sunny

|||

did anyone succeed in this on this with a sql2005 EE x64 sp1 to sql2000sp3a ?

Or it states the is an NCLI problem

- connectiontimeout (again and again and ......)

- OLE DB provider "SQLNCLI" for linked server "MySQl2000sp3a_03" returned message "Unspecified error".

Msg 7311, Level 16, State 2, Line 3

or it says :
Msg 7403, Level 16, State 1, Line 3

The OLE DB provider "MSDASQL" has not been registered.

None of the folowing definitions work :

|||

I just discouvered this thread with a KB link that may do the trick : http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=62887&SiteID=1

kb906954 did the trick

|||

I'm having similar issues

There is no equivalent of MSDASQL within 64 bit SQL, and from what i've read SQL Native client is meant to be used.

However I can't get this to see the 64 bit IBM ISeries ODBC DSN that I've configured within the 64bit ODBC setup

Anybody else having these problems?

|||

YES !!!

And the solution is: Execute odbccad32.exe in WOW directory. That's it !

www.mcfly.dj

|||

Hi,

I'm running SQL 2005 64 bit on the windows 2003 (64 bit box)

I'm trying to create a linked server using an ODBC driver which has a corresponding DSN

Using odbccad32.exe will work if you are using a 32 bit install of SQL 2005 on Windows 2003 (64bit)

but this doesn't work with a 64 bit instance of SQL 2005 as there is no MSDASQL provider to work with.

Has anybody managed to get the SQL native client provider SQLNCLI

in 64 bit SQL 2005 connected through a DSN (32bit or 64bit)?

Thanks, Richard

|||

Richard...see the following thread.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1239339&SiteID=1

|||

hey guys,

i have C# windows application which calles ODBC 32 bit provider. it is working very well with the 32 bit operating systems. My application is compiled targetting to any operating system.

Please help in this.

regards

Monday, March 19, 2012

odbc call to sql 7 fails

Have 3 XP machines running Office XP Pro. The odbc file
dsn sits in same file as the mdb on a server (on purpose
so it gets backed up regularly). The odbc file connects
to an SQL 7 database on an NT4 machine. All sql driver
versions are 2000.81.9042.00 The authentication is an
sql account - not windows.
Two people can open and connect fine. One gets a login
failure.
If we place the 'failed' user into the domain
administrator account and he logs in at another machine,
he connects fine. If he tries to login from his machine,
still fails.
Two questions:
Why does it fail in either scenario at his machine?
Using sql authentication, how can I let him connect
WITHOUT being a member of the admin group?
Many thanks for any help!
(P.S. Same account works fine through an asp page on the
web without the user having to be in the administrator's
group.)At some level, Named Pipes connections still do make NT calls to see if you
have Windows rights on the other machine.
My suggestion is to either share a network drive or find a network drive
that you don't mind this person connecting to. Make sure they can connect
to that shared drive. Then see how that affects the SQL connection attempt.
Unshare the drive. See what happens to the SQL connection attempt.
Suggestion #2 is to go into SQL Enterprise manager and add a Windows NT
authentication entry for his user account. Maybe that will help.
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"Janet" <janetb@.mtn.ncahec.org> wrote in message
news:27f501c3e104$cfd509b0$a501280a@.phx.gbl...

quote:

> Have 3 XP machines running Office XP Pro. The odbc file
> dsn sits in same file as the mdb on a server (on purpose
> so it gets backed up regularly). The odbc file connects
> to an SQL 7 database on an NT4 machine. All sql driver
> versions are 2000.81.9042.00 The authentication is an
> sql account - not windows.
> Two people can open and connect fine. One gets a login
> failure.
> If we place the 'failed' user into the domain
> administrator account and he logs in at another machine,
> he connects fine. If he tries to login from his machine,
> still fails.
> Two questions:
> Why does it fail in either scenario at his machine?
> Using sql authentication, how can I let him connect
> WITHOUT being a member of the admin group?
> Many thanks for any help!
> (P.S. Same account works fine through an asp page on the
> web without the user having to be in the administrator's
> group.)
>

|||Andy,
Many thanks for the reply.
I know this isn't the popular thinking, but I had set up
sql to take sql authentication only for security
purposes. That way, if someone compromises the network
he/she couldn't by default get to sql data and;
conversly, if someone compromises sql he/she couldn't by
default get to network files.
But, the only way I could get this guy connected was to
use Windows Authentication on a group, put him in it, and
then everything worked fine. I think it's because our pc
machines are XP and the server is still NT/sql7. (The
servers will be updated to 2003 soon with Active
Directory, so maybe this will "all go away".) So, by
default and no matter what you specify, authentication is
by Windows, not sql.
Again, thanks for your reply. If I continue to have
problems after the upgrade, I will be sure to try your
suggestion.
Janet

quote:

>--Original Message--
>At some level, Named Pipes connections still do make NT

calls to see if you

quote:

>have Windows rights on the other machine.
>My suggestion is to either share a network drive or find

a network drive

quote:

>that you don't mind this person connecting to. Make

sure they can connect

quote:

>to that shared drive. Then see how that affects the SQL

connection attempt.

quote:

>Unshare the drive. See what happens to the SQL

connection attempt.

quote:

>Suggestion #2 is to go into SQL Enterprise manager and

add a Windows NT

quote:

>authentication entry for his user account. Maybe that

will help.

quote:

>--
> ****************************************
*****************

**********

quote:

>Andy S.
>MCSE NT/2000, MCDBA SQL 7/2000
>andymcdba1@.NOMORESPAM.yahoo.com
>Please remove NOMORESPAM before replying.
>Always keep your antivirus and Microsoft software
>up to date with the latest definitions and product

updates.

quote:

>Be suspicious of every email attachment, I will never

send

quote:

>or post anything other than the text of a http:// link

nor

quote:

>post the link directly to a file for downloading.
>This posting is provided "as is" with no warranties
>and confers no rights.
> ****************************************
*****************

**********

quote:

>"Janet" <janetb@.mtn.ncahec.org> wrote in message
>news:27f501c3e104$cfd509b0$a501280a@.phx.gbl...
file[QUOTE]
purpose[QUOTE]
connects[QUOTE]
machine,[QUOTE]
machine,[QUOTE]
the[QUOTE]
administrator's[QUOTE]
>
>.
>

|||Unfortunately, SQL runs in mixed mode when it SQL security is used. If
someone compromises the administrative NT account, they'll get into Windows
and SQL. In that sense Windows NT authentication is secure.
To really secure your SQL server from a Windows perspective, always password
the SA account, consider restricting rights on xp_cmdshell (that procedure
in the master database grants DOS level access to administrators) and try
putting a proxy account for non-admin users for SQL Server agent.
The authentication models still get frustrating for me. I can't stand the
fact that when you restore a database to a separate server, the logins and
users can get out of sync requiring the procedure sp_change_users_login
auto_fix, user_id. (try restoring a database on a separate server), then
add a login with the user name of a user in the database. That is always a
minor annoyance.
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"Janet" <janetb@.mtn.ncahec.org> wrote in message
news:34f501c3e1d8$33367ba0$a601280a@.phx.gbl...[QUOTE]
> Andy,
> Many thanks for the reply.
> I know this isn't the popular thinking, but I had set up
> sql to take sql authentication only for security
> purposes. That way, if someone compromises the network
> he/she couldn't by default get to sql data and;
> conversly, if someone compromises sql he/she couldn't by
> default get to network files.
> But, the only way I could get this guy connected was to
> use Windows Authentication on a group, put him in it, and
> then everything worked fine. I think it's because our pc
> machines are XP and the server is still NT/sql7. (The
> servers will be updated to 2003 soon with Active
> Directory, so maybe this will "all go away".) So, by
> default and no matter what you specify, authentication is
> by Windows, not sql.
> Again, thanks for your reply. If I continue to have
> problems after the upgrade, I will be sure to try your
> suggestion.
> Janet
>
> calls to see if you
> a network drive
> sure they can connect
> connection attempt.
> connection attempt.
> add a Windows NT
> will help.
> **********
> updates.
> send
> nor
> **********
> file
> purpose
> connects
> machine,
> machine,
> the
> administrator's

Monday, March 12, 2012

ODBC Administrator app fails only on SQL Server

Make sure this isn't a rights-issue
You could reinstall mdac 2.8 or sql server client.

>--Original Message--
>Hello,
>I am on an XP SP1 system and when I use the ODBC
Administrator application
>to establish a new SQL Server DSN the process fails.
>After launching the ODBC Administrator I push the "Add"
button and select
>"SQL Server" from the list of available drivers. When I
then push the
>"Finish" button I am immediately returned to the initial
ODBC Administrator
>window. That is, I am never presented with the dialog
box for configuring
>the SQL Server DSN. If I select a Sybase, MS Access or
Oracle DSN I do get
>the expected configuration dialog box. Under W2000 I get
a dialog box for
>configuring a SQL Server DSN and on a different XP SP1
system I also get the
>configuration dialog box. All of this suggets that
something has gone wrong
>on this particular XP SP1 box. Can anyone tell me what's
happened and how
>to fix this?
>Thanks very much for the help.
>Al Koch
>AlKoch@.MyRealBoxREMOVEALLTHESECHARS.com
>
>.
>
Thanks for the reply. It wasn't a right issue since I was logged in as an
Admin. However your suggestion to reinstall MDAC fixed the problem I a
curious though, are you aware of what might have triggered the loss of
(only) the SQL Server ODBC facility?
Thanks,
Al
|||I can only guess
-Sql2000 has been updated to SP3a
(Perhaps the old driver was one for sql server 7)
-WindowsXP had a fair share of updates as well.
-Perhaps a anti-virusprogram was running during install of
mdac/updates

>--Original Message--
>Thanks for the reply. It wasn't a right issue since I
was logged in as an
>Admin. However your suggestion to reinstall MDAC fixed
the problem I a
>curious though, are you aware of what might have
triggered the loss of
>(only) the SQL Server ODBC facility?
>Thanks,
>Al
>
>.
>
|||Thanks for the possible causes and thanks again for the help!
Al
"gandalf" <anonymous@.discussions.microsoft.com> wrote in message
news:307801c4b03d$6f50dac0$a301280a@.phx.gbl...
> I can only guess
> -Sql2000 has been updated to SP3a
> (Perhaps the old driver was one for sql server 7)
> -WindowsXP had a fair share of updates as well.
> -Perhaps a anti-virusprogram was running during install of
> mdac/updates
>

ODBC Administrator app fails only on SQL Server

Make sure this isn't a rights-issue
You could reinstall mdac 2.8 or sql server client.

>--Original Message--
>Hello,
>I am on an XP SP1 system and when I use the ODBC
Administrator application
>to establish a new SQL Server DSN the process fails.
>After launching the ODBC Administrator I push the "Add"
button and select
>"SQL Server" from the list of available drivers. When I
then push the
>"Finish" button I am immediately returned to the initial
ODBC Administrator
>window. That is, I am never presented with the dialog
box for configuring
>the SQL Server DSN. If I select a Sybase, MS Access or
Oracle DSN I do get
>the expected configuration dialog box. Under W2000 I get
a dialog box for
>configuring a SQL Server DSN and on a different XP SP1
system I also get the
>configuration dialog box. All of this suggets that
something has gone wrong
>on this particular XP SP1 box. Can anyone tell me what's
happened and how
>to fix this?
>Thanks very much for the help.
>Al Koch
>AlKoch@.MyRealBoxREMOVEALLTHESECHARS.com
>
>.
>Thanks for the reply. It wasn't a right issue since I was logged in as an
Admin. However your suggestion to reinstall MDAC fixed the problem I a
curious though, are you aware of what might have triggered the loss of
(only) the SQL Server ODBC facility?
Thanks,
Al|||I can only guess
-Sql2000 has been updated to SP3a
(Perhaps the old driver was one for sql server 7)
-WindowsXP had a fair share of updates as well.
-Perhaps a anti-virusprogram was running during install of
mdac/updates

>--Original Message--
>Thanks for the reply. It wasn't a right issue since I
was logged in as an
>Admin. However your suggestion to reinstall MDAC fixed
the problem I a
>curious though, are you aware of what might have
triggered the loss of
>(only) the SQL Server ODBC facility?
>Thanks,
>Al
>
>.
>|||Thanks for the possible causes and thanks again for the help!
Al
"gandalf" <anonymous@.discussions.microsoft.com> wrote in message
news:307801c4b03d$6f50dac0$a301280a@.phx.gbl...
> I can only guess
> -Sql2000 has been updated to SP3a
> (Perhaps the old driver was one for sql server 7)
> -WindowsXP had a fair share of updates as well.
> -Perhaps a anti-virusprogram was running during install of
> mdac/updates
>

Friday, March 9, 2012

odbc

I have moved my Sql2000 and the database to a new server. It works fine on the server but when I try to attach from a workstation odbc fails it tells me the server is unavailable.Hi,
Have you changed the ODBC driver on the workstation to
point to the new server?
Take a look at the account your using to connect to the db
on the new server? The account you are using must exist on
the new db server as well.
You could have orphaned users?
Possible that your new server is NOT on the same network
as the old one or your workstation.
hth
DeeJay
>--Original Message--
>I have moved my Sql2000 and the database to a new server.
It works fine on the server but when I try to attach from
a workstation odbc fails it tells me the server is
unavailable.
>.
>|||Hi,
Just by putting the users name in Enterprise Manager may
not be enough. It seems like you have orphaned users. Try
these scripts one at a time from the server or a client
machine that can connect to the new server:
1.
Use database_name
exec sp_change_users_login 'report'
This scripts reports any orphaned users in the database.
2.
Use database_name
exec
sp_change_users_login 'update_one', 'login_name', 'login_na
me_in_db'
Use this script to update all users one at a time. You
should run script for each user only if script 1 reported
a result.
If you have orphaned users and 'dspusers' was a user in
the old server, it will be returned as a result of script
1.
The other thing:
Are you able to ping this new server from the workstation?
When you configured the ODBC driver, did the server name
show-up in the drop-down list of SQL Servers?
hth
DeeJay
>--Original Message--
> Hi Deejay
>thanks for getting me started , yes I changed the Odbc
driver to point to the new server.
>I have an account called dspusers that I put into
enterprise manger and checked to be sure that my server is
on the same network. The workstation will attach to the
old server by just changing the server name in odbc, for
the new server I have used the name in odbc and when it
did not work I tried the address with the same results.
Anything else I can try.
> -- DeeJay Puar wrote: --
> Hi,
> Have you changed the ODBC driver on the workstation
to
> point to the new server?
> Take a look at the account your using to connect to
the db
> on the new server? The account you are using must
exist on
> the new db server as well.
> You could have orphaned users?
> Possible that your new server is NOT on the same
network
> as the old one or your workstation.
> hth
> DeeJay
>
> >--Original Message--
> >I have moved my Sql2000 and the database to a new
server.
> It works fine on the server but when I try to attach
from
> a workstation odbc fails it tells me the server is
> unavailable.
> >.
> >
>.
>|||Yes I can ping the server from the workstation, by name or by address. Script 1 shows all my users but dspusers, I am having trouble with script 2 getting syntax errors|||If Script 1 is returning results, all those users are
orphaned users. Orphaned users WILL NOT be able to connect
this database. I am wondering why dspusers in not showing?
Was this user already on the new server?
Script 2 should look like this:
EXEC sp_change_users_login 'Update_One', 'Mary', 'NewMary'
Where Mary is the name currently in the db and 'NewMary'
is the new name added in the Enterprise Manager.
I need some more info:
Was the dspuser in the old server as well? Or did you just
create it in on the new server? If you created on the new
server, did you grant dspusers access in the database.
Also, look in the db users and see if name is there? To do
this: Expand the db in question, and click on users.
How did you move the database?
I am sure if mentioned already or not, are you able to
connect to the database from the server? or anyother
workstation?
You did not answer the other question: When you configured
the ODBC driver, did the server name
show-up in the drop-down list of SQL Servers?
DeeJay
>--Original Message--
>Yes I can ping the server from the workstation, by name
or by address. Script 1 shows all my users but dspusers, I
am having trouble with script 2 getting syntax errors
>.
>

Occasional record fails to merge replicate, but SQL Server reports no errors

Rob,
I have seen this happen in 2 circumstances:
(1) Firstly when the filter was set to 1=2 and inserts
were made while the merge agent was running
(2) Secondly, if you bulk insert the rows and choose the
defaults, then FIRE_TRIGGERS is false and consequently
the rows are not added to MSmerge_contents.
In either case, you need to run sp_addtabletocontents to
include the rows then resynchronise. Alternatively you
can use sp_mergedummyupdate for a single row.
For your case I'd first check to see if there are
corresponding records in MSmerge_contents - ie did the
triggers fire? This should help narrow things down.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Paul, thanks for the quick reply. I have no filters on the merge and do not
do any bulk inserts, but I will take your suggestion and review
msmerge_contents next time this occurs.
Rob Kraft
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:2dd801c4c0fd$22539b60$a601280a@.phx.gbl...
> Rob,
> I have seen this happen in 2 circumstances:
> (1) Firstly when the filter was set to 1=2 and inserts
> were made while the merge agent was running
> (2) Secondly, if you bulk insert the rows and choose the
> defaults, then FIRE_TRIGGERS is false and consequently
> the rows are not added to MSmerge_contents.
> In either case, you need to run sp_addtabletocontents to
> include the rows then resynchronise. Alternatively you
> can use sp_mergedummyupdate for a single row.
> For your case I'd first check to see if there are
> corresponding records in MSmerge_contents - ie did the
> triggers fire? This should help narrow things down.
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>

Monday, February 20, 2012

Obscure SQL Server error when task fails in my dts

Does anyone have any insight to this error:
"Duplicate column name resolution could not be done because the ordinal specified a column of a different name"

I googled it and got one result with no resolution.
I get this error from SQL Server when a task in my dts package fails. My dts package is attempting to update records whose fields have changed based on a specified criteria.

Any help would be greatly appreciated.

TIA,
Jennifer
I moved this thread to the dts/SSIS forum.|||

Gail Erickson [MS] wrote:
I moved this thread to the dts/SSIS forum.

Gail -- There is no DTS forum here at forums.microsoft.com.|||Jennifer -- For DTS related issues, please see the following group: http://groups.google.com/group/microsoft.public.sqlserver.dts?lnk=sg|||ok thanks!

Friday, March 30, 2012

ODBC Error

ODBC Error

Friday, March 23, 2012

ODBC Connection SQL Server Error

ODBC Connection SQL Server Error

Wednesday, March 21, 2012

ODBC Connection Fails from cluster node

ODBC connection fails

ODBC connection failing on 64 version of Windows 2003 server

ODBC connection failing on 64 version of Windows 2003 server

ODBC connection failing on 64 version of Windows 2003 server

ODBC connection failing on 64 version of Windows 2003 server

ODBC connection failing on 64 version of Windows 2003 server

ODBC connection failing on 64 version of Windows 2003 server

Monday, March 19, 2012

odbc call to sql 7 fails

Monday, March 12, 2012

ODBC Administrator app fails only on SQL Server

ODBC Administrator app fails only on SQL Server

Friday, March 9, 2012

odbc

Occasional record fails to merge replicate, but SQL Server reports no errors

Monday, February 20, 2012

Obscure SQL Server error when task fails in my dts

Objects related to DB

Blog Archive

About Me