October 2, 2006 at 10:09 am
OK I have to ask, why does this happen??? My boss attempts the same process, it hangs for 2-3 seconds and the properties come up for him.
I right click to view the properties of a transform data task between two data sources....enterprise manager hangs, becomes unresponsive...CPU goes to 100% and seems like it never ends...I have to go in and kill MMC.exe to get the computer back.
Why does this happen? Anything I can do to review or change on the DTS?
Thanks,
Leeland
October 2, 2006 at 10:22 am
I've had this happen when I've opened a package on my workstation without being logged on to the server. It works when I log on to the server either remotely or directly at the server console.
It seems to happen most commonly when one of the data sources is an ODBC source and I don't have the same DSN on my workstation.
Greg
Greg
October 2, 2006 at 10:41 am
Very interesting...I will try to log into the server and open the data task there and see if there is any difference...
I was going to try to log into the server with the SA account in EM to see if it made a difference vs. logging in with windows authentication...
I will let you know the results.
Leeland
October 3, 2006 at 9:10 am
If I go on the server and login with the service account...I can get into the DTS no problem. However when I attempt to open a tansformation data task from my desktop it hangs and the CPU goes to 100%....to the point that I have to kill it.
Does anyone have a recommendation as to what may be causing this issue that I cannot acces the transformation data task properties ?
Thanks,
Leeland
October 3, 2006 at 10:09 am
Are your server and workstations on the same Service Pack? It may be that the mmc components on your workstation need to be updated. I've found refrences in MS Knowledgebase to crashing and hanging problems prior to SP4.
Greg
Greg
October 3, 2006 at 11:29 am
You are my hero Greg...that was it. When I checked the version of QA, it
| 8.00.194 | RTM |
I ran the SP4 upgrade, rebooted and attempted the same task...works !!! Thanks a bunch...saved me some time screwing around with this issue.
Leeland
October 3, 2006 at 5:23 pm
Cool! Glad to help.
Greg
Greg
October 25, 2006 at 10:38 am
Hello,
I have similar problem. When I tried to open the transformation task between the db2 server and SQL Server, i just got the hour glass cursor indefinitely that I had to shut down the Enterprise Manager.
I access my DTS package directly on the SQL Server because that's where it's installed.
Sorry I don't understand what you guys were saying here. What is mmc components on the workstation and how can I tell what Service Pack is for the mmc components and for the sql server?
Thanks a lot,
TV.
October 25, 2006 at 11:03 am
you need to go into query analyzer and into help to the about portion and see what version of QA you have.
then go on the server in question via QA and run the following
select @@VERSION
it will tell you what version and\or system packs you have installed....
you can view all the different system packs on this website which give a better definition.
http://www.krell-software.com/mssql-builds.asp
let me know if you have more questions...I don't know squat about DB2 so I am of no use to you there...it could very well be something totally unreleated to my post.
October 25, 2006 at 11:27 am
My QA version said 8.00.2039.
When I ran the sql statement select @@VERSION in QA for that server I got 8.00.2040.
Let me explain my problem again so you can see if this is related to this post.
I have a source server that connects to a db2 database via an ODBC driver, and a destination server which is a SQL Server. I have a transformation task between these two servers.
I was able to test the db2 datasource sucessfully but when I tried to double click on it in DTS, I got the hour glass cursor indefinitely that I had to shut down EM. Same thing with the Transformation Task between the db2 server and SQL server. It just got hung that I had to kill EM.
Not only I can't open the task in DTS to modify the code but I can't even run it either (This DTS package is developed by someone else who's no longer working for us).
Please let me know if you have any idea how to fix this problem.
Thanks a lot for your help.
TV.
October 25, 2006 at 11:38 am
ok first things first...if you have the ability to modify system tables...go into msdb and find out who the id is that owns the dts
then you can update that row or rows to make the dts owned by the SA account
update msdb.dbo.sysdtspackages
set owner = 'sa',
owner_sid = 0x01
where owner = 'some owner'
As for the ODBC connection, I am not too familiar with that sort of thing...only thing I would do is attempt to re-install or re-create that connection to the other server. I am not the best with security but it sounds like something is tying up the access...I would review how DB2 and SQL talk to one another...maybe you know about that...I don't so I am sorry I can't help you at the moment
October 26, 2006 at 9:37 am
I prefer to use sp_reassign_dtspackageowner in msdb. It's parameters are the package name, package Id, and new package owner logon id.
Greg
Greg
October 26, 2006 at 9:41 am
thanks for the info Greg, I wasn't aware of that stored proc...mental note made !
December 12, 2007 at 2:29 pm
Was there any resolution to this?? Experiencing same thing when we moved to 2003 OS from 2000. SQL Server remained 2000 SP2, and now havign similar issues in DTS but with Sybase versus DB2
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply