Hi , 

I have a SQL server agent job which runs SSIS package as the daily job. The SSIS package contains multiple child package. Its a master package which calls other SSIS package. The master package calls 23 SSIS packages, few of the packages runs in parallel. I am getting the below 2 different errors more frequently. It fails only in the production server, I scheduled the job in UAT server, it did not fail. Also when we run the master package with out sql agent job, it did not fail. 

Error 1 :

R6025  - pure virtual function call.  The return value was unknown.  The process exit code was 255.  The step failed.

Error 2 : The step did not generate any output.  The return value was unknown.  The process exit code was -1073741819.  The step failed.

We tried browsing for the answers ,no luck. It failing in live , so we need to run the package manually in live server every time. 

Please help me to resolve this issue. Thanks in advance.

Regards, 

Dhivya Sivakumar

Hi Dhivya, 

For Error 1          

       Can you please let me know whether you are calling any Perl Scripts withing SSIS packages? Sometimes, the PERL installation may not be correct and thus the libraries will give errors when used in an executable. Also, are the OS on the UAT server and the Production server one and the same? If Perl is used, Are the Latest versions of the DLLs installed on the machine? 

For Error 2, 

          Have you developed the SSIS Packages in a lower version of SQL Server and then used within higher version of SQL Server without upgrading the packages (Especially applicable if the Package has Script tasks).

    Reference : http://notesonmicrosoft.blogspot.in/2013/11/ssis-execution-fails-when-called-by-sql.html

Please verify if the UAT and the Production servers are having the same bit size (32 bit or 64 bit).

Hi Vijeth, 

Thanks for the reply. I have copied the details of the prod and UAT server below, 

We are not using any perl scripts inside the SSIS package. Most of the packags uses, txt file, excel file, foxpro DB, Progress DB as the source system. Few packages are having script task used. I believe the packages are developed using the same version. 

UAT and live, both are having the 64 bit environment. 

LIVE Details
Microsoft SQL Server Management Studio	10.50.2500.0
Microsoft Analysis Services Client Tools	10.50.2500.0
Microsoft Data Access Components (MDAC)	6.1.7601.17514
Microsoft MSXML	3.0 5.0 6.0
Microsoft Internet Explorer	9.11.9600.16428
Microsoft .NET Framework	2.0.50727.5477
Operating System	6.1.7601
UAT Details
Microsoft SQL Server Management Studio	10.50.1600.1
Microsoft Analysis Services Client Tools	10.50.1600.1
Microsoft Data Access Components (MDAC)	6.1.7601.17514
Microsoft MSXML	3.0 4.0 5.0 6.0
Microsoft Internet Explorer	9.10.9200.17054
Microsoft .NET Framework	2.0.50727.5483
Operating System	6.1.7601

Hi Dhivya Priya, 

      Unfortunately I am not aware of FoxPro or Progress databases. But when I encounter issues such as these, I would try to isolate the issue in the following ways. Please note that many of these steps may or may not be possible for you to execute in your environment. 

1) Run the Package manually and check whether it runs successfully. 

2) If Step 1 is successful,

a) Point the same package to the UAT database and run it and check whether it runs successfully or not.

b) In UAT database, point to the Production database and run the package. 

     These steps will help us identify whether the problems lies within the package or the Environment. 

3) Run the Package manually in production Environment using dtexec utilily. 

4) Check the ID used to run the SQL Agent job and modify to an account with elevated permissions or GRANT more permissions to the existing ID. 

This is based on the assumption that the SSIS Package is deployed on the UAT and Production dat

Hi Vijeth, 

Thanks for your reply. 

1) Run the Package manually and check whether it runs successfully.  - No Failures. Package completed succesfully

2) If Step 1 is successful,

a) Point the same package to the UAT database and run it and check whether it runs successfully or not. - We tried to schedule the package almost for 1 month. No failures in UAT. 

b) In UAT database, point to the Production database and run the package. - I am not sure, if i can do this.I will try and let you know the result.

     These steps will help us identify whether the problems lies within the package or the Environment. 

3) Run the Package manually in production Environment using dtexec utilily. - No Failures. Success.

4) Check the ID used to run the SQL Agent job and modify to an account with elevated permissions or GRANT more permissions to the existing ID. - The account used currently is having all the privileges. Its the most powerful user in live DB. 

Regards, 

Dhivya S

Hi Divya,

As stated if your package works well manually and not in sql agent job then please check the below settings :

1. Package configuration files supplied. Please check all the attribute values in it.

2. Check the 32 bit environment if required

As your package contains the script component then please check the .net framework it points to or if it throws an error when opened.

Hi Supriya, 

Thanks for your reply.

Live server is 64 bit environment.- It is not possible to change the live server to 32 bit. 

We have requested to upgrade the .Net framework version in live, when compared it is lower than UAT version. 

I will let you know once the upgrade is done and whether it helped. 

Also please suggest if have any other solution in your mind . 

Thanks in advance. 

Regards, 

Dhivya s

Hi Dhivya Priya,

According to your description, there is a master package calls 23 SSIS packages, when you run the package use sql server agent job, you got the error message.

According to my knowledge, error code 1073741819 means Windows operation system denies a process to read or write in a memory which has not been assigned to it. It indicates that the executed program has terminated abnormally or crashed.

To troubleshoot the problem, please refer to the following steps:

1. Make sure that you checked off - 32 Bit Runtime.
   
2. In Object Explorer, expand a server.
   
3. Expand SQL Server Agent.
   
4. Right-click Proxies and select New Proxy.
   
5. On the General page of the New Proxy Account dialog, specify the proxy name, credential name, and description for the new proxy. Note that you must create a credential first before you create a proxy if one is not already available.
   
6. Check the appropriate subsystem for this proxy.
   
7. On the Principals page, add or remove logins or roles to grant or remove access to the proxy account.

Since the issue the error message is generic, we can enable logging in your SSIS package, then analyze the specific error message.

If you have any more questions, please feel free to ask.

Thanks,
Wendy Fu

Hello all, 

Nothing helped me. The user which i am using to execute the JOB is a super user, which has all the privileges. 

We have the logging enabled in the package and also on error we have a send mail option. I believe the onerror event is not trigger in this case. we are not receiving any error mail.No error message logged in ssis log tables.

The job fails and when we look into the history we are seeing the above 2 error message in the agent. 

Any help is appreciated. Please