| |
Results |
|
Cannot log into RM Browser after install or upgrade – IIS Error XML 404 – Dim RM 2009 R2
|
Please go to IIS Manager Web Service Extensions Highlight All Unknown CGI Extensions then select ALLOW
|
|
|
|
After upgrade, when run report, get error "Exceeded maximum number of attempts to invoke webservice. methodname: GetDBConnectionsAsXml"
|
Exceeded maximum number of attempts to invoke webservice.\n status: ProtocolError\n url: https://servername/Mariner/ WebServices /peswebconfig.asmx\n methodname: GetDBConnectionsAsXml\n.
|
|
|
|
RLM: After upgrade from 2.1 to 3.5 to 4.0 get SOAP Error checkUniqueness
|
In many of the orchestrations within Release Control, checkUniqueness is the first web service called. Therefore, if there is a problem it will often be with this service. In this situation, the upgrade to 3.5 was accomplished without the benefit of the upgrade documentation and there are many manual steps that should have been performed.
|
|
|
|
Custom written ZMF web service routines failing after upgrade to 8.1.2 zmfws.war
|
After upgrading to the 8.1.2 GA version of the ZMF Web Services (zmfws.war) several homegrown routines based on sample code distributed to customers failed with the following errors :
|
|
|
|
After upgrade to 6.6.1, relational field data returned by web service call is different
|
In 6.6.1, however, instead of the TITLE being returned, a value such as 1009:4 is returned. The number before the colon is the Table ID (TS_ID from TS_TABLES); the number after the colon is the TS_ID of the selected item in the aux table. This was changed since programs using these returned values to update the record in the aux table would get errors if there were multiple records with the same title, since the system wouldn't know which to update.
|
|
|
|
After upgrade to SBM 10.1.3+ orchestration workflow may get error "Invalid item id 0 for table 0."
|
Along with that change you created an external orchestration event that uses the "ItemId_TableRecId" element in another application to run an SBM web service method. For illustration the following screen shot shows the "Issue Id" field was renamed to "Acme" in this application. In versions of SBM prior to 10.1.3 the Element in the Event Definition would use the field name like below "Acme_TableRecId".
|
|
|
|
Web Services "[URL_TO_GSOAP sbminternalservices72]" returned an error
|
This may be an issue with the way users were imported / created in SBM. Perhaps, this is caused by an upgrade from an old version of TeamTrack. Check the TS_TIMEPREFERENCES column in the TS_USERS table in the Application Engine database for the user. The only valid values for TS_TIMEPREFERENCES are 0 or 1. If you have any other value in TS_TIMEPREFERENCES, replace it with a 0 or 1.
|
|
|
|
After upgrade from RLC 6.1 to RLC 6.2, new Release Package gives: java.io.IOException: File 'createDeploymenPath.groovy' not found in current ClassPath
|
After upgrading from RLC 6.1 to RLC 6.2, when the users try to create a new Release Package, they get the following error: Error occurred during web service invocation: RequestPost
|
|
|
|
The service cannot be found for the endpoint reference when running orchestration and the orchestration doesn't run after upgrading to SBM 11+
|
For synchronous orchestrations the following would show in the form being submitted. Error occurred during web service invocation: SOAP Fault Code: axis2ns1:Client
|
|
|
|
SBM 11.4.1 Hotfix 1: Repository gives error 500, Exchange web services, multi select values empty, blank form when SetFieldValue, Oracle max list is 1000
|
DEF321205: Application Repository fails to start and gives error 500 DEF321255: Mail Client using Exchange web services no longer working after upgrade to SBM 11.4.1 DEF321327: Multi Selection Fields do not get populated correctly and become empty
|
|
|
