Hi All, I'm trying to implement the SQL Server logging in my package but Im receiving a very weird error message. Follow below: "Error at Consumer_Common_Transportation [Log provider "SSIS log provider for SQL Server"]: An OLE DB error has occurred. Error code: 0x80040E14.An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E14 Description: "There is already an object named 'sysdtslog90' in the database. Error at Copy Data to TCARRIER: The SSIS logging provider "SSIS log provider for SQL Server" failed with error code 0xC0202009 ((null)). This indicates a logging error attributable to the specified log provider. (Microsoft.DataTransformationServices.VsIntegration)" I know that the sysdtslog90 table exists ( with no rows ), but i cant understand why this process doesnt includes rows/data in this table. I alsohave the Text file logging in this package and it is working fine. I just need to fix this issue to move it to production. Does anyone knows what is happening? Is there any property or flag that i need to change? Thanks in advance for your help. Regards, Thiago

Hi, when do you get this message? When the package executes or as you are trying to add the log provider?Can other packages log data to the same database?The sysdtslog90 table you see there was created by SSIS, not you correct? What database are your logging to/seeing the sysdtslog90 table in?If you create a new test DB, point the log provider to it, does it log ok? You mention you want to move it to production...when that occurs will you be logging to a different database anyway?

HiCraig, I get this message whenI execute the package. I tried to exclude only the loggingfeature from my package and it worked fine. It happens when I execute the package with ANY log writing (error messages, information, posexecute, etc )There isnt other packages logging in this table because this the first one that i have included this feature. I noted that the table was created with the name myLogin.sysdtslog90. Is this right? Can I change it?This table was created automatically by the log process in the development database. I didnt try this option ( create a new test DB.... ). I will try and then i post the results. Thanks for you sugestion.No. I have a configuration for this packages.I will just change the path in the XML file and the package will point to production server. In the production environment I have the same structure as development environment.Thanks for you help Craig.RegardsThiago

Hi Thiago, Did you get any solution for this error, I'm facing same issue with logging. Thanks AG_MD

hi, i get the same error. it works on my own laptop. when i deploy my packages via file-system to the server i run the packages via a command-prompt. then i get the error about the log-provider. don't have a clue what to do about it.

Hi I'm having a similar problem. Package execution sporadically fails when accessing sysdtslog90. Once I drop this table, the package executes a number of times, before I face this problem again. Does anyone know what might be the cause of this error? Cheers Sachin

Have the same problem here... seems to have to do with permissions, but don't know for sure. Any other ideas on this?

I have encountered the same issue when in Connection Manager I used SQL Authentication to connectwith SQL Server OleDB Provider. SSIS Logging Provider in this case created log table for the SQL user (something like yourDBuser.sysdtslog90) To resolve the issue scriptand then drop yourDBuser.sysdtslog90 table. in the script change the name of the table to dbo.sysdtslog90. Execute script to recreate table with dbo user. Execute your SSIS package in BIDS and check dbo.sysdtslog90. This time you should see log entries in the table

Hi - Just wanted to follow up on this, because Boris's solution worked for me. I was having the same error as detailed above, but changing the object owner worked fine(in fact I used sp_changeobjectowner rather than dropping and recreating the table, but same difference) Now, if all the msft devs didn't connect as sa, we wouldn't have had this problem...

Hello, I am new to ssis and I was wondering how you got your text file logging working. I have it setup but not sure if it is correct and text file is empty. Could you give me a run down on setting this up? Thanks, Jeremy

Truncated the log table and it started working for me again :|