The workaround is to place this entry into the ‘hosts’ file on the Windows Server 2003 machine :
<<<<<
#Fix for slow running SSIS packages
127.0.0.1 crl.microsoft.com
If you're using 2005, this might have something to do with the certificate revocation list.
In 2008 its modified the dtexec configuration to not check the list. The customer could do the same for 2005 by manually editing the file.
See Michael's blog post for more information:
http://blogs.msdn.com/michen/archive/2008/03/14/configuring-net-for-running-ssis-packages-from-custom-applications.aspx
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment