Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML How to test a SOAP web service call from the server
Internally, SBM makes web service calls to itself. SBM Orchestrations often will call the Application Engine web services , but will also make web service calls to third party tools. These calls do not happen from the web browser on the workstation, but rather from the SBM server itself.
CMS-XML Unable to find new items in Work Center search
To rebuild the Work Center index, do the following: Look at the Indexer Directory Path located in the Configurator under the Common Services section. ... Look at the SSF.log located in [sbm]\ common \jboss405\server\default\log.
CMS-XML Web Services "[URL_TO_GSOAP sbminternalservices72]" returned an error
Web Services "[URL_TO_GSOAP sbminternalservices72]" returned an error
CMS-XML Exporting Excel Document from a Report Creates a Corrupt Document
There is no current limitation on the amount of text users may enter into a Mariner text attribute. However, when a report is run that is based on the attribute with large amounts of text, the Excel file is corrupted because the content exceeds the SQL Report Services 2000 (SRS) limit of 4060 characters for exporting text into an Excel cell.
CMS-XML When logging into Mariner, user has error "Logon Failed: Unable to connect to database"
This error is telling you that the Mariner/PPM application server cannot connect to the database server. Some common reasons this error may occur are:
CMS-XML Execution '...' cannot be found (rsExecutionNotFound) when running a Mariner report
The time on the SQL Server housing the reporting services databases is more than one minute out of synchronization from the SQL Reporting Services server. The report being run is sufficiently complex as to take more time to complete than SQL Reporting Services allows in its timeout setting.
CMS-XML Internet Explorer randomly hangs and/or the reports can no longer be run, and IIS must be reset
On the Microsoft Report Server, create a file called “helloreports.aspx” in the root of the Reports virtual directory. By default, this folder is C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services \ReportManager. The file should contain the following code:
CMS-XML Client-side browser requirements
Cache is another key elemete on the client-side. If the browser requests data from the server too often , performance will be slower. If it does not request data enough, it could show outdated information. Below are
CMS-XML Adobe Reader could not open "filename.pdf" because it is either not supported or because the file has been damaged
cscript.exe adsutil.vbs enum /P w3 svc /1/root/mariner/controls
CMS-XML Unable to execute a command line using Ext.CmdLineWait() function
When using Ext.CmdLineWait() in App Script, commands are executed in the context of the Internet Information Services (IIS) application pool. If the script is called from a transition or URL, the script runs under the application pool for the TMTrack virtual directory which defaults to DefaultAppPool. If the script is called from a notification in 10.1+, it will run under the gsoap_pool.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs