Topic
15 replies Latest Post - ‏2013-10-24T18:47:29Z by ChrisGloe
johnydo
johnydo
19 Posts
ACCEPTED ANSWER

Pinned topic IBM Docs 1.0.4

‏2013-10-02T14:01:05Z |

Hi,

I have installed a IBM Connections 4.5 CR2 environment with the new IBM Docs version 1.0.4. I have no problems with the installtion and the IBM Connections works fine. But I have a problem when I click to a document view for an example a Worddocument (doc or docx). I get a error message in the SystemOut.log from the DocsViewerCluster:

VersionCheckF E   Viewer application version is incompatible with Conversion!

Im not sure what the problem is. My environment:

  • IBM WebSphere Application Server 8.0.0.5 with the fixes PM71430, PM76920, PM85834, PM62615 and PM83196
  • IBM Connections 4.5 CR2 with CCM
  • IBM Docs 1.0.4
  • IBM DB2 9.7 fp7

IBM Docs, Viewer Server and Proxy on the same node but in different JVMs. -> OS is RedHat Enterprise Linux 5.8 64Bit

IBM Conversion Server -> OS Windows 2008 R2 64Bit

 

Can everybody help me?

 

  • ChrisGloe
    ChrisGloe
    60 Posts
    ACCEPTED ANSWER

    Re: IBM Docs 1.0.4

    ‏2013-10-03T13:26:48Z  in response to johnydo

    Hello,

    Check Environment -> WebSphere variables *VERSION*

    Make sure the CONVERSION_VERSION, DOCS_VERSION, and VIEWER_VERSION all match.  They need to match.  If they don't, something went wrong with one of your installs.

    If they match, resync the nodes to ensure they all have the same values for these WebSphere variables and then restart your viewer and conversion clusters and retry.

    • johnydo
      johnydo
      19 Posts
      ACCEPTED ANSWER

      Re: IBM Docs 1.0.4

      ‏2013-10-08T17:01:27Z  in response to ChrisGloe

      Hi,

      in all variables I have the version 1.0.4 and I have resync all nodes and restart my environment but the same problem. I Think the problem is the NFS Client Share from my WIndows system to the NFS Server on Linux.

      How can I check the NFS connections?

      • ChrisGloe
        ChrisGloe
        60 Posts
        ACCEPTED ANSWER

        Re: IBM Docs 1.0.4

        ‏2013-10-11T20:40:02Z  in response to johnydo

        To check your NFS connections from the Windows node:

        1) Check the SystemOut.log for the Conversion server.  When the application starts, it will do the mount of the Docs and Viewer Shares.  You can search the log for 'mount'.  The log will either indicate success or will tell you the error to check.

        2) If the mounts are successful, you can just try to edit a file from whatever drive letter you mounted (using Explorer or something like that).  It should let you write to the directory.  If not, you have a problem with your NFS configuration or a UID/GID mismatch.

        I don't believe however that the NFS mount would cause the error you indicated above.  Another item to check is to verify routability to conversion and docs and viewer:

        https://<ihsnode>/docs/version.txt

        https://<ihsnode>/conversion/version.txt

        https://<ihsnode>/viewer/version.txt

        They all should return a version and it should be the same version.

        • johnydo
          johnydo
          19 Posts
          ACCEPTED ANSWER

          Re: IBM Docs 1.0.4

          ‏2013-10-14T06:56:58Z  in response to ChrisGloe

          Hi,

          I checked the version but I think its ok?

          {
              "build_description" : "IBM Docs 1.0.4" ,
              "product_name" : "IBMDocs",
              "build_version" :  "1.0.4" ,
              "build_timestamp" : "20130829-1702"
          }


          {
              "product_name" : "IBM Conversion",
              "build_version" : "1.0.4" ,
              "build_timestamp" : "20130829-1702"
          }


          {
              "build_description" : "1.0.4",
              "product_name" : "Viewer",
              "build_version" :  "1.0.4" ,
              "viewer_version" : "20130829-1703"
          }

        • johnydo
          johnydo
          19 Posts
          ACCEPTED ANSWER

          Re: IBM Docs 1.0.4

          ‏2013-10-14T06:58:57Z  in response to ChrisGloe

          Hi,

          I checked the SystemOut.log from the ConversionServer and I found the problem with the NFS Share:

          I   Mount Shared Storage for IBM Docs: [mount, -o, mtype=soft, casesensitive=yes, anon, :, //server.docs.com/docs_data]

          O Sub-Process STD_OUT[ERROR - Invalid command line argument]

          The problem is the doublepoint : in the mount command? How can I change this?

           

    • johnydo
      johnydo
      19 Posts
      ACCEPTED ANSWER

      Re: IBM Docs 1.0.4

      ‏2013-10-14T07:14:32Z  in response to ChrisGloe

      Hi,

      here is my responsefile from the ConversionServer installation:

      conversion_install_root=D:\IBM\IBMConversion
      docs_shared_storage_type=nfs
      viewer_shared_storage_type=nfs
      conversion_shared_data_root=\\docs.server.com\docs_data
      conversion_shared_data_server=
      conversion_shared_data_server_viewer=
      conversion_shared_data_root_remote=
      viewer_shared_data_name=\\docs.server.com\docs_viewer_data
      conversion_shared_data_root_remote_viewer=
      was_install_root=D:\IBM\WebSphere\AppServer
      was_soap_port=8879
      scope_name=DocsConversionCluster
      software_mode=Premise
       

      • ChrisGloe
        ChrisGloe
        60 Posts
        ACCEPTED ANSWER

        Re: IBM Docs 1.0.4

        ‏2013-10-15T01:33:40Z  in response to johnydo

        You response file should have been created something like this instead:

        conversion_shared_data_root=w:
        conversion_shared_data_server=docs.server.com
        conversion_shared_data_server_viewer=docs.server.com
        conversion_shared_data_root_remote=docs_data
        viewer_shared_data_name=v:
        conversion_shared_data_root_remote_viewer=docs_viewer_data

        This assumes your NFS server is docs.server.com and you exported docs_data for your docs share and docs_viewer_data for your viewer share.  To fix it post install you would need to do 2 things:

        1) Update the storage section of the <CONVERSION_INSTALL_ROOT>/config/conversion-config.json with the values like above.

        2) Update the *SHARE* WebSphere variables (for example DOCS_SHARE) with matching values.

        For example using the above values, DOCS_SHARE would be w: and VIEWER_SHARE would be v:

        DOCS_SHARED_DATA_ROOT would be docs_data, etc.

         

        • johnydo
          johnydo
          19 Posts
          ACCEPTED ANSWER

          Re: IBM Docs 1.0.4

          ‏2013-10-15T12:33:53Z  in response to ChrisGloe

          Hi,

          I have changed the conversion-config.json and the envrionment variables. But after a restart I have the same problem the wrong command is used:

          Mount Shared Storage for IBM Docs: [mount, -o, mtype=soft, casesensitive=yes, anon, docs.server.com:docs_data, w:]
          [15.10.13 14:26:18:399 CEST] 0000001e SystemOut     O Sub-Process STD_OUT[ERROR - Invalid command line argument]

           

          I have test the mount command on my Windows system and I used this command:

          C:\>mount -o mtype=soft casesensitive=yes anon \\docs.server.com\docs_data w:

          w: is now successfully connected to \\docs01.greenhouse.ffm.fum.de\docs_data

          This command is working.

           

          After that I have changed conversion-config.json to this:

              "shared_storage" :
              {
                  "docs": {
                      "type": "nfs",
                      "server": "\\docs.server.com",
                      "from": "\docs_data",
                      "to": "w:",
                      "retry": "-1",
                      "timeo": "-1"
                  },
                  "viewer": {
                      "type": "nfs",
                      "server": "\\docs.server.com",
                      "from": "\docs_viewer_data",
                      "to": "v:",
                      "retry": "-1",
                      "timeo": "-1"
                  }

           

          After restart my ConversionServer did not start because I get an exeption:

          E   CLFAE1021E: Can't get conversion service.
                                           java.lang.IllegalArgumentException: Malformed config file: D:\IBM\IBMConversion\config\conversion-config.json can not be parsed successfully.

           

          What is the correct configuration in this file on a Windows system?

           

          Updated on 2013-10-15T12:34:32Z at 2013-10-15T12:34:32Z by johnydo
          • johnydo
            johnydo
            19 Posts
            ACCEPTED ANSWER

            Re: IBM Docs 1.0.4

            ‏2013-10-15T12:48:25Z  in response to johnydo

            Hi,

            I have found my problem. The correct value for Windows is:

            docs_shared_storage_type=nfs
            viewer_shared_storage_type=nfs
            conversion_shared_data_root=w:
            conversion_shared_data_server=docs.server.com
            conversion_shared_data_server_viewer=docs.server.com
            conversion_shared_data_root_remote=/docs_data
            viewer_shared_data_name=v:
            conversion_shared_data_root_remote_viewer=/docs_viewer_data
             

            The correct mount command for Windows is:

            C:\>mount -o mtype=soft casesensitive=yes anon docs.server.com:/docs_data w:

             

            I   Mount Shared Storage for IBM Docs: [mount, -o, mtype=soft, casesensitive=yes, anon, docs.server.com:/docs_data, w:]
            [15.10.13 14:44:53:676 CEST] 0000001c SystemOut     O Sub-Process STD_OUT[w: is now successfully connected to docs.server.com:/docs_data]

            Updated on 2013-10-15T12:48:44Z at 2013-10-15T12:48:44Z by johnydo
  • johnydo
    johnydo
    19 Posts
    ACCEPTED ANSWER

    Re: IBM Docs 1.0.4

    ‏2013-10-15T12:55:08Z  in response to johnydo

    Hi,

    after I solved the problem with the NFS Share I start my IBM Docs and Connections System. I can see the "View" and "Edit in IBM Docs" buttons. I have create a Word 2013 document "dok1.docx" and uploaded this to the Connections Files Application.

    After I click to the "View" button I get a error message in my browser:

    Conversion service is not available.

    IBM Docs conversion service is not available. Your request cannot be processed at this time. Try again later or contact your system administrator.

     

    Any ideas?

     

    Updated on 2013-10-15T13:44:21Z at 2013-10-15T13:44:21Z by johnydo
    • johnydo
      johnydo
      19 Posts
      ACCEPTED ANSWER

      Re: IBM Docs 1.0.4

      ‏2013-10-15T13:13:57Z  in response to johnydo

      When I click to the "Edit in IBM Docs" button I can see this message in my browser:

      Loading...
      One moment please, we are processing your document for editing on the web.

       

      After a long time I get this message:

      The document conversion timed out.

      At this time, the document takes too long to convert. Try again later.

       

      In the SystemOut.log from my ConversionCluster I can see this messages:

      [15.10.13 15:41:53:520 CEST] 00000072 NFSFileUtil   I   failed to copy file by retry: 20 from: D:\IBM\IBMConversion\data\temp\target-c5a95b98-e2d7-468c-b1c0-2cc4cf7a0e0a\result.json to: w:\draft\default_org\draft\298\139\2b9047ef-5c56-4ae4-bc2a-4fb9c23825d5\temp\3afa38d2-7f2d-46df-a515-2b753500de3a\concord\result.json
      [15.10.13 15:41:53:520 CEST] 00000072 NFSFileUtil   I   failed to copy file from: D:\IBM\IBMConversion\data\temp\target-c5a95b98-e2d7-468c-b1c0-2cc4cf7a0e0a\result.json to folder: w:\draft\default_org\draft\298\139\2b9047ef-5c56-4ae4-bc2a-4fb9c23825d5\temp\3afa38d2-7f2d-46df-a515-2b753500de3a\concord
      [15.10.13 15:41:53:520 CEST] 00000072 ConversionWor I   copy target file from local: D:\IBM\IBMConversion\data\temp\target-c5a95b98-e2d7-468c-b1c0-2cc4cf7a0e0a to shared storage: w:\draft\default_org\draft\298\139\2b9047ef-5c56-4ae4-bc2a-4fb9c23825d5\temp\3afa38d2-7f2d-46df-a515-2b753500de3a\concord cost time: 4415 ms
      [15.10.13 15:41:53:551 CEST] 00000072 ConversionWor I   conversion completed, false cost 10218ms, application/vnd.openxmlformats-officedocument.wordprocessingml.document, text/html, w:\draft\default_org\draft\298\139\2b9047ef-5c56-4ae4-bc2a-4fb9c23825d5\temp\5d3a85e7-4519-4624-8a09-fd78fbaccb82\contentfile.docx
      [15.10.13 15:41:55:282 CEST] 00000065 NFSFileUtil   I   failed to copy file by retry: 20 from: D:\IBM\IBMConversion\data\temp\target-1ea671d0-5838-44bb-920b-8608614e9b63\content.html to: w:\draft\default_org\draft\298\139\2b9047ef-5c56-4ae4-bc2a-4fb9c23825d5\temp\upload\79c23c58229f6a718215ced51a501c9b\concord\content.html
      [15.10.13 15:41:55:282 CEST] 00000065 NFSFileUtil   I   failed to copy file from: D:\IBM\IBMConversion\data\temp\target-1ea671d0-5838-44bb-920b-8608614e9b63\content.html to folder: w:\draft\default_org\draft\298\139\2b9047ef-5c56-4ae4-bc2a-4fb9c23825d5\temp\upload\79c23c58229f6a718215ced51a501c9b\concord
      [15.10.13 15:41:55:282 CEST] 00000065 NFSFileUtil   I   failed to copy folder from: D:\IBM\IBMConversion\data\temp\target-1ea671d0-5838-44bb-920b-8608614e9b63 to folder: w:\draft\default_org\draft\298\139\2b9047ef-5c56-4ae4-bc2a-4fb9c23825d5\temp\upload\79c23c58229f6a718215ced51a501c9b\concord
      [15.10.13 15:41:55:282 CEST] 00000065 ConversionWor W   CLFAE525W: Fail to copy source files from local to NFS
      [15.10.13 15:41:57:466 CEST] 00000065 NFSFileUtil   I   failed to mkdirs by retry: 20 file: w:\draft\default_org\draft\298\139\2b9047ef-5c56-4ae4-bc2a-4fb9c23825d5\temp\upload\79c23c58229f6a718215ced51a501c9b\concord
      [15.10.13 15:41:57:466 CEST] 00000065 NFSFileUtil   I   failed to copy file from: D:\IBM\IBMConversion\data\temp\target-1ea671d0-5838-44bb-920b-8608614e9b63\result.json to: w:\draft\default_org\draft\298\139\2b9047ef-5c56-4ae4-bc2a-4fb9c23825d5\temp\upload\79c23c58229f6a718215ced51a501c9b\concord\result.json, will retry shortly.
                                       java.io.FileNotFoundException: w:\draft\default_org\draft\298\139\2b9047ef-5c56-4ae4-bc2a-4fb9c23825d5\temp\upload\79c23c58229f6a718215ced51a501c9b\concord\result.json (The system cannot find the path specified.)
          at java.io.FileOutputStream.<init>(FileOutputStream.java:205)
          at java.io.FileOutputStream.<init>(FileOutputStream.java:156)
          at com.ibm.symphony.conversion.service.common.util.NFSFileUtil.nfs_copyFileToFile(NFSFileUtil.java:566)
          at com.ibm.symphony.conversion.service.common.util.NFSFileUtil.nfs_copyFileToDir(NFSFileUtil.java:692)
          at com.ibm.conversion.service.rest.servlet.ConversionWork.copyTargetToNFS(ConversionWork.java:146)
          at com.ibm.conversion.service.rest.servlet.ConversionWork.run(ConversionWork.java:610)
          at com.ibm.ws.asynchbeans.J2EEContext$RunProxy.run(J2EEContext.java:269)
          at java.security.AccessController.doPrivileged(AccessController.java:252)
          at javax.security.auth.Subject.doAs(Subject.java:495)
          at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:132)
          at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:90)
          at com.ibm.ws.asynchbeans.J2EEContext$DoAsProxy.run(J2EEContext.java:336)
          at java.security.AccessController.doPrivileged(AccessController.java:280)
          at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:804)
          at com.ibm.ws.asynchbeans.WorkWithExecutionContextImpl.go(WorkWithExecutionContextImpl.java:222)
          at com.ibm.ws.asynchbeans.ABWorkItemImpl.run(ABWorkItemImpl.java:206)
          at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1690)

      [15.10.13 15:41:59:666 CEST] 00000065 NFSFileUtil   I   failed to copy file by retry: 20 from: D:\IBM\IBMConversion\data\temp\target-1ea671d0-5838-44bb-920b-8608614e9b63\result.json to: w:\draft\default_org\draft\298\139\2b9047ef-5c56-4ae4-bc2a-4fb9c23825d5\temp\upload\79c23c58229f6a718215ced51a501c9b\concord\result.json
      [15.10.13 15:41:59:666 CEST] 00000065 NFSFileUtil   I   failed to copy file from: D:\IBM\IBMConversion\data\temp\target-1ea671d0-5838-44bb-920b-8608614e9b63\result.json to folder: w:\draft\default_org\draft\298\139\2b9047ef-5c56-4ae4-bc2a-4fb9c23825d5\temp\upload\79c23c58229f6a718215ced51a501c9b\concord
      [15.10.13 15:41:59:666 CEST] 00000065 ConversionWor I   copy target file from local: D:\IBM\IBMConversion\data\temp\target-1ea671d0-5838-44bb-920b-8608614e9b63 to shared storage: w:\draft\default_org\draft\298\139\2b9047ef-5c56-4ae4-bc2a-4fb9c23825d5\temp\upload\79c23c58229f6a718215ced51a501c9b\concord cost time: 6583 ms
      [15.10.13 15:41:59:697 CEST] 00000065 ConversionWor I   conversion completed, false cost 24585ms, application/vnd.openxmlformats-officedocument.wordprocessingml.document, text/html, w:\draft\default_org\draft\298\139\2b9047ef-5c56-4ae4-bc2a-4fb9c23825d5\temp\upload\79c23c58229f6a718215ced51a501c9b\contentfile.docx
      [15.10.13 15:43:43:843 CEST] 00000070 ConversionWor I   CLFAE1244I: Todo: cancel the conversion job: cba3dd5c-8404-4b43-9e8f-199aa7d31b29
      [15.10.13 15:43:43:843 CEST] 00000070 ConversionRes I   CLFAE1201I: Conversion job is canceled

       

      Updated on 2013-10-15T13:47:11Z at 2013-10-15T13:47:11Z by johnydo
      • johnydo
        johnydo
        19 Posts
        ACCEPTED ANSWER

        Re: IBM Docs 1.0.4

        ‏2013-10-15T14:29:01Z  in response to johnydo

        Hi,

        I think I have found the problem but I dont know how can I solve it. When I click to "View" in the IBM Connections Files application I can see the Docs Viewer in my Browser (See Attachment Unbenannt_01.PNG).

        I see in the SystemOut.log from my ConversionServer the document is prepared to view. My NFS Server is running on Linux with this access:

        /docs_viewer_data

        drwxr-xr-x 2 docs_nfs root 4096 Oct  2 14:39 cache
        drwxr-xr-x 3 docs_nfs root 4096 Oct  2 16:26 conversion
        drwxr-xr-x 2 docs_nfs root 4096 Oct  2 15:13 dataStore
        drwxr-xr-x 5 docs_nfs root 4096 Oct 15 15:41 default_org
        drwxr-xr-x 2 docs_nfs root 4096 Oct  2 14:39 fake_filer
        drwxr-xr-x 5 docs_nfs root 4096 Oct  2 14:42 FileViewer
         

        I can see the conversion server prepare the document and copy it to my NFS Share v:

        D:\IBM\IBMConversion\data\temp\target-f9b24fd8-5f5a-4605-b52c-2937ca8dd2e8\result.json to: v:\default_org\534\734\2b9047ef-5c56-4ae4-bc2a-4fb9c23825d5\media\pictures\result.json

         

        after copy I checked the access to this file and I can see its the wrong user:

        /docs_viewer_data/default_org/534/734/2b9047ef-5c56-4ae4-bc2a-4fb9c23825d5

        drwxr-xr-x 2 root root 4096 Oct 15 16:25 1c1cd8b2cd2d055bc72236014277bdea
        -rw-r--r-- 1 root root  426 Oct 15 16:23 job.lock
        drwxr-xr-x 4 root root 4096 Oct 15 16:23 media
        -rw-r--r-- 1 root root    3 Oct 15 16:23 meta.json
        drwxr-xr-x 3 root root 4096 Oct 15 16:23 temp
         

        is that the problem?

        Attachments

        Updated on 2013-10-15T14:29:50Z at 2013-10-15T14:29:50Z by johnydo
        • ChrisGloe
          ChrisGloe
          60 Posts
          ACCEPTED ANSWER

          Re: IBM Docs 1.0.4

          ‏2013-10-23T20:12:06Z  in response to johnydo

          Hi,

          Yes likely it is an authority problem.  The shares owner and access information needs to be set correctly as documented in the Installation Guide, and all of the servers (Docs, Viewer, and Conversion) need to be using the same userid (UID/GID) to write to and read from the Docs and Viewer shares.  For Docs and Viewer (if running on Linux), the UID that is being used for the WebSphere JVM that the Docs and Viewer applications are running in, will be the UID that will be used to create files and read files from the NFS shares.  For the Conversion node running on Windows, the UID in the AnonymousUID/AnonymousGID registry entries are what is used to read and write from the NFS shares.  It looks like you have a combination of some servers (or perhaps when you created the shares) using whatever UID is associated with user docs_nfs whereas some are using the UID associated with root (0).

          Here is the section of the Installation Guide for creating the shares and the correct UID/GID values:

          http://www-10.lotus.com/ldd/docswiki.nsf/xpDocViewer.xsp?lookupName=Installing+and+deploying+IBM+Docs+1.0.4+documentation#action=openDocument&res_title=Configuring_a_shared_data_folder_id104&content=pdcontent

          • johnydo
            johnydo
            19 Posts
            ACCEPTED ANSWER

            Re: IBM Docs 1.0.4

            ‏2013-10-24T07:51:17Z  in response to ChrisGloe

            Hi Chris,

            I have changed my UID and GID to 0 because my Appservers are run as user root. I can View documents and I can Create new documents. But I get an exeption when I published a new document:

            IBM Docs cannot connect to the file repository. Try again later or contact your system administrator.

             

            [10/24/13 9:46:53:972 CEST] 0000007d LCFilesQCSRep W   [S2S call Response Code]: 302
            [10/24/13 9:46:53:977 CEST] 0000007d LCFilesQCSRep W   [S2S call Response Body]: "" javax.xml.stream.XMLStreamException: An invalid XML character (Unicode: 0x0) was found in the prolog of the document. org.apache.abdera.parser.ParseException: javax.xml.stream.XMLStreamException: An invalid XML character (Unicode: 0x0) was found in the prolog of the document.
            [10/24/13 9:46:53:978 CEST] 0000007d Job           E   /docs_data/job_cache/default_org/job_cache/298/139/2b9047ef-5c56-4ae4-bc2a-4fb9c23825d5/472876fb42634343a7acaed604855a91/error.json
                                             com.ibm.concord.job.exception.JobExecutionException: com.ibm.concord.spi.exception.RepositoryAccessException
                    at com.ibm.concord.job.object.ExportDraftToRepositoryJob.exec(ExportDraftToRepositoryJob.java:152)
                    at com.ibm.concord.job.Job.run(Job.java:207)
                    at com.ibm.ws.asynchbeans.J2EEContext$RunProxy.run(J2EEContext.java:269)
                    at java.security.AccessController.doPrivileged(AccessController.java:252)
                    at javax.security.auth.Subject.doAs(Subject.java:495)
                    at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:132)
                    at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:90)
                    at com.ibm.ws.asynchbeans.J2EEContext$DoAsProxy.run(J2EEContext.java:336)
                    at java.security.AccessController.doPrivileged(AccessController.java:280)
                    at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:804)
                    at com.ibm.ws.asynchbeans.WorkWithExecutionContextImpl.go(WorkWithExecutionContextImpl.java:222)
                    at com.ibm.ws.asynchbeans.ABWorkItemImpl.run(ABWorkItemImpl.java:206)
                    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1690)
            Caused by: com.ibm.concord.spi.exception.RepositoryAccessException
                    at com.ibm.concord.lc3.repository.LCFilesQCSRepository.processError(LCFilesQCSRepository.java:287)
                    at com.ibm.concord.lc3.repository.LCFilesQCSRepository.setContentStream(LCFilesQCSRepository.java:571)
                    at com.ibm.concord.lc3.repository.LCFilesCMISRepository.setContentStream(LCFilesCMISRepository.java:99)
                    at com.ibm.concord.platform.repository.RepositoryServiceUtil.update(RepositoryServiceUtil.java:125)
                    at com.ibm.concord.document.services.DocumentServiceUtil.publishDocument(DocumentServiceUtil.java:214)
                    at com.ibm.concord.document.common.AbstractDocumentService.publish(AbstractDocumentService.java:644)
                    at com.ibm.concord.job.object.ExportDraftToRepositoryJob.exec(ExportDraftToRepositoryJob.java:120)
                    ... 12 more

            • ChrisGloe
              ChrisGloe
              60 Posts
              ACCEPTED ANSWER

              Re: IBM Docs 1.0.4

              ‏2013-10-24T18:47:29Z  in response to johnydo

              Well, that is an error we've never seen.  Basically Connections Files doesn't like something that IBM Docs is sending to it as part of the Publish (trying to set the new Version into Connections Files).  You could check the Connections Files JVM SystemOut.log at the matching timestamp to see if that provides any additional details on the problem and increase the Docs Server logging levels (com.ibm.concord.*) to FINEST to see if that helps provide other clues.  You may need to contact IBM Support for assistance with this one.