When an item is submitted into Service Desk (both Incident and SR projects), you may be unable to "resolve" incidents if the "Reported By" user is an Occasional User.
In SBM on-demand, when submitting a new item in IM or SR , an alert should appear if content in the title field is similar to that in an existing KB article. This is not happening.
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.
When four Batch Stage jobs are running at the same time for the same package one of them failed with a 'RC=8' message 'CMN2660I - UNABLE TO OPEN CMNXX.ERO53D.SAF.#000036. SR 1 DATASET'
A file that fetched successfully under 12.x now produces the following in 14.1 FI "PCSTUFF: SR C~01.AAAA-SRC;2" /USER_FILENAME="F:\Work\My Documents\ sr .c" /NOEXPAND /NOOVERWRITE
Some scheduled reports are occasionally not being sent to the users. When this happens, the ns logs show the following error message: “ SR : Exception occured during invoking AE web service 'RunReportXML': Read timed out” The problem seems to occur when the scheduled report takes over a minute to run (60 seconds timeout built into the code for a web service that runs in a notification).
Audit job abended with a S0C4 in SERBSAM module. The package contains a single component of libtype SR 4. Libtype SR 4 has a baseline defined for it with a storage means of LA (Librarian Archie).
If it is coming from a customer reported DEFECT: 1. Describe the problem & the customer's use case scenario? when I run the agent install on Win2003 SR 2 32bit, I get ...\ah3srvc.exe is not a valid Win32 application. If I click on OK the same error message keeps on appearing and the installation does not complete.