how to solve this error Code: 0xC0010018?
-
Wednesday, August 22, 2012 4:23 PM
hi sir,
Actually i got this error i.e package could not be loaded . The error number is
Code: 0xC0010018. Actually i am installed in windows xp , so plz explaine how to solve this error.
Thank you sir..
Regards:
Bhaskar
- Moved by Sethu SrinivasanMicrosoft Employee Friday, November 02, 2012 12:15 AM SSIS (From:SQL Server Manageability)
All Replies
-
Wednesday, August 22, 2012 4:51 PM
-
Friday, August 24, 2012 8:38 AM
Hi Bhaskar,
Do you try to load a SQL Server Integration Services (SSIS) package and encounter this error? If so, maybe the SSIS package contains a DateTime type variable. You define the period (.) character or another user-defined character as the date separator in the Windows locale setting before you create the SSIS package.
This problem occurs because the value of the DateTime variable is saved in string format when you save the SSIS package. However, the string representation of the DateTime variable is based on the date format that is specified in the Windows locale. Therefore, when you try to load the SSIS package on a computer that has an incompatible locale date format, the operation fails.
There’re two methods to work around this problem:
- Manually update the DateTime type string in the SSIS package to use the slash (/) character as the separator.
- Update the date separator in the Windows locale setting to be identical to the date separator of variables in the SSIS package file.
For more details, please refer to this article: You receive an error message when you try to load an SSIS package that contains a DateTime type variable in SQL Server 2005.
Best Regards,
Ray Chen -
Saturday, August 25, 2012 7:16 AM
hi sir,
actually i got that error at the time of execute the jobs in maintenance plans. i.e once job can be executed the error can be occured i.e package could not be loaded.
Thank you sir
Regarads
bhaskar
-
Monday, August 27, 2012 2:41 AM
Hi Bhaskar,
Could you please elaborate your scenario and provide the SQL error log for getting better help?
What edition of SQL Server are you using? Maybe you can apply the latest Service Pack for it and then give it a try again.
Best Regards,
Ray Chen

