I am trying to run an SSIS package and I am getting the following error:
Error Messages:
The SSIS Execution failed

Number of warnings: 2
Warning (0):SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.

Warning (1):SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.

Number of errors: 2
Error (0):The script threw an exception: Unable to connect to the remote server Error (1):The script threw an exception: Unable to connect to the remote server From, GetErrorValues (0)


I am using Visualcron 5.5.5 on a Windows 2003 32 bit server. The SQL server is not on the local server, but the SSIS package is on the same server as Visualcron. I can run the SSIS package manually or in a batch file successfully.

Could you verify that this is not a permission problem by:

1. disconnect the client
2. stop the VisualCron service
3. go to the VisualCron folder and double click to start VisualCronService.exe
4. start the client
5. run again

---

I ended up changing the service to logon with a domain admin account. I saw someone else had done this from reading another post. Is this the recommended method. Surely, we don't have to use domain admin permissions. Although, that does cover our bases, but probably leaves a security hole.

We will build a new version for you testing this. We will get back to you.

---

Please try this version:

http://neteject.com/down...Cron/VisualCron5.5.6.exe 

You need to change the following settings:

1. change back your service to run as SYSTEM
2. Add a Credential (not sql credential but the other one - a local admin or domain user which can access that file/database - i.e. the same as you ran your service as). Then select that Credential
3. select (in top of SSIS settings) if you are running against SQL 2005 or 2008
4. Try the Task again and please get back to us

---

I installed version 5.5.6 as suggested, but it didn't work very well. I tried to run the task without changing the service back to system, and the task did not finish. It hung in an executing state. When I tried to change the service back to System account, the service did not start. Then tried changing it back to domain admin and it did not start. I am going to remove 5.5.6 and reinstall 5.5.5.

We are investigating a similar issue and another customer is running 5.5.6. as well:

http://www.visualcron.co....aspx?g=posts&t=1148 

What OS and SQL version are you using?

---

The OS is server 2003 standard 32 bit. It is a VMWare virtual. The database is not on the local machine. It is clustered.

1. What is the sql version?
2. are you able to run that ssis task manually from the VMWare machine?
3. did you check the standard error output column after executing?

---

The SQL version is 2005. I am running VC from the VMWare instance.