Deploy failed in generic control network
Answers
- Ensure that all of your services are running correctly
- Ensure that all of the PLC's are communicating and you have a valid connection to every OPC server
- If you have redundancy configured, ensure that BOTH connections to the OPC server are properly configured and running ( or in standby with no error )
- Hold Shift Key and Press "Deploy" to force a Full Deploy.
- Log files can be found on (both) Connectivity Servers where the Softpoint Server Service is running at \OperateITData<x>\AdsServer\ServiceGroupData{guid-for-your-PLC-Connect}\L
og Files
- Warmstart files are in OperateITData<x>\AdsServer\Generic Control Network Data {Your Guid}\ *.TXT (There are 3 files)
The log files are circular, the latest error message is NOT at the end of the file. Search for 'End of Log'
A common problem is where you have mixed redundancy where some PLCs are or are not redundant. IIRC, the PLC connect config files on both servers should be the same. If a compile fails or redundancy is mis-configured then you can find that one server doesnt compile properly and the warmstart files are not the same.
You can also get this issue when you Export/Import between versions.
Go to the logfile for Deploy Manager:
C:\Operate IT Data\Ads Server\ service group data\ Logfile.
Then the Deploy stop at the first error, you maybe have many.
Then search for "End of Log" and go back in time and see where the Deploy stop and look on the item.
Do a dummy change on this item, both in the Signal Configuration Aspect and in the Alarm Event Aspect.
Then do a new deploy and see if the error is moved to another object.
If this new object is of same Object Type, then you can try to do the dummy changes in the Object type structure instead.
and a new deploy...
This can take time.... but if you always with the same object even after dummy changes then send an e-mail to the support with all the PLC Connect logfiles not only for the deploy manager.
Add new comment