ANCILE uPerform 4.40.0 Error while adding new document to the publish queue

[Former Member]

Hello,

We have installed Ancile uPerform 4.40 with WIN2008 and Oracle 11.2.0.1. The installation completed successfully and we enter the site with user admin. We have done post-installations steps ok.

Now we have created a project and add a template, and a new document. We add the new document to the publish queue, and then go to Administration->Server Administration->Publishing->View publishing queue, but the queue is empty. We can see various errors in logs:

File C:\Vignette\Collaboration\WWW\uPerformWS\logs\ServerErrors.xml

- <Entry Type="Error" Id="c401649f-6a18-43ac-bfa9-5ce20225026a">

<Date>6/21/2012 9:22:18 AM</Date>

  <ThreadID>4</ThreadID>

<ErrorCode>23-03-066</ErrorCode>

  <RoutineNamespace>RWD.uPerform.Data.OracleDataStore.ResetQueue</RoutineNamespace>

  <FriendlyMessage>An error occurred while resetting Publishing Queue.</FriendlyMessage>

  <Message>ORA-01843: mes no válido ORA-06512: en "GLOADM.TS_GETTIMESTAMP", línea 1 ORA-06512: en "GLOADM.TS_RESETQUEUES", línea 1 ORA-06512: en línea 1</Message>

  <StackTrace>at Oracle.DataAccess.Client.OracleException.HandleErrorHelper(Int32 errCode, OracleConnection conn, IntPtr opsErrCtx, OpoSqlValCtx* pOpoSqlValCtx, Object src, String procedure, Boolean bCheck) at Oracle.DataAccess.Client.OracleException.HandleError(Int32 errCode, OracleConnection conn, String procedure, IntPtr opsErrCtx, OpoSqlValCtx* pOpoSqlValCtx, Object src, Boolean bCheck) at Oracle.DataAccess.Client.OracleCommand.ExecuteNonQuery() at RWD.uPerform.Data.OracleDataStore.ExecSPNonQuery(String spName, List`1& params) at RWD.uPerform.Data.OracleDataStore.ResetQueue() at RWD.uPerform.WindowsService.QueueMonitor.ClearPublishingQueue()</StackTrace>

  <Parameters />

</Entry>

C:\Vignette\Collaboration\log\CollabConsole.txt

[21-jun-2012 10:20:47 (TP-Processor3_2)]: admin: http cmd: RunScript, TP-Processor3, object=1.11.1449

[21-jun-2012 10:20:47 (TP-Processor3_2)]: RunScript - executing script: pscripts\rwdAddDocToPublishQueue.py, threadId: TP-Processor3, user: Administrator.

[21-jun-2012 10:20:47 (TP-Processor3_2)]: http://MyWeb:80/uPerformWS/uPerformWS.asmx?WSDL

[21-jun-2012 10:20:47 (TP-Processor3_2)]: admin: Begin rwdAddDocToPublishQueue.main()

[21-jun-2012 10:20:47 (TP-Processor3_2)]: admin: Begin rwdAddDocToPublishQueue.sendChildren(1.11.1449)

[21-jun-2012 10:20:47 (TP-Processor3_2)]: admin: Begin rwdAddDocToPublishQueue.sendDoc(6bfc67e1133b43e6a8c755845fb247e3_es-ES)

[21-jun-2012 10:20:47 (TP-Processor3_2)]: admin: Begin rwdPublishDoc.sendDoc(6bfc67e1133b43e6a8c755845fb247e3_es-ES, 1340266845, admin)

[21-jun-2012 10:20:47 (TP-Processor3_2)]: admin: Sending document to publishing queue

        Name: Documeto

        OID: 1440

        Date: 1340266845

        By: admin

[21-jun-2012 10:20:47 (TP-Processor3_2)]: admin: Begin rwdWSConnector.AddToPublishingQueue(6bfc67e1133b43e6a8c755845fb247e3_es-ES, Documeto, 1440, 1340266845, admin)

[21-jun-2012 10:20:48 (TP-Processor3_2)]: admin: Error reading SOAP response

<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"><soap:Header><wsa:Action>http://schemas.xmlsoap.org/ws/2004/08/addressing/fault</wsa:Action><wsa:MessageID>urn:uuid:6c81b689-1457-4107-9f34-dd24f1b9e192</wsa:MessageID><wsa:RelatesTo>urn:uuid:10092fa8-454d-4400-bb1c-8e86516ecd36</wsa:RelatesTo><wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To><wsse:Security><wsu:Timestamp wsu:Id="Timestamp-fa794899-1ea6-4415-bf1e-1f6a04ca7389"><wsu:Created>2012-06-21T08:20:48Z</wsu:Created><wsu:Expires>2012-06-21T08:25:48Z</wsu:Expires></wsu:Timestamp></wsse:Security></soap:Header><soap:Body><soap:Fault><faultcode>soap:Server</faultcode><faultstring>System.Web.Services.Protocols.SoapException: Server was unable to process request. ---&gt; Oracle.DataAccess.Client.OracleException ORA-01843: mes no válido

ORA-06512: en "GLOADM.TS_GETTIMESTAMP", línea 1

ORA-06512: en "GLOADM.TS_ADDTOQUEUE", línea 1

ORA-06512: en línea 1    at uPerformWS.AddtoPublishingQueue(String DocumentGUID, String DocumentName, String ProjectOID, Int64 LastModifiedDate, String LastModifiedBy, String UserID, String UserOID)

   --- End of inner exception stack trace ---</faultstring><detail /></soap:Fault></soap:Body></soap:Envelope>

[21-jun-2012 10:20:48 (TP-Processor3_2)]: admin: End rwdWSConnector.AddToPublishingQueue()

[21-jun-2012 10:20:48 (TP-Processor3_2)]: admin: End rwdPublishDoc.sendDoc() - None

[21-jun-2012 10:20:48 (TP-Processor3_2)]: admin: End rwdAddDocToPublishQueue.sendDoc()

[21-jun-2012 10:20:48 (TP-Processor3_2)]: admin: End rwdAddDocToPublishQueue.sendChildren()

[21-jun-2012 10:20:48 (TP-Processor3_2)]: admin: End rwdAddDocToPublishQueue.main()

[21-jun-2012 10:20:48 (TP-Processor3_2)]: Redirect to:folder-1.11.1449

[21-jun-2012 10:20:48 (TP-Processor3_2)]: RunScript - returning from script: pscripts\rwdAddDocToPublishQueue.py, threadId: TP-Processor3.

[21-jun-2012 10:20:48 (TP-Processor3_2)]: redirecting to folder-1.11.1449

[21-jun-2012 10:20:48 (TP-Processor3_2)]: admin: http cmd: GetContainer, TP-Processor3, object=1.11.1449

The error seems to be with the timeStamp and the sentence in Oracle, I have checked in Oracle NLS_DATE_FORMAT

SQL> select * from nls_session_parameters;

PARAMETER

-----------------------------------------------------------------------

VALUE

-----------------------------------------------------------------------

NLS_LANGUAGE

SPANISH

NLS_TERRITORY

SPAIN

NLS_CURRENCY

Ç

PARAMETER

-----------------------------------------------------------------------

VALUE

-----------------------------------------------------------------------

NLS_ISO_CURRENCY

SPAIN

NLS_NUMERIC_CHARACTERS

,.

NLS_CALENDAR

GREGORIAN

PARAMETER

-----------------------------------------------------------------------

VALUE

-----------------------------------------------------------------------

NLS_DATE_FORMAT

DD/MM/RR

NLS_DATE_LANGUAGE

SPANISH

NLS_SORT

SPANISH

PARAMETER

-----------------------------------------------------------------------

VALUE

-----------------------------------------------------------------------

NLS_TIME_FORMAT

HH24:MI:SSXFF

NLS_TIMESTAMP_FORMAT

DD/MM/RR HH24:MI:SSXFF

NLS_TIME_TZ_FORMAT

HH24:MI:SSXFF TZR

PARAMETER

-----------------------------------------------------------------------

VALUE

-----------------------------------------------------------------------

NLS_TIMESTAMP_TZ_FORMAT

DD/MM/RR HH24:MI:SSXFF TZR

NLS_DUAL_CURRENCY

Ç

NLS_COMP

BINARY

PARAMETER

-----------------------------------------------------------------------

VALUE

-----------------------------------------------------------------------

NLS_LENGTH_SEMANTICS

BYTE

NLS_NCHAR_CONV_EXCP

FALSE

Could you help us?

Best regards

Jose

[satishra · Accepted solution]

most likely it's to do with locale settings(like language, date,timestamp format).

ORA-01843: not a valid month...

Make sure Ancile Server and Database and Operating system are in Correct locale format (language

Check the regional settings on the Application server to

Check the  Oracle database

date format. Check the

NLS_LANG settings

You may have to sync the  locale settings for Application Server and Database

Example like NLS_LANG to AMERICAN.AMERICA.AL32UTF8

[Former Member · Accepted solution]

Dear Satish,

Thanks for your reply. I fixed the problem the last week and the problem was with NLS_LANG. The problem is that uPerform is always expecting a US time and date format, and in the Oracle database is expecting a US date format:

I changed the NLS_LANG settings on Applications server and Database Server as described below:

1. Open command prompt

2. Type "regedit"

3. In the registry select following path : My computer ->HKEY_LOCAL_MACHINE -> SOFTWARE -> ORACLE -> KEY_Ora or Client ->

4. Look for the entry "NLS_LANG"

5. Change the value of this entry to : AMERICAN_AMERICA.AL32UTF8

6. Restart the Server and test add publishing queue.

The document is added correctly, but now the problem is that we cannot see the document in the queue, but the queue is not empty.

When the queue is empty the message is different as you can see in the following snapshot

We have detected another issue with the glossary, in the administration->Glossary we can not select a language, the list is empty.

We have opened a message to SAP....

Any ideas?

Regards

[Former Member · Accepted solution]

Hi,

Please create another post for this seperate issue as this avoids confusion and also makes information easier to find.

Kind Regards,

Matthew