November 17, 2015 at 12:18 pm
Environment - VS 2012, 32 bit, SQL 2008/2012, UNC paths
OK. I've done this kind of thing before and now it's really .. ummm .. annoying me.
My intent is to create an Excel file for every time there's an error in the audit log. The name of the Excel file is a variable.
I've got all my delay validations set to True. All of them. Package, connection manager, and data flow task.
But I keep getting an 'object not found, can't open rowset' error.
I've even tried the file system task to copy an empty one into the same variable name that's used in the Excel connection manager but no joy.
What the heck am I missing or is SSIS no longer playing nicely with new dynamically created Excel files?
January 11, 2016 at 1:07 pm
OK - either I'm doing something way out of the ordinary or people aren't able to give me much help here.
I have tried going to a static drive for this - my C drive. I get the same problem. The file gets created, I can open it in Excel, but SSIS doesn't recognize it.
One think I've noticed is that the path shows up in double quotes in the connection string. I have no idea why this is or how to make it go away. If I take out those quotes it finds the file.
So my problem seems to be that the connection manager is getting double quotes from the file connection variable. Anyone else find and fix this problem?
January 21, 2016 at 10:09 am
I give up.
It seems like SSIS is OK with dynamic Excel files when they're a data source but when it comes to a destination it stomps its little foot and refuses to play nicely.
I'm going to send the email I need with embedded HTML (hello scripting since the Send Mail task doesn't like HTML) and let it go since the core data is in a table.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply