Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
notes4we
Yak Posting Veteran
90 Posts |
 Posted - 2008-10-24 : 09:42:12
|
| I had enabled Logging in the packages before. But now we do not need it as we figured out some better way to look for the errrors. So, I went ahead and disabled logging from all the packages and the packages are running fine in BIDS. But when I am trying to deploy them on the test server and run as a job, then it is giving the below error:MessageExecuted as user: UserName. ...ion 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 9:38:02 AM Error: 2008-10-24 09:38:32.80 Code: 0xC001403D Source: Description: The log provider type "DTS.LogProviderEventLog.1" specified for log provider "SSIS log provider for Windows Event Log" is not recognized as a valid log provider type. This error occurs when an attempt is made to create a log provider for unknown log provider type. Verify the spelling in the log provider type name. End Error Error: 2008-10-24 09:38:32.80 Code: 0xC0010018 Source: Description: Error loading value "<DTS:LogProvider xmlns:DTS="www.microsoft.com/SqlServer/Dts"><DTS:Property DTS:Name="ConfigString"></DTS:Property><DTS:Property DTS:Name="DelayValidation">0</DTS:Property><DTS:Property DTS:Name="ObjectName">SSIS log provider for Windows Event Log</DTS:Prop" from node "DTS:LogProvider". End Error Could... The package could not be lo... The step failed.Any help? |
|
|
rgombina
Constraint Violating Yak Guru
319 Posts |
Posted - 2008-10-24 : 09:46:12
|
| Check all the packages again; might have missed/checked one somewhere. It happened to me and drove me nuts. |
 |
|
|
notes4we
Yak Posting Veteran
90 Posts |
Posted - 2008-10-24 : 10:55:27
|
| No. I had tried only on three packages and I did not leave anything. But now I know how to solve it.It was still showing in the Package Explorer Tab. When I right mouse clicked and deleted from there directly, the package got corrupted. So what I did is, I went ahead and changed the XML Code (deleted two lines having logprovider).And now all is good. But now I have this work to do - change the XML code.Thank you anyways. |
|
|
|
|
|
|
Error on removing windows event log