• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 7792
  • Last Modified:

SSIS: Package Validation Error: THe SSIS logging provider has failed to open the log. Error code:0x80070005

I have a working SSIS package being converted from VS 2005 to VS 2008.  Logging has worked correctly for years.  I use an Expression for the connection string of the connection manage for the log file:
"\\\\" + @[System::MachineName] + "\\OxmoorHouse\\SSIS_Logging\\OH_CAP_Grids_Build\\" + @[System::PackageName] + "_" + Right ("0" + (DT_WSTR, 4) DATEPART("YEAR", @[System::StartTime]) ,4) + "_" + Right ("0" + (DT_WSTR, 2) DATEPART("Month",  @[System::StartTime]) ,2) + "_" + Right ("0" + (DT_WSTR, 2) DATEPART("Day",  @[System::StartTime]),2) + "_" + Right ("0" + (DT_WSTR, 2) DATEPART("Hour",  @[System::StartTime]),2) + "_" + Right ("0" + (DT_WSTR, 2) DATEPART("Minute",  @[System::StartTime]),2) + ".txt"

After conversion, I tested the package on my Dev SQL machine .  Worked fine except I noticed the expression for the log file connectionstring on the connection manager vanished.  I re-added the syntax above.  Now with or without the expressions I get the following error:
Package Validation Error:  The SSIS logging provider has failed to open the log.  Error Code: 0x80070005.

Facts:
1.  Delay Validation is True on the package and the connection manager.
2.  Permissions to the directory and files for the log files is full control for all users.
3.  Usage Type for the file is Create file but i have tried Existing with no difference.
4.  The expression is correct as I have Evaluated it and confirmed the path is correct.
5.  I have removed the expression and returned to using a fixed name file, fails with same message.  Nothing works now.

I cannot identify anything else that has changed since the last successful execution.

Suggestions?
0
OHIS
Asked:
OHIS
  • 3
  • 2
1 Solution
 
hspoulsenCommented:
One thing that bit me very hard when going from SQL Server 2005 to 2008 was the way that SSIS handles NULLs.

I had to change each and every place where NULLs could occur.
The worst part was all the Script Components in the Data Flows.

I cannot see if that is your problem, though.
0
 
OHISAuthor Commented:
Nulls are not the issue.  As I stated, this was a working package.  I converted to 2008, it dropped the expressions but ran to a fixed log file.  I edited to add the expression back into the connection string of the log file, now it fails with or without the expression.  I can get it to run if I turn logging off.

I am running this from BIDS not the server, at this point.  i have not deployed the new version to the development server; I am just pointing there, dynamically for testing purposes.
0
 
OHISAuthor Commented:
Solved it.
The location of the logging is dynamic, but on the my PC it is a directory that has a Share on the root of the log directory.  On my PC, I had declared the directory to be full control to all users.  The share had read only permissions and as we all know. Microsoft likes most restrictive permissions so The log was unable to pass the share permissions.  i opened the share, log writes.

Thanks for your time hspoulsen.
0
 
hspoulsenCommented:
I'm glad you solved it, and I hope for you that NULL will not bite you, as I was bitten.
0
 
OHISAuthor Commented:
I resolved the problem after discovering the layered permissions.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: C++ 11 Fundamentals

This course will introduce you to C++ 11 and teach you about syntax fundamentals.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now