Options
Run package error
Brian Donahue
Posts: 6,590 Bronze 1
Hello,
Thanks for your post. SQL Package will attempt to write to the event log when something goes wrong. In your case, though, you can't see what SQL Package is trying to log because the SQL Package assembly doesn't have rights to make an event log entry!
I'd have a look at your .net Framework security configuration. If you implement trusts, you may want to give this SQL Package full trust.
This may also happen if you run a Package over the network, for instance from a file share. Try installing the application to the local hard disk and see if that helps.
Thanks for your post. SQL Package will attempt to write to the event log when something goes wrong. In your case, though, you can't see what SQL Package is trying to log because the SQL Package assembly doesn't have rights to make an event log entry!
I'd have a look at your .net Framework security configuration. If you implement trusts, you may want to give this SQL Package full trust.
This may also happen if you run a Package over the network, for instance from a file share. Try installing the application to the local hard disk and see if that helps.
This discussion has been closed.
Comments
The default trust level in .net seems to be sufficient to run SQL Packages, but if you implement a policy that restricts assembly trusts, you can change these trusts during deployment with CASPOL.exe. Here is an MS TechNet article describing just that:
http://msdn.microsoft.com/library/defau ... licies.asp