A ssis Package was created two days ago to loop through Excel and then import it to the database. It works normally in the development environment, but after being deployed to the SQLAgent, it is found that the Job has failed.
Open JobHistory to see the following error:
Description: Authorization: 0x80004005. AnOLEDBrecordisavailable. Source: "MicrosoftAccessDatabaseEngine" Hresult: 0x80004005Description: "comment''. mismatch, oryouneedpermissiontoviewandwriteitsdata .".
Simply looking at the above error, we generally think that the permission is insufficient or the file is opened. But I can see that the folder directory does not have any files, and the permissions are fine. It runs normally directly in the development environment.
I checked it on the Internet and found that although the variable is used to save the Excel name, but the Excel file address is specified when ExcelConnectionManger is set ), therefore, the file will still be searched after the deployment is complete.
650) this. width = 650; "title =" 2013-09-16 10-37-25.png "src =" http://www.bkjia.com/uploads/allimg/131229/21304641R-0.png "alt =" 105736675.png"/>
Because the file is deleted, an error is returned if SSISJob cannot be found during running.
Solution:
Place an Excel file in the original Excel address to locate SSISJob.
In addition, you can consider adjusting the DelayValidation attribute to "Ture" for verification at runtime.
This article is from the "follow SQL Server Technology" blog, please be sure to keep this source http://lzf328.blog.51cto.com/1196996/1297609