Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Rest Grid Widget - get more logging from the SBMProxy
Rest Grid Widget - get more logging from the SBMProxy
CMS-XML Making a call through the SBM Proxy using JavaScript how can I control whether the SSO Token is added to the request header or not?
You may be using JavaScript to make a request to an external website. When you do this you have to use the sbmproxy to avoid cross site scripting issues but depending on your needs you might not want the SSO token to be included in the header of the request you're going to. A good example where you might not want the SSO token included might be when making a rest call to another Serena product that uses SSO.
CMS-XML SBM: Rest Grid connecting to ZMF Connector returns error 500
Unknown error received from https://SERVER/ sbmproxy /xhp [url: 'http://SERVER:8080/almsernet/services/SernetProxyHttpServer?system=ZMF&hostName=999.999.999.999&hostPortId=8888&responseType=JSON&request=PACKAGE%2FGENERAL%2FSEARCH%2Fpackage%3Dxxxx%2CsearchForDevelopmentStatus%3DY% 2CsearchForFrozenStatus%3DY']
CMS-XML Rest Grid widget gives "We did not find any matches for your request" with error 401
We did not find any matches for your request Unknown error received from http://sbm-10121/ sbmproxy /xhp [url: 'http%3A%2F%2Fsbm-10121%3A8080%2Falm%2Frest%2FVaultService%2FgetVaultBaselineProjects%3FcomposerMode%3Dfalse%26providerName%3DDIM*', xslfile: 'xml2json-discard-prefix.xslt'] (401)
CMS-XML Invalid user name or password with SSO enabled, cannot log into Application Repository if SSO is disabled
If you do not get an invalid post request, and instead get an internal 500 error referencing the sbmproxy , then set the gsoap virtual directory to use the same application pool that the tmtrack virtual directory uses. This will be fixed in a later release, but is a valid workaround in current versions of SBM.
CMS-XML How to troubleshoot the Rest Grid widget when you get "We did not find any matches for your request" instead of results.
We did not find any matches for your request Unknown error received from http://sbm-10121/ sbmproxy /xhp [url: 'http%3A%2F%2Fsbm-10121%3A8080%2Falm%2Frest%2FVaultService%2FgetVaultBaselineProjects%3FcomposerMode%3Dfalse%26providerName%3DDIM*', xslfile: 'xml2json-discard-prefix.xslt'] (404)
CMS-XML REST Grid does not give any data, even when there is data to show
Several lines will appear. Look for the one referencing / sbmproxy in the path, and click on it. This will open the details for this call.
CMS-XML Get a "Connection Error. Check your network connection or contact your system administrator" when opening the SBM Application Administrator. ( Manage Resources, Resources or Work Center icons are greyed out )
Below, we describe different causes for this error: Use Case 1: The sbmproxy isapi_redirect.dll is not setup in IIS. Open IIS Manager
CMS-XML SBM Unable to get to IIS URL with HTTP 500 error / Uninstall SBM from IIS
Highlight the web site Double-click on ISAPI Filters highlight sbmproxy and sbmrewrite (one at a time) and click Remove under actions. Now move up the tree of IIS Manager and select the server name.
CMS-XML Logging into Request Center and get "Error getting catalog: Not found" error
Double click the ISAPI Filter icon Verify you have a filter called " sbmproxy " and it shoud be pointing to the following dll by default. C:\Program Files\Serena\SBM\Application Engine\bin\isapi_redirect.dll
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs