80004005 ODBC SQL Server Driver shared memory or TCP/IP sockets er

Hi all,
I have been getting these errors on simple ASP code on my web site:
|80004005|[Microsoft][ODBC_SQL_Server_Driver][TCP/IP_Sockets]ConnectionWrite_(send()).
|80004005|[Microsoft][ODBC_SQL_Server_Driver]Timeout_expired
|80004005|[Microsoft][ODBC_SQL_Server_Driver][Shared_Memory]SQL_Server_does_not_exist_or_access_denied.
|80004005|[Microsoft][ODBC_SQL_Server_Driver][TCP/IP_Sockets]SQL_Server_does_not_exist_or_access_denied.
|80004005|[Microsoft][ODBC_SQL_Server_Driver]Timeout_expired
The SQL 2000 is Standard Edition, SP3 and OS is Windows 2003 Standard edition.
Previously I never faced this problem before. These errors come
intermittently, at no specific time. It appears randomly at any time.
The only thing I have to do is reboot the server to solve this issue.
please tell me if there's anything to solve this issue.
reboot?
"tapman" wrote:

> Hi all,
> I have been getting these errors on simple ASP code on my web site:
> |80004005|[Microsoft][ODBC_SQL_Server_Driver][TCP/IP_Sockets]ConnectionWrite_(send()).
> |80004005|[Microsoft][ODBC_SQL_Server_Driver]Timeout_expired
> |80004005|[Microsoft][ODBC_SQL_Server_Driver][Shared_Memory]SQL_Server_does_not_exist_or_access_denied.
>
> |80004005|[Microsoft][ODBC_SQL_Server_Driver][TCP/IP_Sockets]SQL_Server_does_not_exist_or_access_denied.
> |80004005|[Microsoft][ODBC_SQL_Server_Driver]Timeout_expired
> The SQL 2000 is Standard Edition, SP3 and OS is Windows 2003 Standard edition.
> Previously I never faced this problem before. These errors come
> intermittently, at no specific time. It appears randomly at any time.
> The only thing I have to do is reboot the server to solve this issue.
> please tell me if there's anything to solve this issue.
>

64-bit ODBC issues with DTEXEC

We've hit a weird problem that we can't resolve. We have a package using ODBC to extract from an AS400. When running the package through DTEXECUI, the package executes successfully. However, it chokes when executing through DTEXEC or as a SQL Agent job on our 64-bit machine. Seems like DTEXECUI is using the 32-bit ODBC driver while DTEXEC and SQL Agent is trying to access an non-existent 64 bit ODBC driver. We're using a DSN-less connection string (Driver={Client Access ODBC Driver (32-bit)};system=AS400;....) so that's not the issue. Anyone else seen this weird error? Any possible workarounds?If the 64-bit ODBC driver is not aviailable, you can run the package in 32-bit mode.

To do this, edit the SSIS step in Agent. Copy the text from Command Line tab. Switch step to use CmdExec subsystem instead of SSIS subsystem. Specify 32-bit DTEXEC as application ("C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\dtexec.exe" - including quotes) and add the parameters you've copied from Command Line tab.|||Thank you. This will work until we upgrade Client Access to a version supporting 64 bit drivers. This is our first 64-bit server. Was wondering why there was both "C:\Program Files\" and "C:\Program Files (x86)\" directories and didn't know how to execute dtexec in 32-bit mode.

64 bit ODBC Datasource

Hello together
I'm running Reporting Services on a 64 bit Windows 2003 R2 machine. I've
installed the MyOdbc 3.51 Drivers for MySql which I would like to use as the
Datasource for my reports. I configured and tested the ODBC connection
successfully using the odbcad32.exe in the windows\syswow64 folder.
But when I deploy a report which I designed on my 32 bit development machine
where all is running correctly, and I run the report on the server, it
cannot find the datasource.
I think it has the same reason why I cannot see the MyODBC driver in the
normal ODBC Configuration Manager in the Administrative Tools.
Is there a possiblity to do that anyway'
Thank you and greetings from Switzerland
ThomasHi Thomas,
Did you get a response to this question? I'm not using MySQL, but
I've spent most of today chasing this exact problem. I can tell you
that hacking the registry doesn't work, but I'd really like to know if
you heard from someone that had solved it, or if you found the answer
yourself.
Thanks in advance.
Dan
Thomas Bolt wrote:
> Hello together
> I'm running Reporting Services on a 64 bit Windows 2003 R2 machine. I've
> installed the MyOdbc 3.51 Drivers for MySql which I would like to use as the
> Datasource for my reports. I configured and tested the ODBC connection
> successfully using the odbcad32.exe in the windows\syswow64 folder.
> But when I deploy a report which I designed on my 32 bit development machine
> where all is running correctly, and I run the report on the server, it
> cannot find the datasource.
> I think it has the same reason why I cannot see the MyODBC driver in the
> normal ODBC Configuration Manager in the Administrative Tools.
> Is there a possiblity to do that anyway'
> Thank you and greetings from Switzerland
> Thomas|||Hi Dan,
Did you get anywhere with this? I'm in exactly the same position that you
were in August!
Any help would be very much appreciated.
Rob
"barnetted@.michigan.gov" wrote:
> Hi Thomas,
> Did you get a response to this question? I'm not using MySQL, but
> I've spent most of today chasing this exact problem. I can tell you
> that hacking the registry doesn't work, but I'd really like to know if
> you heard from someone that had solved it, or if you found the answer
> yourself.
> Thanks in advance.
> Dan
> Thomas Bolt wrote:
> > Hello together
> >
> > I'm running Reporting Services on a 64 bit Windows 2003 R2 machine. I've
> > installed the MyOdbc 3.51 Drivers for MySql which I would like to use as the
> > Datasource for my reports. I configured and tested the ODBC connection
> > successfully using the odbcad32.exe in the windows\syswow64 folder.
> > But when I deploy a report which I designed on my 32 bit development machine
> > where all is running correctly, and I run the report on the server, it
> > cannot find the datasource.
> >
> > I think it has the same reason why I cannot see the MyODBC driver in the
> > normal ODBC Configuration Manager in the Administrative Tools.
> > Is there a possiblity to do that anyway'
> >
> > Thank you and greetings from Switzerland
> > Thomas
>

64 bit ntwdblib.dll

We are currently installing SQL Server 2005 on 32 bit platforms as well as
EM64T platforms. In addition to accessing it via OLE DB and ODBC, we also
still use the API Library which requires ntwdblib.dll. This is not included
with SQL Server 2005 and is identified as one of the deprecated features
that will be dropped completely in a future release. Furthermore, MS goes
to say that you need to copy the ntwdblib.dll from a previous version of SQL
Server to get it to work. This works fine on the 32 bit platforms since we
have SQL Server 2000. However, on the EM64T platform there is no previous
64 bit version since the 64 bit version of SQL Server 2000 was only
supported on the Itanium processor. Is there a way to use SQL Server 2005 in
64 bit mode and access it from the API Library interface?
Michael F. Parenteau
SAC MRI
Unisys
Very simple, there is no 64 bit version of DB-Lib, only 16 and 32-bit.
-GertD
"MParenteau" <michael.parenteau@.unisys.com> wrote in message
news:dvfa90$opd$1@.si05.rsvl.unisys.com...
> We are currently installing SQL Server 2005 on 32 bit platforms as well as
> EM64T platforms. In addition to accessing it via OLE DB and ODBC, we also
> still use the API Library which requires ntwdblib.dll. This is not
> included with SQL Server 2005 and is identified as one of the deprecated
> features that will be dropped completely in a future release.
> Furthermore, MS goes to say that you need to copy the ntwdblib.dll from a
> previous version of SQL Server to get it to work. This works fine on the
> 32 bit platforms since we have SQL Server 2000. However, on the EM64T
> platform there is no previous 64 bit version since the 64 bit version of
> SQL Server 2000 was only supported on the Itanium processor. Is there a
> way to use SQL Server 2005 in 64 bit mode and access it from the API
> Library interface?
> Michael F. Parenteau
> SAC MRI
> Unisys
>

64 bit ntwdblib.dll

We are currently installing SQL Server 2005 on 32 bit platforms as well as
EM64T platforms. In addition to accessing it via OLE DB and ODBC, we also
still use the API Library which requires ntwdblib.dll. This is not included
with SQL Server 2005 and is identified as one of the deprecated features
that will be dropped completely in a future release. Furthermore, MS goes
to say that you need to copy the ntwdblib.dll from a previous version of SQL
Server to get it to work. This works fine on the 32 bit platforms since we
have SQL Server 2000. However, on the EM64T platform there is no previous
64 bit version since the 64 bit version of SQL Server 2000 was only
supported on the Itanium processor. Is there a way to use SQL Server 2005 in
64 bit mode and access it from the API Library interface?
Michael F. Parenteau
SAC MRI
UnisysVery simple, there is no 64 bit version of DB-Lib, only 16 and 32-bit.
-GertD
"MParenteau" <michael.parenteau@.unisys.com> wrote in message
news:dvfa90$opd$1@.si05.rsvl.unisys.com...
> We are currently installing SQL Server 2005 on 32 bit platforms as well as
> EM64T platforms. In addition to accessing it via OLE DB and ODBC, we also
> still use the API Library which requires ntwdblib.dll. This is not
> included with SQL Server 2005 and is identified as one of the deprecated
> features that will be dropped completely in a future release.
> Furthermore, MS goes to say that you need to copy the ntwdblib.dll from a
> previous version of SQL Server to get it to work. This works fine on the
> 32 bit platforms since we have SQL Server 2000. However, on the EM64T
> platform there is no previous 64 bit version since the 64 bit version of
> SQL Server 2000 was only supported on the Itanium processor. Is there a
> way to use SQL Server 2005 in 64 bit mode and access it from the API
> Library interface?
> Michael F. Parenteau
> SAC MRI
> Unisys
>

64 bit ntwdblib.dll

We are currently installing SQL Server 2005 on 32 bit platforms as well as
EM64T platforms. In addition to accessing it via OLE DB and ODBC, we also
still use the API Library which requires ntwdblib.dll. This is not included
with SQL Server 2005 and is identified as one of the deprecated features
that will be dropped completely in a future release. Furthermore, MS goes
to say that you need to copy the ntwdblib.dll from a previous version of SQL
Server to get it to work. This works fine on the 32 bit platforms since we
have SQL Server 2000. However, on the EM64T platform there is no previous
64 bit version since the 64 bit version of SQL Server 2000 was only
supported on the Itanium processor. Is there a way to use SQL Server 2005 in
64 bit mode and access it from the API Library interface?
Michael F. Parenteau
SAC MRI
UnisysVery simple, there is no 64 bit version of DB-Lib, only 16 and 32-bit.
-GertD
"MParenteau" <michael.parenteau@.unisys.com> wrote in message
news:dvfa90$opd$1@.si05.rsvl.unisys.com...
> We are currently installing SQL Server 2005 on 32 bit platforms as well as
> EM64T platforms. In addition to accessing it via OLE DB and ODBC, we also
> still use the API Library which requires ntwdblib.dll. This is not
> included with SQL Server 2005 and is identified as one of the deprecated
> features that will be dropped completely in a future release.
> Furthermore, MS goes to say that you need to copy the ntwdblib.dll from a
> previous version of SQL Server to get it to work. This works fine on the
> 32 bit platforms since we have SQL Server 2000. However, on the EM64T
> platform there is no previous 64 bit version since the 64 bit version of
> SQL Server 2000 was only supported on the Itanium processor. Is there a
> way to use SQL Server 2005 in 64 bit mode and access it from the API
> Library interface?
> Michael F. Parenteau
> SAC MRI
> Unisys
>

64 Bit MSDASQL.DLL

Is microsoft going to provide 64 bit version of MSDASQL ( OLEDB Wraper for ODBC) in future? This was working great while accessing Data from IBM AS/400 on Iseries from 32 bit sql 2000. Now, it's all screwed up with rediculously slow OLEDB both from MS and IBM. I wonder if any of these guys really care!

Yes, the 64-bit version (both x64 and ia64) of msdasql.dll will be released very soon.

Ming (MDAC Team, Microsoft).

|||

Ming,

We are in great need of a verion of msdasql.dll for x64 as well. Our current code is dependent on it while at the same time we are in the midst of a large SQL 2005 x64 rollout and have been tripped up by the lack of msdasql.dll support in 64 bit. Do you have any idea how soon it will be out or if there are ways to get it sooner rather than later?

Thank you in advance,

Mark

|||

Ming,

Any idea when this might be? I am in need of this as well.

Thanks.

|||

+1

I need this as well...

|||

In case anyone cares. We are also in great need of this release. In our investigation of this issue, I received the following answer through another resouce. The MDAC team might want to confirm:

The MDAC team is going to release 64 MSDASQL..."when Longhorn is released, which is the new version of Windows. I've read that Longhorn won't be out until 3rd or 4th quarter, so we'll have to investigate other avenues."

|||

64-bit MSDASQL (both AMD64 and IA64) will be released in Windows Longhorn Server Beta 3 and Windows Vista SP1.

Pak-Ming Cheung,

MDAC Team, MSFT.

|||Is there any way we can get a copy of X64 MSDASQL.DLL now?|||...I am needing this as well. Any possibility to get the x64 msdasql.dll earlier than with vista sp 1 would be very much appreciated!|||How soon is soon? Anxiously waiting...|||

Interesting. It was my understanding that this technology had been deprecated.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/mdacsdk/htm/mdac_deprecated_components.asp

|||

Well, Longhorn Beta 3 is out, but I don't see an updated MSDQSQL.dll download. Will the 64-bit MSDASQL.dll be available as a separate download? I don't want to have to download the immense Longhorn and take up a test server trying to extract the single DLL.

This lack of 64-bit compatibility is delaying a production implementation for us.

Thanks!

|||

Well, Longhorn Beta 3 is our but I don't see an updated MSDASQL.dll download. Will the 64-bit version of MSDQSQL.dll be a separate download? I do not want to download the immens Longhorn to simply install and extract a single DLL.

This lack of 64-bit availability is delaying a production implementation for us.

Thanks!

|||

Well, Longhorn Beta 3 is our but I don't see an updated MSDASQL.dll download. Will the 64-bit version of MSDQSQL.dll be a separate download? I do not want to download the immense Longhorn to simply install and extract a single DLL.

This lack of 64-bit availability is delaying a production implementation for us.

Thanks!

P.S. I've tried posting this 4 times and MSDN keeps giving me errors. Hope this posts.

|||

Is there any update since April? I can not connect 64-bit SQL Server 2005 to SQL Server 6.5. As far as 6.5 is not supported by native SQL client, ODBC is the only way to make a direct connection.

64 Bit MSDASQL.DLL

Is microsoft going to provide 64 bit version of MSDASQL ( OLEDB Wraper for ODBC) in future? This was working great while accessing Data from IBM AS/400 on Iseries from 32 bit sql 2000. Now, it's all screwed up with rediculously slow OLEDB both from MS and IBM. I wonder if any of these guys really care!

Yes, the 64-bit version (both x64 and ia64) of msdasql.dll will be released very soon.

Ming (MDAC Team, Microsoft).

|||

Ming,

We are in great need of a verion of msdasql.dll for x64 as well. Our current code is dependent on it while at the same time we are in the midst of a large SQL 2005 x64 rollout and have been tripped up by the lack of msdasql.dll support in 64 bit. Do you have any idea how soon it will be out or if there are ways to get it sooner rather than later?

Thank you in advance,

Mark

|||

Ming,

Any idea when this might be? I am in need of this as well.

Thanks.

|||

+1

I need this as well...

|||

In case anyone cares. We are also in great need of this release. In our investigation of this issue, I received the following answer through another resouce. The MDAC team might want to confirm:

The MDAC team is going to release 64 MSDASQL..."when Longhorn is released, which is the new version of Windows. I've read that Longhorn won't be out until 3rd or 4th quarter, so we'll have to investigate other avenues."

|||

64-bit MSDASQL (both AMD64 and IA64) will be released in Windows Longhorn Server Beta 3 and Windows Vista SP1.

Pak-Ming Cheung,

MDAC Team, MSFT.

|||Is there any way we can get a copy of X64 MSDASQL.DLL now?|||...I am needing this as well. Any possibility to get the x64 msdasql.dll earlier than with vista sp 1 would be very much appreciated!|||How soon is soon? Anxiously waiting...|||

Interesting. It was my understanding that this technology had been deprecated.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/mdacsdk/htm/mdac_deprecated_components.asp

|||

Well, Longhorn Beta 3 is out, but I don't see an updated MSDQSQL.dll download. Will the 64-bit MSDASQL.dll be available as a separate download? I don't want to have to download the immense Longhorn and take up a test server trying to extract the single DLL.

This lack of 64-bit compatibility is delaying a production implementation for us.

Thanks!

|||

Well, Longhorn Beta 3 is our but I don't see an updated MSDASQL.dll download. Will the 64-bit version of MSDQSQL.dll be a separate download? I do not want to download the immens Longhorn to simply install and extract a single DLL.

This lack of 64-bit availability is delaying a production implementation for us.

Thanks!

|||

Well, Longhorn Beta 3 is our but I don't see an updated MSDASQL.dll download. Will the 64-bit version of MSDQSQL.dll be a separate download? I do not want to download the immense Longhorn to simply install and extract a single DLL.

This lack of 64-bit availability is delaying a production implementation for us.

Thanks!

P.S. I've tried posting this 4 times and MSDN keeps giving me errors. Hope this posts.

|||

Is there any update since April? I can not connect 64-bit SQL Server 2005 to SQL Server 6.5. As far as 6.5 is not supported by native SQL client, ODBC is the only way to make a direct connection.

64 Bit MSDASQL.DLL

Is microsoft going to provide 64 bit version of MSDASQL ( OLEDB Wraper for ODBC) in future? This was working great while accessing Data from IBM AS/400 on Iseries from 32 bit sql 2000. Now, it's all screwed up with rediculously slow OLEDB both from MS and IBM. I wonder if any of these guys really care!

Yes, the 64-bit version (both x64 and ia64) of msdasql.dll will be released very soon.

Ming (MDAC Team, Microsoft).

|||

Ming,

We are in great need of a verion of msdasql.dll for x64 as well. Our current code is dependent on it while at the same time we are in the midst of a large SQL 2005 x64 rollout and have been tripped up by the lack of msdasql.dll support in 64 bit. Do you have any idea how soon it will be out or if there are ways to get it sooner rather than later?

Thank you in advance,

Mark

|||

Ming,

Any idea when this might be? I am in need of this as well.

Thanks.

|||

+1

I need this as well...

|||

In case anyone cares. We are also in great need of this release. In our investigation of this issue, I received the following answer through another resouce. The MDAC team might want to confirm:

The MDAC team is going to release 64 MSDASQL..."when Longhorn is released, which is the new version of Windows. I've read that Longhorn won't be out until 3rd or 4th quarter, so we'll have to investigate other avenues."

|||

64-bit MSDASQL (both AMD64 and IA64) will be released in Windows Longhorn Server Beta 3 and Windows Vista SP1.

Pak-Ming Cheung,

MDAC Team, MSFT.

|||Is there any way we can get a copy of X64 MSDASQL.DLL now?|||...I am needing this as well. Any possibility to get the x64 msdasql.dll earlier than with vista sp 1 would be very much appreciated!|||How soon is soon? Anxiously waiting...|||

Interesting. It was my understanding that this technology had been deprecated.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/mdacsdk/htm/mdac_deprecated_components.asp

|||

Well, Longhorn Beta 3 is out, but I don't see an updated MSDQSQL.dll download. Will the 64-bit MSDASQL.dll be available as a separate download? I don't want to have to download the immense Longhorn and take up a test server trying to extract the single DLL.

This lack of 64-bit compatibility is delaying a production implementation for us.

Thanks!

|||

Well, Longhorn Beta 3 is our but I don't see an updated MSDASQL.dll download. Will the 64-bit version of MSDQSQL.dll be a separate download? I do not want to download the immens Longhorn to simply install and extract a single DLL.

This lack of 64-bit availability is delaying a production implementation for us.

Thanks!

|||

Well, Longhorn Beta 3 is our but I don't see an updated MSDASQL.dll download. Will the 64-bit version of MSDQSQL.dll be a separate download? I do not want to download the immense Longhorn to simply install and extract a single DLL.

This lack of 64-bit availability is delaying a production implementation for us.

Thanks!

P.S. I've tried posting this 4 times and MSDN keeps giving me errors. Hope this posts.

|||

Is there any update since April? I can not connect 64-bit SQL Server 2005 to SQL Server 6.5. As far as 6.5 is not supported by native SQL client, ODBC is the only way to make a direct connection.

64 Bit MSDASQL.DLL

Is microsoft going to provide 64 bit version of MSDASQL ( OLEDB Wraper for ODBC) in future? This was working great while accessing Data from IBM AS/400 on Iseries from 32 bit sql 2000. Now, it's all screwed up with rediculously slow OLEDB both from MS and IBM. I wonder if any of these guys really care!

Yes, the 64-bit version (both x64 and ia64) of msdasql.dll will be released very soon.

Ming (MDAC Team, Microsoft).

|||

Ming,

We are in great need of a verion of msdasql.dll for x64 as well. Our current code is dependent on it while at the same time we are in the midst of a large SQL 2005 x64 rollout and have been tripped up by the lack of msdasql.dll support in 64 bit. Do you have any idea how soon it will be out or if there are ways to get it sooner rather than later?

Thank you in advance,

Mark

|||

Ming,

Any idea when this might be? I am in need of this as well.

Thanks.

|||

+1

I need this as well...

|||

In case anyone cares. We are also in great need of this release. In our investigation of this issue, I received the following answer through another resouce. The MDAC team might want to confirm:

The MDAC team is going to release 64 MSDASQL..."when Longhorn is released, which is the new version of Windows. I've read that Longhorn won't be out until 3rd or 4th quarter, so we'll have to investigate other avenues."

|||

64-bit MSDASQL (both AMD64 and IA64) will be released in Windows Longhorn Server Beta 3 and Windows Vista SP1.

Pak-Ming Cheung,

MDAC Team, MSFT.

|||Is there any way we can get a copy of X64 MSDASQL.DLL now?|||...I am needing this as well. Any possibility to get the x64 msdasql.dll earlier than with vista sp 1 would be very much appreciated!|||How soon is soon? Anxiously waiting...|||

Interesting. It was my understanding that this technology had been deprecated.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/mdacsdk/htm/mdac_deprecated_components.asp

|||

Well, Longhorn Beta 3 is out, but I don't see an updated MSDQSQL.dll download. Will the 64-bit MSDASQL.dll be available as a separate download? I don't want to have to download the immense Longhorn and take up a test server trying to extract the single DLL.

This lack of 64-bit compatibility is delaying a production implementation for us.

Thanks!

|||

Well, Longhorn Beta 3 is our but I don't see an updated MSDASQL.dll download. Will the 64-bit version of MSDQSQL.dll be a separate download? I do not want to download the immens Longhorn to simply install and extract a single DLL.

This lack of 64-bit availability is delaying a production implementation for us.

Thanks!

|||

Well, Longhorn Beta 3 is our but I don't see an updated MSDASQL.dll download. Will the 64-bit version of MSDQSQL.dll be a separate download? I do not want to download the immense Longhorn to simply install and extract a single DLL.

This lack of 64-bit availability is delaying a production implementation for us.

Thanks!

P.S. I've tried posting this 4 times and MSDN keeps giving me errors. Hope this posts.

|||

Is there any update since April? I can not connect 64-bit SQL Server 2005 to SQL Server 6.5. As far as 6.5 is not supported by native SQL client, ODBC is the only way to make a direct connection.

64 Bit MSDASQL.DLL

Is microsoft going to provide 64 bit version of MSDASQL ( OLEDB Wraper for ODBC) in future? This was working great while accessing Data from IBM AS/400 on Iseries from 32 bit sql 2000. Now, it's all screwed up with rediculously slow OLEDB both from MS and IBM. I wonder if any of these guys really care!

Yes, the 64-bit version (both x64 and ia64) of msdasql.dll will be released very soon.

Ming (MDAC Team, Microsoft).

|||

Ming,

We are in great need of a verion of msdasql.dll for x64 as well. Our current code is dependent on it while at the same time we are in the midst of a large SQL 2005 x64 rollout and have been tripped up by the lack of msdasql.dll support in 64 bit. Do you have any idea how soon it will be out or if there are ways to get it sooner rather than later?

Thank you in advance,

Mark

|||

Ming,

Any idea when this might be? I am in need of this as well.

Thanks.

|||

+1

I need this as well...

|||

In case anyone cares. We are also in great need of this release. In our investigation of this issue, I received the following answer through another resouce. The MDAC team might want to confirm:

The MDAC team is going to release 64 MSDASQL..."when Longhorn is released, which is the new version of Windows. I've read that Longhorn won't be out until 3rd or 4th quarter, so we'll have to investigate other avenues."

|||

64-bit MSDASQL (both AMD64 and IA64) will be released in Windows Longhorn Server Beta 3 and Windows Vista SP1.

Pak-Ming Cheung,

MDAC Team, MSFT.

|||Is there any way we can get a copy of X64 MSDASQL.DLL now?|||...I am needing this as well. Any possibility to get the x64 msdasql.dll earlier than with vista sp 1 would be very much appreciated!|||How soon is soon? Anxiously waiting...|||

Interesting. It was my understanding that this technology had been deprecated.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/mdacsdk/htm/mdac_deprecated_components.asp

|||

Well, Longhorn Beta 3 is out, but I don't see an updated MSDQSQL.dll download. Will the 64-bit MSDASQL.dll be available as a separate download? I don't want to have to download the immense Longhorn and take up a test server trying to extract the single DLL.

This lack of 64-bit compatibility is delaying a production implementation for us.

Thanks!

|||

Well, Longhorn Beta 3 is our but I don't see an updated MSDASQL.dll download. Will the 64-bit version of MSDQSQL.dll be a separate download? I do not want to download the immens Longhorn to simply install and extract a single DLL.

This lack of 64-bit availability is delaying a production implementation for us.

Thanks!

|||

Well, Longhorn Beta 3 is our but I don't see an updated MSDASQL.dll download. Will the 64-bit version of MSDQSQL.dll be a separate download? I do not want to download the immense Longhorn to simply install and extract a single DLL.

This lack of 64-bit availability is delaying a production implementation for us.

Thanks!

P.S. I've tried posting this 4 times and MSDN keeps giving me errors. Hope this posts.

|||

Is there any update since April? I can not connect 64-bit SQL Server 2005 to SQL Server 6.5. As far as 6.5 is not supported by native SQL client, ODBC is the only way to make a direct connection.

64 Bit MSDASQL.DLL

Is microsoft going to provide 64 bit version of MSDASQL ( OLEDB Wraper for ODBC) in future? This was working great while accessing Data from IBM AS/400 on Iseries from 32 bit sql 2000. Now, it's all screwed up with rediculously slow OLEDB both from MS and IBM. I wonder if any of these guys really care!

Yes, the 64-bit version (both x64 and ia64) of msdasql.dll will be released very soon.

Ming (MDAC Team, Microsoft).

|||

Ming,

We are in great need of a verion of msdasql.dll for x64 as well. Our current code is dependent on it while at the same time we are in the midst of a large SQL 2005 x64 rollout and have been tripped up by the lack of msdasql.dll support in 64 bit. Do you have any idea how soon it will be out or if there are ways to get it sooner rather than later?

Thank you in advance,

Mark

|||

Ming,

Any idea when this might be? I am in need of this as well.

Thanks.

|||

+1

I need this as well...

|||

In case anyone cares. We are also in great need of this release. In our investigation of this issue, I received the following answer through another resouce. The MDAC team might want to confirm:

The MDAC team is going to release 64 MSDASQL..."when Longhorn is released, which is the new version of Windows. I've read that Longhorn won't be out until 3rd or 4th quarter, so we'll have to investigate other avenues."

|||

64-bit MSDASQL (both AMD64 and IA64) will be released in Windows Longhorn Server Beta 3 and Windows Vista SP1.

Pak-Ming Cheung,

MDAC Team, MSFT.

|||Is there any way we can get a copy of X64 MSDASQL.DLL now?|||...I am needing this as well. Any possibility to get the x64 msdasql.dll earlier than with vista sp 1 would be very much appreciated!|||How soon is soon? Anxiously waiting...|||

Interesting. It was my understanding that this technology had been deprecated.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/mdacsdk/htm/mdac_deprecated_components.asp

|||

Well, Longhorn Beta 3 is out, but I don't see an updated MSDQSQL.dll download. Will the 64-bit MSDASQL.dll be available as a separate download? I don't want to have to download the immense Longhorn and take up a test server trying to extract the single DLL.

This lack of 64-bit compatibility is delaying a production implementation for us.

Thanks!

|||

Well, Longhorn Beta 3 is our but I don't see an updated MSDASQL.dll download. Will the 64-bit version of MSDQSQL.dll be a separate download? I do not want to download the immens Longhorn to simply install and extract a single DLL.

This lack of 64-bit availability is delaying a production implementation for us.

Thanks!

|||

Well, Longhorn Beta 3 is our but I don't see an updated MSDASQL.dll download. Will the 64-bit version of MSDQSQL.dll be a separate download? I do not want to download the immense Longhorn to simply install and extract a single DLL.

This lack of 64-bit availability is delaying a production implementation for us.

Thanks!

P.S. I've tried posting this 4 times and MSDN keeps giving me errors. Hope this posts.

|||

Is there any update since April? I can not connect 64-bit SQL Server 2005 to SQL Server 6.5. As far as 6.5 is not supported by native SQL client, ODBC is the only way to make a direct connection.

64 Bit MSDASQL.DLL

Is microsoft going to provide 64 bit version of MSDASQL ( OLEDB Wraper for ODBC) in future? This was working great while accessing Data from IBM AS/400 on Iseries from 32 bit sql 2000. Now, it's all screwed up with rediculously slow OLEDB both from MS and IBM. I wonder if any of these guys really care!

Yes, the 64-bit version (both x64 and ia64) of msdasql.dll will be released very soon.

Ming (MDAC Team, Microsoft).

|||

Ming,

We are in great need of a verion of msdasql.dll for x64 as well. Our current code is dependent on it while at the same time we are in the midst of a large SQL 2005 x64 rollout and have been tripped up by the lack of msdasql.dll support in 64 bit. Do you have any idea how soon it will be out or if there are ways to get it sooner rather than later?

Thank you in advance,

Mark

|||

Ming,

Any idea when this might be? I am in need of this as well.

Thanks.

|||

+1

I need this as well...

|||

In case anyone cares. We are also in great need of this release. In our investigation of this issue, I received the following answer through another resouce. The MDAC team might want to confirm:

The MDAC team is going to release 64 MSDASQL..."when Longhorn is released, which is the new version of Windows. I've read that Longhorn won't be out until 3rd or 4th quarter, so we'll have to investigate other avenues."

|||

64-bit MSDASQL (both AMD64 and IA64) will be released in Windows Longhorn Server Beta 3 and Windows Vista SP1.

Pak-Ming Cheung,

MDAC Team, MSFT.

|||Is there any way we can get a copy of X64 MSDASQL.DLL now?|||...I am needing this as well. Any possibility to get the x64 msdasql.dll earlier than with vista sp 1 would be very much appreciated!|||How soon is soon? Anxiously waiting...|||

Interesting. It was my understanding that this technology had been deprecated.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/mdacsdk/htm/mdac_deprecated_components.asp

|||

Well, Longhorn Beta 3 is out, but I don't see an updated MSDQSQL.dll download. Will the 64-bit MSDASQL.dll be available as a separate download? I don't want to have to download the immense Longhorn and take up a test server trying to extract the single DLL.

This lack of 64-bit compatibility is delaying a production implementation for us.

Thanks!

|||

Well, Longhorn Beta 3 is our but I don't see an updated MSDASQL.dll download. Will the 64-bit version of MSDQSQL.dll be a separate download? I do not want to download the immens Longhorn to simply install and extract a single DLL.

This lack of 64-bit availability is delaying a production implementation for us.

Thanks!

|||

Well, Longhorn Beta 3 is our but I don't see an updated MSDASQL.dll download. Will the 64-bit version of MSDQSQL.dll be a separate download? I do not want to download the immense Longhorn to simply install and extract a single DLL.

This lack of 64-bit availability is delaying a production implementation for us.

Thanks!

P.S. I've tried posting this 4 times and MSDN keeps giving me errors. Hope this posts.

|||

Is there any update since April? I can not connect 64-bit SQL Server 2005 to SQL Server 6.5. As far as 6.5 is not supported by native SQL client, ODBC is the only way to make a direct connection.

64 Bit MSDASQL.DLL

Is microsoft going to provide 64 bit version of MSDASQL ( OLEDB Wraper for ODBC) in future? This was working great while accessing Data from IBM AS/400 on Iseries from 32 bit sql 2000. Now, it's all screwed up with rediculously slow OLEDB both from MS and IBM. I wonder if any of these guys really care!

Yes, the 64-bit version (both x64 and ia64) of msdasql.dll will be released very soon.

Ming (MDAC Team, Microsoft).

|||

Ming,

We are in great need of a verion of msdasql.dll for x64 as well. Our current code is dependent on it while at the same time we are in the midst of a large SQL 2005 x64 rollout and have been tripped up by the lack of msdasql.dll support in 64 bit. Do you have any idea how soon it will be out or if there are ways to get it sooner rather than later?

Thank you in advance,

Mark

|||

Ming,

Any idea when this might be? I am in need of this as well.

Thanks.

|||

+1

I need this as well...

|||

In case anyone cares. We are also in great need of this release. In our investigation of this issue, I received the following answer through another resouce. The MDAC team might want to confirm:

The MDAC team is going to release 64 MSDASQL..."when Longhorn is released, which is the new version of Windows. I've read that Longhorn won't be out until 3rd or 4th quarter, so we'll have to investigate other avenues."

|||

64-bit MSDASQL (both AMD64 and IA64) will be released in Windows Longhorn Server Beta 3 and Windows Vista SP1.

Pak-Ming Cheung,

MDAC Team, MSFT.

|||Is there any way we can get a copy of X64 MSDASQL.DLL now?|||...I am needing this as well. Any possibility to get the x64 msdasql.dll earlier than with vista sp 1 would be very much appreciated!|||How soon is soon? Anxiously waiting...|||

Interesting. It was my understanding that this technology had been deprecated.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/mdacsdk/htm/mdac_deprecated_components.asp

|||

Well, Longhorn Beta 3 is out, but I don't see an updated MSDQSQL.dll download. Will the 64-bit MSDASQL.dll be available as a separate download? I don't want to have to download the immense Longhorn and take up a test server trying to extract the single DLL.

This lack of 64-bit compatibility is delaying a production implementation for us.

Thanks!

|||

Well, Longhorn Beta 3 is our but I don't see an updated MSDASQL.dll download. Will the 64-bit version of MSDQSQL.dll be a separate download? I do not want to download the immens Longhorn to simply install and extract a single DLL.

This lack of 64-bit availability is delaying a production implementation for us.

Thanks!

|||

Well, Longhorn Beta 3 is our but I don't see an updated MSDASQL.dll download. Will the 64-bit version of MSDQSQL.dll be a separate download? I do not want to download the immense Longhorn to simply install and extract a single DLL.

This lack of 64-bit availability is delaying a production implementation for us.

Thanks!

P.S. I've tried posting this 4 times and MSDN keeps giving me errors. Hope this posts.

|||

Is there any update since April? I can not connect 64-bit SQL Server 2005 to SQL Server 6.5. As far as 6.5 is not supported by native SQL client, ODBC is the only way to make a direct connection.

5041. MODIFY FILE failed. File '%.*ls' does not exist.

I am trying to change the file growth of a database file by 10% and I get an error message.
Microsoft SQL-DMO (ODBC SQL-STATE 42000)
Error 5041 MODIFY FILE failed. File '%.*ls' does not exist.
All I know is that it is an error of severity 16.
Can you post the SQL command you executed?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Kostas Kourtides" <Kostas Kourtides@.discussions.microsoft.com> wrote in message
news:1E944558-4968-4249-AC6B-9B9FCF87AB25@.microsoft.com...
> I am trying to change the file growth of a database file by 10% and I get an error message.
> Microsoft SQL-DMO (ODBC SQL-STATE 42000)
> Error 5041 MODIFY FILE failed. File '%.*ls' does not exist.
> All I know is that it is an error of severity 16.
|||The issue has been solved by changing the names of the filenames.
Thanks for the interest.
"Tibor Karaszi" wrote:

> Can you post the SQL command you executed?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Kostas Kourtides" <Kostas Kourtides@.discussions.microsoft.com> wrote in message
> news:1E944558-4968-4249-AC6B-9B9FCF87AB25@.microsoft.com...
>
>

5041. MODIFY FILE failed. File '%.*ls' does not exist.

I am trying to change the file growth of a database file by 10% and I get an error message.
Microsoft SQL-DMO (ODBC SQL-STATE 42000)
Error 5041 MODIFY FILE failed. File '%.*ls' does not exist.
All I know is that it is an error of severity 16.Can you post the SQL command you executed?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Kostas Kourtides" <Kostas Kourtides@.discussions.microsoft.com> wrote in message
news:1E944558-4968-4249-AC6B-9B9FCF87AB25@.microsoft.com...
> I am trying to change the file growth of a database file by 10% and I get an error message.
> Microsoft SQL-DMO (ODBC SQL-STATE 42000)
> Error 5041 MODIFY FILE failed. File '%.*ls' does not exist.
> All I know is that it is an error of severity 16.|||The issue has been solved by changing the names of the filenames.
Thanks for the interest.
"Tibor Karaszi" wrote:
> Can you post the SQL command you executed?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Kostas Kourtides" <Kostas Kourtides@.discussions.microsoft.com> wrote in message
> news:1E944558-4968-4249-AC6B-9B9FCF87AB25@.microsoft.com...
> > I am trying to change the file growth of a database file by 10% and I get an error message.
> >
> > Microsoft SQL-DMO (ODBC SQL-STATE 42000)
> >
> > Error 5041 MODIFY FILE failed. File '%.*ls' does not exist.
> >
> > All I know is that it is an error of severity 16.
>
>

5041. MODIFY FILE failed. File '%.*ls' does not exist.

I am trying to change the file growth of a database file by 10% and I get an
error message.
Microsoft SQL-DMO (ODBC SQL-STATE 42000)
Error 5041 MODIFY FILE failed. File '%.*ls' does not exist.
All I know is that it is an error of severity 16.Can you post the SQL command you executed?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Kostas Kourtides" <Kostas Kourtides@.discussions.microsoft.com> wrote in mes
sage
news:1E944558-4968-4249-AC6B-9B9FCF87AB25@.microsoft.com...
> I am trying to change the file growth of a database file by 10% and I get
an error message.
> Microsoft SQL-DMO (ODBC SQL-STATE 42000)
> Error 5041 MODIFY FILE failed. File '%.*ls' does not exist.
> All I know is that it is an error of severity 16.|||The issue has been solved by changing the names of the filenames.
Thanks for the interest.
"Tibor Karaszi" wrote:

> Can you post the SQL command you executed?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Kostas Kourtides" <Kostas Kourtides@.discussions.microsoft.com> wrote in m
essage
> news:1E944558-4968-4249-AC6B-9B9FCF87AB25@.microsoft.com...
>
>

3753 Provider is not specified and there is no designated default provider.

i just bought a brand new server and put windows server 2003 x64 sp1 on it then put sql server 2000 sp4 on that and set up a trusted odbc connection. however, it gave me the following error:
SQLSTATE:IM002, diagnosis:[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
so i made a vbs file (adodb.connection) to see if that could connect to it and it came out with this on the err.number err.description
err.number = 3753
err.description = Provider is not specified and there is no designated default provider.
this even happened when i tried to use a dsnless connection to the old server machine so i dont know if its a problem with whatever is trying to use the connection or odbc or what. please can someone tell me what can i do to fix this problem?
i dont know if this is just a missing driver or something, odbc only has "SQL Server" in the list (C:\WINDOWS\System32\SQLSRV32.dll i think) wheras all my other machines have something like 25 or 30 drivers in the list, but "SQL Server" is the one im trying to use anyway..
edit: iis is not installed on this new server. other machines (with iis and vbs) can connect using dsnless or dsn with uid and pwd. also i think asp might have a different err.number for this problem than vbs' 3753

Due to the length of time since this issue was posted, I'm marking it as resolved. If you're still in need of help, please respond here.

Paul

3753 Provider is not specified and there is no designated default provider.

i just bought a brand new server and put windows server 2003 x64 sp1 on it then put sql server 2000 sp4 on that and set up a trusted odbc connection. however, it gave me the following error:
SQLSTATE:IM002, diagnosis:[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
so i made a vbs file (adodb.connection) to see if that could connect to it and it came out with this on the err.number err.description
err.number = 3753
err.description = Provider is not specified and there is no designated default provider.
this even happened when i tried to use a dsnless connection to the old server machine so i dont know if its a problem with whatever is trying to use the connection or odbc or what. please can someone tell me what can i do to fix this problem?
i dont know if this is just a missing driver or something, odbc only has "SQL Server" in the list (C:\WINDOWS\System32\SQLSRV32.dll i think) wheras all my other machines have something like 25 or 30 drivers in the list, but "SQL Server" is the one im trying to use anyway..
edit: iis is not installed on this new server. other machines (with iis and vbs) can connect using dsnless or dsn with uid and pwd. also i think asp might have a different err.number for this problem than vbs' 3753

Due to the length of time since this issue was posted, I'm marking it as resolved. If you're still in need of help, please respond here.

Paul