Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 371
  • Last Modified:

Problems with SSIS

We are using SQL Server Integration Services on several servers for our customers. We sync data from a Pervasive database and calling the SSIS packages from a .NET application. All servers are working fine using the .Net Providers\Odbc Data Provider but now we have one server where we can't get it to work.

We get this error
ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

When I do a manual import from Pervasive using the .Net Providers\Odbc Data Provider it works fine

The different on this server from the other ones is:
Windows 2008 Enterprise SP2 (all other server are Windows 2008 R2 Standard)
MS SQL 2008 (all other servers are MS SQL 2008 R2)


All servers are 64 bit.

Any idea what to look for?
0
Gerhardpet
Asked:
Gerhardpet
  • 5
  • 3
1 Solution
 
lcohanDatabase AnalystCommented:
<<We get this error
ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified >>

You must look for that Odbc Data Provider on that .." one server where we can't get it to work. "

Its under Control Panel - Admin Tools - ODBC Data sources and make sure that the Pervasive user running the .NET application can access it.
0
 
GerhardpetAuthor Commented:
You must look for that Odbc Data Provider on that .." one server where we can't get it to work. "

Its under Control Panel - Admin Tools - ODBC Data sources and make sure that the Pervasive user running the .NET application can access it.

Been over this a hundred times already. It is not a permission issue.

As I said when I do a manual import from Pervasive using the .Net Providers\Odbc Data Provider it works fine
0
 
David ToddSenior DBACommented:
Hi,

This isn't a 32bit vs 64bit issue is it?

That is, are all your versions of windows/sql/etc 32bit?

Regards
  David
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
GerhardpetAuthor Commented:
Correct it is not related to 32bit vs 64bit.

 We have the same .NET application working on 5 other servers of which 4 are 64 bit and 1 is a 32bit.

Pervasive 10 only supports 32 bit so we connect to the 32bit ODBC data source.

That is not the issue here.
0
 
David ToddSenior DBACommented:
Hi,

The issue isn't if Pervasive is 32 or 64bit, the issue is if you can find the correct bit driver for your application.

If your application is 64bit, then it isn't going to accept a 32bit driver - generally speaking.

Given your servers are 64bit, are you using the correct version of odbc administrator? There are two versions, and they look identical, and you can only run one at a time if memory is correct ...

Regards
  David
0
 
GerhardpetAuthor Commented:
Thanks for trying to help David but did you read my original question?

I know all about the issue of selecting the right driver for Pervasive (32bit vs 64bit) and that is not the problem here.

The different on this server from the other servers is:
Windows 2008 Enterprise SP2 (all other server are Windows 2008 R2 Standard)
MS SQL 2008 (all other servers are MS SQL 2008 R2).

Again to manually run an import job it works fine (which uses ISSIS as well) but to run it from a package it does not work where we get this error

ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
0
 
David ToddSenior DBACommented:
Hi,

Have you created a user DSN vs a System DSN?

Regards
  David
0
 
GerhardpetAuthor Commented:
The problem was in IIS.

This is from the links below
Open IIS manager, select Application Pools, select the application pool you are using, click on Advanced Settings in the right-hand menu. Under General, set "Enable 32-Bit Applications" to "True".

Here are a few links that I used to solved it
http://stackoverflow.com/questions/1134827/how-do-i-use-a-32-bit-odbc-driver-on-64-bit-server-2008-when-the-installer-doesn 
http://lostechies.com/gabrielschenker/2009/10/21/force-net-application-to-run-in-32bit-process-on-64bit-os/
0
 
GerhardpetAuthor Commented:
Found the solution myself
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now