Enterprise Manager hang when using ODBC to iSeries in DTS package

Question

Post reply

Enterprise Manager hang when using ODBC to iSeries in DTS package

Jelle Struijk

SSC Rookie

Points: 28
More actions
January 15, 2008 at 4:26 am

#69702

On our Win 2K3 server with SP2 and SQL Server 2000 SP3a, I am no longer able to save any DTS packages that use ODBC or OLEDB connections to our iSeries.
When I attempt to save or even create such a connection, Enterprise Manager simply hangs and all i can do is kill EM using task manager.
The DSN for the AS/400 does work, and if I create the DTS package on my client PC running XP SP2 I can run and download data from the iSeries.
Any ideas how to get EM on the Win 2K3 machine to edit and save the DTS packages?
Any help will be appreciated
Jelle

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply

lexx00 Newbie Points: 7 More actions · Answer 1

Hi Jelle,

I am experiencing the same issue - but with a windows 2003 sp 2 on the server... did you find a resolution for this?

Thanks,

L

Jelle Struijk SSC Rookie Points: 28 More actions · Answer 2

Lex,

I have not found a real solution for this issue using SQL 2000.

We are however upgrading to SQL 2005 and what i found is that using the SQL Management Studio and the additional DTS 2005 download available from Microsoft, it is possible to edit DTS packages in both SQL 2000 and SQL 2005.

The one thing that is not possible is creating a new DTS package that way.

Hope this helps

Regards

Jelle

otolino SSC Veteran Points: 268 More actions · Answer 3

Hi,

I'm experimenting the same problem. But I realize that if you wait long enough the Enterprise manager returns from limbo (and I mean really long time, once was about 30 minutes), and you are able to modify your queries and everything in you datapump task.

The work around for us was to create an import DTS using the import wizard, saving it to the SQl Server at the end and then editing and adding the additional tasks.

I hope this help to find a solution for this issue.

maddogs SSCrazy Points: 2474 More actions · Answer 4

I realize this is an old post but we are now experiening this same issue with ALL our DTS packages that have AS\400 connections, they worked just fine a week ago but now when we try to save these packages enterprise manager gets hung. Was there ever a resolution as to the specific cause\fix for this? Our host SQL server is SQL2000 SP4 on a Win2003 SP2 OS.

Thanks!

maddog

Jelle Struijk SSC Rookie Points: 28 More actions · Answer 5

I am not aware if any specific fix for this.

For me, the solution was to start using SQL Server Management Studio 2005 with the additional download.

That allowed me to Edit and save DTS packages again in both SQL 2000 and SQL 2005

Hope this helps

Jelle

maddogs SSCrazy Points: 2474 More actions · Answer 6

Thanks for the reply. We are not moving to SQL2K5 anytime soon so will keep searching....

Cheers!

maddog

Jim Sander Newbie Points: 3 More actions · Answer 7

I encountered the same problem, hanging in DTS whenever I tried to use or modify a task or connection for the AS400.

The problem went away when I upgraded iseries Access for Windows (Client Access) to version 5, release 4. Previously I was at release 1.

maddogs SSCrazy Points: 2474 More actions · Answer 8

This is also belated, but what fixed it for us was substituting the logical server name of the AS\400 client connection in both the DTS package and the server ODBC configuration with the actual IP address of the AS\400 server. All of a sudden all the pkgs that referenced this connection started working again and we could open\edit\save these connections in DTS pkgs with no delays.

maddog