Leave feedback
  • Question

    Composition Center preview problem

Enter a new topic
  • Sonia Velli Sonia Velli
    0 likes 3843 views

    Hi,

    I have migrated a Composition Center project from SP4 to SP5. Since that, I cannot understand why some document definitions doesn't carry out to be preview, though I create successfully PDF results for the same documents, on patch mode.

    When previewing, I have this error message on the web portal : "An error occured. Please go back and try again. If the problem persists please notify the administrator.". But nothing is written on the project log file. It happens for two messages on my project, but the other are previewed correctly.

    Any idea why ? Thanks in advance for your answers.

    Best regards.

    Friday 07 January, 2011
  • Best Answer
    Sonia Velli Sonia Velli
    0 likes

    Hi,

    In my case, it was caused by a duplication of the document type I used in the project in the DocumentType table. So be carrefull during the process migration not to duplicate the document type. I think it was done during the Global Resources creation step, but I am not very sure of that.

    I think the best is to see with StreamServe support how to repair that. It works for me now.

    Good continuation.

    Tuesday 15 February, 2011
  • Christian Askland Christian Askland Administrator StreamServe Employee
    0 likes

    Do you get anything that looks like an error in the servicegateway.log or platform.log for your Service Gateway app?

    Monday 10 January, 2011
  • Sonia Velli Sonia Velli
    0 likes

    I find this in the servicegateway log file when the problem happens :

    0117 162227 (0942) 3 SoapRequestHandler: SOAP request received. SOAP action: http://schemas.streamserve.com/webservice/document/1.0/getdocumentattr ibutes
    0117 162227 (0100) 3 WSDocument::getDocumentAttributes: Succeeded.
    0117 162227 (0942) 3 SoapRequestHandler: SOAP request received. SOAP action: http://schemas.streamserve.com/webservice/schema/1.0/getschemas
    0117 162227 (0100) 3 WSSchema::getSchemas: Succeeded.
    0117 162227 (0942) 3 SoapRequestHandler: SOAP request received. SOAP action: http://schemas.streamserve.com/webservice/documentondemand/1.0/getdocu mentdefinitionsinuse
    0117 162227 (0100) 3 WSDocumentOnDemand::getDocumentDefinitionsInUse: Succeeded.
    0117 162227 (0942) 3 SoapRequestHandler: SOAP request received. SOAP action: http://schemas.streamserve.com/webservice/documentondemandcontent/mtom /1.0/getdocumentscontent
    0117 162227 (0415) 1 Service controller: Failed to invoke remote service http://schemas.streamserve.com/uid/service/storedmessage/1.0/Service_L ettreSimple/preview. (0x80000010: empty)
    0117 162227 (0047) 1 WSDocumentOnDemandContent::getDocumentsContent: Bad response from remote service: Remote service not found
    0117 162227 (0100) 3 WSDocumentOnDemandContent::getDocumentsContent: Succeeded.

     

    Kind regards.

    Tuesday 18 January, 2011
  • Tony RANNOU Tony RANNOU
    0 likes

    Hi Sonia,

    I test the migration too, I use the last version of the DBAT, and I have the same problem.

    Tony

    Wednesday 19 January, 2011
  • Olivier Picard Olivier Picard StreamServe Employee
    0 likes

    My Friend,

    Have a look at the picture.

    Best regards.

    Wednesday 26 January, 2011

    Attached files

  • Sonia Velli Sonia Velli
    0 likes

    Hi,

    Thank you for your answer. But I have already done it.

    Another idea ?

    Wednesday 26 January, 2011
  • David Shih David Shih StreamServe Employee
    0 likes

    One line in your Service Gateway's log file has me curious:

    Failed to invoke remote service http://schemas.streamserve.com/uid/service/storedmessage/1.0/Service_L ettreSimple/preview. (0x80000010: empty)

    Why is there a space in the "Service_L ettreSimple"? Can you double-check that? Also make sure you're not using any special characters in the name.

    Thursday 27 January, 2011
  • Sonia Velli Sonia Velli
    0 likes

    I don't know why there is a space on the log line mentionning the problem, but I can say that it's the same on the other lines.

    Otherwise, I have some news from the support and they confirm me the reproduction of this problem. So, we have to wait a correction now...

    Thank you for your ideas !

    Friday 28 January, 2011
  • Sonia Velli Sonia Velli
    0 likes

    Hi,

    In my case, it was caused by a duplication of the document type I used in the project in the DocumentType table. So be carrefull during the process migration not to duplicate the document type. I think it was done during the Global Resources creation step, but I am not very sure of that.

    I think the best is to see with StreamServe support how to repair that. It works for me now.

    Good continuation.

    Tuesday 15 February, 2011
  • Birgit van Pul Birgit van Pul
    0 likes

    Hi all,

    I'm having the same problem, can you please post the solution over here?

    Kind Regards.

    Wednesday 25 May, 2011
  • Sonia Velli Sonia Velli
    0 likes

    Hi,

    The hotfix 1054 and later should correct this specific issue.

    Kind regards.

    Wednesday 25 May, 2011
Next