We recently updated from SDM 12.9 to 17.1. We never had any issues with using GRLoader (manually or through CCA), until now. When I ran GRLoader to update CI's manually (CCA has no issues), I get these errors:
07/05 10:40:01.643 INFO GRLoader 493 ===============================================================================
07/05 10:40:01.646 INFO GRLoader 494 GRLoader Started - load from xml file(/home/otdseee/XML/BillableServers.xml) - to CMDB - CI Updates allowed / inserts not allowed
07/05 10:40:01.647 INFO GRLoader 510 ===============================================================================
07/05 10:40:03.585 INFO grDataMgr 200 Multi-tenancy is not enabled
07/05 10:40:03.593 INFO grReader 188 Processing Configuration Items
07/05 10:50:03.724 ERROR grDataMgr 773 checkCIExists WebService error while checking if CI Exists(<server1>.state.nj.us,<server1>,,,,<server1>.state.nj.us,). Exception in checkCIexists: Read timed out
07/05 11:00:04.498 ERROR grDataMgr 773 checkCIExists WebService error while checking if CI Exists(<server2>.state.nj.us,<server2>,,,,<server2>.state.nj.us,). Exception in checkCIexists: Read timed out
Also, the error xml files states the following:
<!--ERROR: Unable to locate ID (null)-->
I used -a and -E options when executing the command. The service account we use has "Administration" Access Type.
According to this discussion: https://communities.ca.com/message/241785018?commentID=241785018#comment-241785018, Gordon_Preston mentioned that the account should have privileges in both SOAP Web Service API Role and Command Line Utility Role. I don't see neither of those roles in the list of roles. So.. Administration is not enough?
In any case, can someone please help me with this issue? Has anyone else have issues running