June 3, 2005 at 9:40 am
Using an Execute Package Task to call another DTS package. I am getting a "Server Busy" dialogue box with the message "This action cannot be completed because the other program is busy. Choose 'Switch To' to activate the busy program and correct the problem."
When I click the "Switch To" button the Windows Start menu opens and the dialogue reappears. The only way out is to stop Enterprise Manager from Windows Task Manager.
The called DTS package runs perfectly normally if run it directly. There is no user interaction in the package.
The package uses ActiveX to copy a blank Access database. Creates tables in the Access database and populates with data. Then zips the database and sends an email giving the intranet path and file name.
June 3, 2005 at 11:06 am
I bet that the email is your culprit. Log into the server (either directly or via term services) as the account that SQL Server Agent runs under (the one the MAPI profile is configured under). Outlook / MAPI is probably needing some attention.
June 3, 2005 at 3:10 pm
I am using xp_smtp_sendmail for email so this is probably not the problem
June 6, 2005 at 11:03 am
Can anyone tell me a called package throws up this message. But it does not throw up a message if I run it directly.
I have tried trying to identify where the problem is by putting stops in. It ran perfectly all the way through. I then overwrote the original package and run it again and got the same problem.
The only difference I can think of is that I am assigning the Server in the Execute Package Task using a Dynamic Properties Task with an INI file.
I guess that if I can not get this to work as a sub task I will have to set it up as a step in the scheduled job and set up some sort of flag which I can test for.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply