Connecting to ODBC Connections with Report Services

I have just migrated from SQL 2000 to SQL 2005 and in the process upgraded to new hardware. I am now running SQL2005 (64 Bit) on Windows 2003 R2 (64 Bit). The problem is that when i deploy some reports to the new server that use ODBC to connect to the data, reporting services is erroring with :

Data source name not found and no default driver specified

The ODBC connections are set up exactly the same on the old server and the new server. Is it because it is looking for a 64 bit ODBC driver and not the 32 Bit one I have installed. If i go into the SysWOW64 and run the odbcad32.exe i can see the drivers and the connection. The connection test works fine from here.

Thanks

Has anyone got any ideas on this ?|||Did you find a resolution? I have the same problem.|||I am waiting for a company called Openlink to get back to me they are currently developing some drivers|||Thanks. My client is switching to 32-bit software to resolve this. Good luck.|||

Did anyone get this resolved? I am having the same problem. I fear I may have to revert back to the 32-Bit OS.

Any advice or suggestion are welcomed.

Thanks,

Andy

Connecting to ODBC Connections with Report Services

I have just migrated from SQL 2000 to SQL 2005 and in the process upgraded to new hardware. I am now running SQL2005 (64 Bit) on Windows 2003 R2 (64 Bit). The problem is that when i deploy some reports to the new server that use ODBC to connect to the data, reporting services is erroring with :

Data source name not found and no default driver specified

The ODBC connections are set up exactly the same on the old server and the new server. Is it because it is looking for a 64 bit ODBC driver and not the 32 Bit one I have installed. If i go into the SysWOW64 and run the odbcad32.exe i can see the drivers and the connection. The connection test works fine from here.

Thanks

Has anyone got any ideas on this ?|||Did you find a resolution? I have the same problem.|||I am waiting for a company called Openlink to get back to me they are currently developing some drivers|||Thanks. My client is switching to 32-bit software to resolve this. Good luck.|||

Did anyone get this resolved? I am having the same problem. I fear I may have to revert back to the 32-Bit OS.

Any advice or suggestion are welcomed.

Thanks,

Andy

Connecting to ODBC Connections with Report Services

I have just migrated from SQL 2000 to SQL 2005 and in the process upgraded to new hardware. I am now running SQL2005 (64 Bit) on Windows 2003 R2 (64 Bit). The problem is that when i deploy some reports to the new server that use ODBC to connect to the data, reporting services is erroring with :

Data source name not found and no default driver specified

The ODBC connections are set up exactly the same on the old server and the new server. Is it because it is looking for a 64 bit ODBC driver and not the 32 Bit one I have installed. If i go into the SysWOW64 and run the odbcad32.exe i can see the drivers and the connection. The connection test works fine from here.

Thanks

Has anyone got any ideas on this ?|||Did you find a resolution? I have the same problem.|||I am waiting for a company called Openlink to get back to me they are currently developing some drivers|||Thanks. My client is switching to 32-bit software to resolve this. Good luck.|||

Did anyone get this resolved? I am having the same problem. I fear I may have to revert back to the 32-Bit OS.

Any advice or suggestion are welcomed.

Thanks,

Andy

Connecting crdb_p2bbde.dll to Crystal Rpts v10

Our company just upgraded to Crystal Rpts v10 and I need to connect to a Paradox database. Crystal's online help saids to connect BDE paradox driver crdb_p2bbde.dll using a 3rd party software. Has anyone done this, thanks in advance.I'm having a similar issue. Back in March I upgraded some obscure CR8.5 reports that utilize both dBase and Paradox tables to CR10. No problem.

Yesterday I revisit these reports, and I repeatedly encounter "cannot load crdb_p2bbde.dll" errors. The dll is right where its supposed to be, in \Program Files\Common Files\Crystal Decisions\2.5\bin, where it has always been.

Where on Crystal's site did you see something that recommended a "third party software"?|||Hi,
I don't know if this will help but we had a similar problem with the advantage database and crdb_p2sads.dll, the problem was there was a file missing in the windows/system32 folder (Msvcp60.dll). Depending on your operating system this one may not get installed.

Hope this helps..
Daryl..

Connectectivity problem after Alias is created

I have an SQL 2000 DB that was upgraded from SQL7. I can connect to and work
with the 7 DB with out any problems. After I upgrade the DB to 2000 sp3 I
can connect to it through enterprise manger only on a workstation that does
not have an alias created to the SQL2000 server. The application we are
using against this DB requires an Alias to connect to the data. I have tried
using the server name -which works fine to connect to the SQL7 DB, I have
tried using IP address, & I have tried using the fully qualified domain name,
when creating the Alias. after the alias is created we can not connect to
the DB.
Civic wrote:
> I have an SQL 2000 DB that was upgraded from SQL7. I can connect to
> and work with the 7 DB with out any problems. After I upgrade the DB
> to 2000 sp3 I can connect to it through enterprise manger only on a
> workstation that does not have an alias created to the SQL2000
> server. The application we are using against this DB requires an
> Alias to connect to the data. I have tried using the server name
> -which works fine to connect to the SQL7 DB, I have tried using IP
> address, & I have tried using the fully qualified domain name, when
> creating the Alias. after the alias is created we can not connect to
> the DB.
Are you saying that you are creating an alias on the client using the
SQL Server 2000 Client Network Utility. You give the alias a name that
differs from the server name and are presumably using TCP/IP as the
protocol. When you try and connect to the 2000 server using the server
name, it works. However, when you connect to the server using the alias
name, you can not connect. If so, can you post your alias information as
you set it up.
Can you connect to SQL Server from Query nalyzer using the alias and
server name both?
David Gugick
Imceda Software
www.imceda.com
|||I created the Alias using SQL Server 2000 Client Network Utility I created
the Alias with the same name as our SQL server using TCPIP and the server
name ( I have also since then tried using the FQDN, and IP address for Server
Name) The initial alias cfg'd with server name works fine with the pre
upgrade SQL7 DB. After the Alias is created I can not connect to the SQL
database at all. Using query analyzer I can not connect to the lowercase
server name -populated by the Alias, or by browsing out to the server. I
lose all connectivity to the SQL server. After I remove the Alias I can once
again connect to the server.
"David Gugick" wrote:

> Civic wrote:
> Are you saying that you are creating an alias on the client using the
> SQL Server 2000 Client Network Utility. You give the alias a name that
> differs from the server name and are presumably using TCP/IP as the
> protocol. When you try and connect to the 2000 server using the server
> name, it works. However, when you connect to the server using the alias
> name, you can not connect. If so, can you post your alias information as
> you set it up.
> Can you connect to SQL Server from Query nalyzer using the alias and
> server name both?
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
|||Is your SQL 7 using Named Pipes or TCP/IP (Server Network Utility). I
believe Named Pipes was the default for SQL 7...
"Civic" <Civic@.discussions.microsoft.com> wrote in message
news:6FD4CF01-DB82-4CB2-9FA8-2ECEC5942441@.microsoft.com...[vbcol=seagreen]
>I created the Alias using SQL Server 2000 Client Network Utility I created
> the Alias with the same name as our SQL server using TCPIP and the server
> name ( I have also since then tried using the FQDN, and IP address for
> Server
> Name) The initial alias cfg'd with server name works fine with the pre
> upgrade SQL7 DB. After the Alias is created I can not connect to the SQL
> database at all. Using query analyzer I can not connect to the lowercase
> server name -populated by the Alias, or by browsing out to the server. I
> lose all connectivity to the SQL server. After I remove the Alias I can
> once
> again connect to the server.
> "David Gugick" wrote:
|||Civic wrote:
> I created the Alias using SQL Server 2000 Client Network Utility I
> created the Alias with the same name as our SQL server using TCPIP
> and the server name ( I have also since then tried using the FQDN,
> and IP address for Server Name) The initial alias cfg'd with server
> name works fine with the pre upgrade SQL7 DB. After the Alias is
> created I can not connect to the SQL database at all. Using query
> analyzer I can not connect to the lowercase server name -populated by
> the Alias, or by browsing out to the server. I lose all connectivity
> to the SQL server. After I remove the Alias I can once again connect
> to the server.
>
Why would you create an alias with the same name as the server? An alias
should have a different name... which is the point of an alias.
From BOL:
"In some cases, an instance of SQL Server may be configured to listen on
alternate network addresses. If this is done, client applications
connecting to that instance must explicitly specify the alternate
address. While applications could specify the alternate addresses on
each connection request, it is easier to use the Client Network utility
to set up an alias specifying the alternate addresses. Applications can
then specify the alias name in place of the server network name in their
connection requests."
Which seems to indicate you should be using a unique alias name that
differs from the server name.
David Gugick
Imceda Software
www.imceda.com
|||"David Gugick" wrote:

> Civic wrote:
> Why would you create an alias with the same name as the server? An alias
> should have a different name... which is the point of an alias.
>
> From BOL:
> "In some cases, an instance of SQL Server may be configured to listen on
> alternate network addresses. If this is done, client applications
> connecting to that instance must explicitly specify the alternate
> address. While applications could specify the alternate addresses on
> each connection request, it is easier to use the Client Network utility
> to set up an alias specifying the alternate addresses. Applications can
> then specify the alias name in place of the server network name in their
> connection requests."
> Which seems to indicate you should be using a unique alias name that
> differs from the server name.
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>

Connectectivity problem after Alias is created

I have an SQL 2000 DB that was upgraded from SQL7. I can connect to and wor
k
with the 7 DB with out any problems. After I upgrade the DB to 2000 sp3 I
can connect to it through enterprise manger only on a workstation that does
not have an alias created to the SQL2000 server. The application we are
using against this DB requires an Alias to connect to the data. I have trie
d
using the server name -which works fine to connect to the SQL7 DB, I have
tried using IP address, & I have tried using the fully qualified domain name
,
when creating the Alias. after the alias is created we can not connect to
the DB.Civic wrote:
> I have an SQL 2000 DB that was upgraded from SQL7. I can connect to
> and work with the 7 DB with out any problems. After I upgrade the DB
> to 2000 sp3 I can connect to it through enterprise manger only on a
> workstation that does not have an alias created to the SQL2000
> server. The application we are using against this DB requires an
> Alias to connect to the data. I have tried using the server name
> -which works fine to connect to the SQL7 DB, I have tried using IP
> address, & I have tried using the fully qualified domain name, when
> creating the Alias. after the alias is created we can not connect to
> the DB.
Are you saying that you are creating an alias on the client using the
SQL Server 2000 Client Network Utility. You give the alias a name that
differs from the server name and are presumably using TCP/IP as the
protocol. When you try and connect to the 2000 server using the server
name, it works. However, when you connect to the server using the alias
name, you can not connect. If so, can you post your alias information as
you set it up.
Can you connect to SQL Server from Query nalyzer using the alias and
server name both?
David Gugick
Imceda Software
www.imceda.com|||I created the Alias using SQL Server 2000 Client Network Utility I created
the Alias with the same name as our SQL server using TCPIP and the server
name ( I have also since then tried using the FQDN, and IP address for Serve
r
Name) The initial alias cfg'd with server name works fine with the pre
upgrade SQL7 DB. After the Alias is created I can not connect to the SQL
database at all. Using query analyzer I can not connect to the lowercase
server name -populated by the Alias, or by browsing out to the server. I
lose all connectivity to the SQL server. After I remove the Alias I can onc
e
again connect to the server.
"David Gugick" wrote:

> Civic wrote:
> Are you saying that you are creating an alias on the client using the
> SQL Server 2000 Client Network Utility. You give the alias a name that
> differs from the server name and are presumably using TCP/IP as the
> protocol. When you try and connect to the 2000 server using the server
> name, it works. However, when you connect to the server using the alias
> name, you can not connect. If so, can you post your alias information as
> you set it up.
> Can you connect to SQL Server from Query nalyzer using the alias and
> server name both?
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Is your SQL 7 using Named Pipes or TCP/IP (Server Network Utility). I
believe Named Pipes was the default for SQL 7...
"Civic" <Civic@.discussions.microsoft.com> wrote in message
news:6FD4CF01-DB82-4CB2-9FA8-2ECEC5942441@.microsoft.com...[vbcol=seagreen]
>I created the Alias using SQL Server 2000 Client Network Utility I created
> the Alias with the same name as our SQL server using TCPIP and the server
> name ( I have also since then tried using the FQDN, and IP address for
> Server
> Name) The initial alias cfg'd with server name works fine with the pre
> upgrade SQL7 DB. After the Alias is created I can not connect to the SQL
> database at all. Using query analyzer I can not connect to the lowercase
> server name -populated by the Alias, or by browsing out to the server. I
> lose all connectivity to the SQL server. After I remove the Alias I can
> once
> again connect to the server.
> "David Gugick" wrote:
>|||Civic wrote:
> I created the Alias using SQL Server 2000 Client Network Utility I
> created the Alias with the same name as our SQL server using TCPIP
> and the server name ( I have also since then tried using the FQDN,
> and IP address for Server Name) The initial alias cfg'd with server
> name works fine with the pre upgrade SQL7 DB. After the Alias is
> created I can not connect to the SQL database at all. Using query
> analyzer I can not connect to the lowercase server name -populated by
> the Alias, or by browsing out to the server. I lose all connectivity
> to the SQL server. After I remove the Alias I can once again connect
> to the server.
>
Why would you create an alias with the same name as the server? An alias
should have a different name... which is the point of an alias.
From BOL:
"In some cases, an instance of SQL Server may be configured to listen on
alternate network addresses. If this is done, client applications
connecting to that instance must explicitly specify the alternate
address. While applications could specify the alternate addresses on
each connection request, it is easier to use the Client Network utility
to set up an alias specifying the alternate addresses. Applications can
then specify the alias name in place of the server network name in their
connection requests."
Which seems to indicate you should be using a unique alias name that
differs from the server name.
David Gugick
Imceda Software
www.imceda.com|||"David Gugick" wrote:

> Civic wrote:
> Why would you create an alias with the same name as the server? An alias
> should have a different name... which is the point of an alias.
>
> From BOL:
> "In some cases, an instance of SQL Server may be configured to listen on
> alternate network addresses. If this is done, client applications
> connecting to that instance must explicitly specify the alternate
> address. While applications could specify the alternate addresses on
> each connection request, it is easier to use the Client Network utility
> to set up an alias specifying the alternate addresses. Applications can
> then specify the alias name in place of the server network name in their
> connection requests."
> Which seems to indicate you should be using a unique alias name that
> differs from the server name.
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>

Connectectivity problem after Alias is created

I have an SQL 2000 DB that was upgraded from SQL7. I can connect to and work
with the 7 DB with out any problems. After I upgrade the DB to 2000 sp3 I
can connect to it through enterprise manger only on a workstation that does
not have an alias created to the SQL2000 server. The application we are
using against this DB requires an Alias to connect to the data. I have tried
using the server name -which works fine to connect to the SQL7 DB, I have
tried using IP address, & I have tried using the fully qualified domain name,
when creating the Alias. after the alias is created we can not connect to
the DB.Civic wrote:
> I have an SQL 2000 DB that was upgraded from SQL7. I can connect to
> and work with the 7 DB with out any problems. After I upgrade the DB
> to 2000 sp3 I can connect to it through enterprise manger only on a
> workstation that does not have an alias created to the SQL2000
> server. The application we are using against this DB requires an
> Alias to connect to the data. I have tried using the server name
> -which works fine to connect to the SQL7 DB, I have tried using IP
> address, & I have tried using the fully qualified domain name, when
> creating the Alias. after the alias is created we can not connect to
> the DB.
Are you saying that you are creating an alias on the client using the
SQL Server 2000 Client Network Utility. You give the alias a name that
differs from the server name and are presumably using TCP/IP as the
protocol. When you try and connect to the 2000 server using the server
name, it works. However, when you connect to the server using the alias
name, you can not connect. If so, can you post your alias information as
you set it up.
Can you connect to SQL Server from Query nalyzer using the alias and
server name both?
David Gugick
Imceda Software
www.imceda.com|||I created the Alias using SQL Server 2000 Client Network Utility I created
the Alias with the same name as our SQL server using TCPIP and the server
name ( I have also since then tried using the FQDN, and IP address for Server
Name) The initial alias cfg'd with server name works fine with the pre
upgrade SQL7 DB. After the Alias is created I can not connect to the SQL
database at all. Using query analyzer I can not connect to the lowercase
server name -populated by the Alias, or by browsing out to the server. I
lose all connectivity to the SQL server. After I remove the Alias I can once
again connect to the server.
"David Gugick" wrote:
> Civic wrote:
> > I have an SQL 2000 DB that was upgraded from SQL7. I can connect to
> > and work with the 7 DB with out any problems. After I upgrade the DB
> > to 2000 sp3 I can connect to it through enterprise manger only on a
> > workstation that does not have an alias created to the SQL2000
> > server. The application we are using against this DB requires an
> > Alias to connect to the data. I have tried using the server name
> > -which works fine to connect to the SQL7 DB, I have tried using IP
> > address, & I have tried using the fully qualified domain name, when
> > creating the Alias. after the alias is created we can not connect to
> > the DB.
> Are you saying that you are creating an alias on the client using the
> SQL Server 2000 Client Network Utility. You give the alias a name that
> differs from the server name and are presumably using TCP/IP as the
> protocol. When you try and connect to the 2000 server using the server
> name, it works. However, when you connect to the server using the alias
> name, you can not connect. If so, can you post your alias information as
> you set it up.
> Can you connect to SQL Server from Query nalyzer using the alias and
> server name both?
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Is your SQL 7 using Named Pipes or TCP/IP (Server Network Utility). I
believe Named Pipes was the default for SQL 7...
"Civic" <Civic@.discussions.microsoft.com> wrote in message
news:6FD4CF01-DB82-4CB2-9FA8-2ECEC5942441@.microsoft.com...
>I created the Alias using SQL Server 2000 Client Network Utility I created
> the Alias with the same name as our SQL server using TCPIP and the server
> name ( I have also since then tried using the FQDN, and IP address for
> Server
> Name) The initial alias cfg'd with server name works fine with the pre
> upgrade SQL7 DB. After the Alias is created I can not connect to the SQL
> database at all. Using query analyzer I can not connect to the lowercase
> server name -populated by the Alias, or by browsing out to the server. I
> lose all connectivity to the SQL server. After I remove the Alias I can
> once
> again connect to the server.
> "David Gugick" wrote:
>> Civic wrote:
>> > I have an SQL 2000 DB that was upgraded from SQL7. I can connect to
>> > and work with the 7 DB with out any problems. After I upgrade the DB
>> > to 2000 sp3 I can connect to it through enterprise manger only on a
>> > workstation that does not have an alias created to the SQL2000
>> > server. The application we are using against this DB requires an
>> > Alias to connect to the data. I have tried using the server name
>> > -which works fine to connect to the SQL7 DB, I have tried using IP
>> > address, & I have tried using the fully qualified domain name, when
>> > creating the Alias. after the alias is created we can not connect to
>> > the DB.
>> Are you saying that you are creating an alias on the client using the
>> SQL Server 2000 Client Network Utility. You give the alias a name that
>> differs from the server name and are presumably using TCP/IP as the
>> protocol. When you try and connect to the 2000 server using the server
>> name, it works. However, when you connect to the server using the alias
>> name, you can not connect. If so, can you post your alias information as
>> you set it up.
>> Can you connect to SQL Server from Query nalyzer using the alias and
>> server name both?
>>
>> --
>> David Gugick
>> Imceda Software
>> www.imceda.com
>>|||Civic wrote:
> I created the Alias using SQL Server 2000 Client Network Utility I
> created the Alias with the same name as our SQL server using TCPIP
> and the server name ( I have also since then tried using the FQDN,
> and IP address for Server Name) The initial alias cfg'd with server
> name works fine with the pre upgrade SQL7 DB. After the Alias is
> created I can not connect to the SQL database at all. Using query
> analyzer I can not connect to the lowercase server name -populated by
> the Alias, or by browsing out to the server. I lose all connectivity
> to the SQL server. After I remove the Alias I can once again connect
> to the server.
>
Why would you create an alias with the same name as the server? An alias
should have a different name... which is the point of an alias.
From BOL:
"In some cases, an instance of SQL Server may be configured to listen on
alternate network addresses. If this is done, client applications
connecting to that instance must explicitly specify the alternate
address. While applications could specify the alternate addresses on
each connection request, it is easier to use the Client Network utility
to set up an alias specifying the alternate addresses. Applications can
then specify the alias name in place of the server network name in their
connection requests."
Which seems to indicate you should be using a unique alias name that
differs from the server name.
David Gugick
Imceda Software
www.imceda.com|||"David Gugick" wrote:
> Civic wrote:
> > I created the Alias using SQL Server 2000 Client Network Utility I
> > created the Alias with the same name as our SQL server using TCPIP
> > and the server name ( I have also since then tried using the FQDN,
> > and IP address for Server Name) The initial alias cfg'd with server
> > name works fine with the pre upgrade SQL7 DB. After the Alias is
> > created I can not connect to the SQL database at all. Using query
> > analyzer I can not connect to the lowercase server name -populated by
> > the Alias, or by browsing out to the server. I lose all connectivity
> > to the SQL server. After I remove the Alias I can once again connect
> > to the server.
> >
> Why would you create an alias with the same name as the server? An alias
> should have a different name... which is the point of an alias.
>
> From BOL:
> "In some cases, an instance of SQL Server may be configured to listen on
> alternate network addresses. If this is done, client applications
> connecting to that instance must explicitly specify the alternate
> address. While applications could specify the alternate addresses on
> each connection request, it is easier to use the Client Network utility
> to set up an alias specifying the alternate addresses. Applications can
> then specify the alias name in place of the server network name in their
> connection requests."
> Which seems to indicate you should be using a unique alias name that
> differs from the server name.
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>