dtexec

I have saved a copy of a package to a 64-bit server running Windows 2003 Enterprise Edition SP1. I changed the Run64BitRuntime to true before saving the package. When I try to use DTExec to execute the package which does have a script task in it I receive the below error.

Error: 2005-08-17 16:52:32.89
Code: 0x00000005
Source: Script Task 1
Description: The script files failed to load.
End Error

Any help is appreciated.

Thanks.In your script task set PreCompileScriptIntobinaryCode=TRUE

This is a known issue with 64-bit machines. The default setting for this property (as of the next CTP) has been set to TRUE because of it.

-Jamie|||Jamie is correct that the default value of this property has been changed from False to True. The Integration Services team opted for 64-bit convenience at the cost of increased package size. 32-bit users may want to measure the impact of this setting if package size is ever a concern.

-Doug|||Thanks you guys - I have been able to get the packages scheduled.

DST and Notification Services

I need some clarification on Daylight Saving Time changes for SQL
Server 2005.
I read MicroSoft Article 931815.
Per the doc, I have determined that I have Notification Services
installed (determined via registry).
However, I do not seem to have any Notification Services to stop (step
1) and not sure what name to use for NSMainDatabase (running the osql
script in step 5).
>From the SQL Server Management Studio, I can determine that I have
version 9.0.242.0 of Notification Services, but it tells me that NO
instances are registered on this machine.
So, please advise if you have any input. I am about 80% confident that
I don't need to do this fix.
Thanks,
RogerIf you do not have an instance of Notification Services deployed, then you
do not have to worry about patching. The binary files of Notification
Services are not affected. You have to apply the update only when you create
an instance. If there are no services running and no NS* databases, then
really nothing to do. Also, for instances deployed after SQL Server 2005 SP2
is installed you do not have to do anything, as instances created with SP2
will have the correct DST info.
HTH,
Plamen Ratchev
http://www.SQLStudio.com|||On Mar 6, 2:59 pm, "Plamen Ratchev" <Pla...@.SQLStudio.com> wrote:
> If you do not have an instance of Notification Services deployed, then you
> do not have to worry about patching. The binary files of Notification
> Services are not affected. You have to apply the update only when you crea
te
> an instance. If there are no services running and no NS* databases, then
> really nothing to do. Also, for instances deployed after SQL Server 2005 S
P2
> is installed you do not have to do anything, as instances created with SP2
> will have the correct DST info.
> HTH,
> Plamen Ratchevhttp://www.SQLStudio.com
I thank you for your comments. Much appreciated.

DST and Notification Services

I need some clarification on Daylight Saving Time changes for SQL
Server 2005.
I read MicroSoft Article 931815.
Per the doc, I have determined that I have Notification Services
installed (determined via registry).
However, I do not seem to have any Notification Services to stop (step
1) and not sure what name to use for NSMainDatabase (running the osql
script in step 5).
>From the SQL Server Management Studio, I can determine that I have
version 9.0.242.0 of Notification Services, but it tells me that NO
instances are registered on this machine.
So, please advise if you have any input. I am about 80% confident that
I don't need to do this fix.
Thanks,
RogerIf you do not have an instance of Notification Services deployed, then you
do not have to worry about patching. The binary files of Notification
Services are not affected. You have to apply the update only when you create
an instance. If there are no services running and no NS* databases, then
really nothing to do. Also, for instances deployed after SQL Server 2005 SP2
is installed you do not have to do anything, as instances created with SP2
will have the correct DST info.
HTH,
Plamen Ratchev
http://www.SQLStudio.com|||On Mar 6, 2:59 pm, "Plamen Ratchev" <Pla...@.SQLStudio.com> wrote:
> If you do not have an instance of Notification Services deployed, then you
> do not have to worry about patching. The binary files of Notification
> Services are not affected. You have to apply the update only when you create
> an instance. If there are no services running and no NS* databases, then
> really nothing to do. Also, for instances deployed after SQL Server 2005 SP2
> is installed you do not have to do anything, as instances created with SP2
> will have the correct DST info.
> HTH,
> Plamen Ratchevhttp://www.SQLStudio.com
I thank you for your comments. Much appreciated.