Page 1 of 1

MS SQL Server Load stage

Posted: Mon Feb 07, 2005 3:51 am
by Martina
On our test server I use MS SQL Server Load stages to Bulk load data from DB2 to SQL Server in a number of jobs. I have exported these jobs and imported it on our Production server, and without changing anything other than the connection to the correct DB2 database, I now get the errors:

MS_SQL_Server_Load_7: Internal error: IDBInitialize->Initialize() failed.
MS_SQL_Server_Load_7: Failed to establish datasource connection

Does anybody have any idea how this can be solved?

Since there is no connection made to SQL Server, setting up a trace on SQL Server is of no use...

Posted: Mon Feb 07, 2005 4:08 am
by Sainath.Srinivasan
Is your production server a separate machine than the machine from which you exported these jobs?

All work in DataStage takes place in the DataStage server. So moving to a new server will imply re-configuring these connections for DataStage to work.

As it raises 'initialize' error, you can start looking at dsenv file (available under the DSEngine directory).

Depending on how you do the load to SQL Server db, you may need to install and configure other libraries.

Re: MS SQL Server Load stage

Posted: Wed Feb 15, 2006 8:19 pm
by Arunachalam
I hope that you had resolved the problem. I am getting the same error now. can you pass me the solution.

Thanks for your time !

Posted: Wed Feb 15, 2006 11:39 pm
by ray.wurlod
Does the production system have a system or file DSN that points to the correct SQL Server instance?

Re: MS SQL Server Load stage

Posted: Thu Feb 16, 2006 12:15 am
by Martina
I am at a different client now, but as I remember well, it had something to do with the ODBC connection from the production server to the SQL Server.

Re: MS SQL Server Load stage

Posted: Fri Feb 17, 2006 2:44 am
by Arunachalam
Yes. You are correct. It works now after I changed the parameters! Thanks Guys for your valuable time !

Re: MS SQL Server Load stage

Posted: Fri Dec 28, 2007 1:18 am
by quiztime
I just had the same error message and it turned out to be because the login in SQL server that I had created had a security policy with "expire password at first login" turned on.

In other words the error message seems to be a bit generic and can represent a variety of parameter/login problems.

Posted: Fri Dec 28, 2007 3:16 am
by ray.wurlod
Welcome aboard. That may be a useful snippet of knowledge for future searchers: thank you.