Topic
  • 9 replies
  • Latest Post - ‏2014-06-06T08:00:47Z by Jens.Engelke
SystemAdmin
SystemAdmin
7615 Posts

Pinned topic [8.0.1] Problem with File Upload from old coaches

‏2013-02-27T08:49:30Z |
Hi,
Do you have any problems with File Upload object (old coaches) after migration to 8.0.1?
I have "Error retrieving document list" and no idea how to fix it.
Everything works correctly after instalation on PS 8.0.0.

best regars
Adam
  • 2W10_GÖKHAN_ORHON
    2W10_GÖKHAN_ORHON
    6 Posts

    Re: [8.0.1] Problem with File Upload from old coaches

    ‏2014-06-05T08:40:42Z  

    hi,

     

    We migrate 7.5 to 8.5. We have same problem. How fix?

     

    Thanks,

  • Jens.Engelke
    Jens.Engelke
    56 Posts

    Re: [8.0.1] Problem with File Upload from old coaches

    ‏2014-06-05T14:22:31Z  

    First thing to check is SystemOut.log.

    In addition you may want to run a tool like www.fiddler2.com to capture network traffic and see the actual request/response that fails

  • Dae Young
    Dae Young
    430 Posts

    Re: [8.0.1] Problem with File Upload from old coaches

    ‏2014-06-05T15:14:10Z  

    hi,

     

    We migrate 7.5 to 8.5. We have same problem. How fix?

     

    Thanks,

    Good afternoon,

    I could be wrong on this, but before bpm v8.0, you could upload a file through a heritage coach and file would be stored in one of lombardi tables (lws_*). I do not know the exact table name. However beginning of v8.0, that functionality is no longer available. For v8.0.x.x, you have to use third party plugin to support file upload or you have to write up custom servlet class and deploy it to an application server to handle uploading process.

    However, if you upgraded to v8.5, I believe that you can easily upload a file through product itself. I quote Neil's comment "Another solution is to use the ECM support built into the product. You can leverage a free ECM product and use the out-of-the-box file uploader Coach View ..." from below thread.

    https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014914657&ps=25

    Have a blessed day.

  • AndrewPaier
    AndrewPaier
    743 Posts

    Re: [8.0.1] Problem with File Upload from old coaches

    ‏2014-06-06T02:56:45Z  

    hi,

     

    We migrate 7.5 to 8.5. We have same problem. How fix?

     

    Thanks,

    There is a step in the upgrade that is intended to move all the items in the DB repository into the new ECM repository.  Are you sure you ran that step?

  • 2W10_GÖKHAN_ORHON
    2W10_GÖKHAN_ORHON
    6 Posts

    Re: [8.0.1] Problem with File Upload from old coaches

    ‏2014-06-06T05:36:35Z  

    There is a step in the upgrade that is intended to move all the items in the DB repository into the new ECM repository.  Are you sure you ran that step?

    Yes. Migrated document store.

  • 2W10_GÖKHAN_ORHON
    2W10_GÖKHAN_ORHON
    6 Posts

    Re: [8.0.1] Problem with File Upload from old coaches

    ‏2014-06-06T05:40:04Z  

    First thing to check is SystemOut.log.

    In addition you may want to run a tool like www.fiddler2.com to capture network traffic and see the actual request/response that fails

    Our problem is run process.

     

     

    Attachments

    Updated on 2014-06-06T06:01:20Z at 2014-06-06T06:01:20Z by 2W10_GÖKHAN_ORHON
  • Jens.Engelke
    Jens.Engelke
    56 Posts

    Re: [8.0.1] Problem with File Upload from old coaches

    ‏2014-06-06T07:26:34Z  

    Our problem is run process.

     

     

    I understand the symptom you are observing. What I am telling you is that - in order to resolve your issue - you need to determine its root cause.

    This little pop-up dialog is a tiny fraction of error information that system gives you. You have to look at all the other information, too.

    Without looking into SystemOut.log you won't be able to understand what's happening.

  • 2W10_GÖKHAN_ORHON
    2W10_GÖKHAN_ORHON
    6 Posts

    Re: [8.0.1] Problem with File Upload from old coaches

    ‏2014-06-06T07:37:43Z  

    I understand the symptom you are observing. What I am telling you is that - in order to resolve your issue - you need to determine its root cause.

    This little pop-up dialog is a tiny fraction of error information that system gives you. You have to look at all the other information, too.

    Without looking into SystemOut.log you won't be able to understand what's happening.

    here, thanks.

     

    [6/6/14 10:35:39:157 EEST] 00000118 wle_servlet   I   CWLLG0006I: Initializing a new session.
    [6/6/14 10:35:39:282 EEST] 00000118 wle_security  I   CWLLG1088I: Initializing session is done for user ak008259
    [6/6/14 10:35:39:672 EEST] 00000118 WSChannelFram A   CHFW0019I: The Transport Channel Service has started chain HttpOutboundChain:st-bpmps2:80.
    [6/6/14 10:35:39:765 EEST] 00000118 wle_javascrip I   TEST TEST TESTundefined
    [6/6/14 10:35:39:765 EEST] 00000118 wle_javascrip I   TEST TEST TEST0
     

     

     

  • Jens.Engelke
    Jens.Engelke
    56 Posts

    Re: [8.0.1] Problem with File Upload from old coaches

    ‏2014-06-06T08:00:47Z  

    here, thanks.

     

    [6/6/14 10:35:39:157 EEST] 00000118 wle_servlet   I   CWLLG0006I: Initializing a new session.
    [6/6/14 10:35:39:282 EEST] 00000118 wle_security  I   CWLLG1088I: Initializing session is done for user ak008259
    [6/6/14 10:35:39:672 EEST] 00000118 WSChannelFram A   CHFW0019I: The Transport Channel Service has started chain HttpOutboundChain:st-bpmps2:80.
    [6/6/14 10:35:39:765 EEST] 00000118 wle_javascrip I   TEST TEST TESTundefined
    [6/6/14 10:35:39:765 EEST] 00000118 wle_javascrip I   TEST TEST TEST0
     

     

     

    [6/6/14 10:35:39:765 EEST] 00000118 wle_javascrip I   TEST TEST TESTundefined
    [6/6/14 10:35:39:765 EEST] 00000118 wle_javascrip I   TEST TEST TEST0

    is likely coming from your application.

    There is nothing related to an internal error. This may well mean that the call from the browser does not even reach the server. You can enable your browser's network traffic monitor (F12 in most browsers) or use a tool like www.fiddler2.com to monitor network traffic. 
    You will see several HTTP requests going back and forth between browser and server. The good ones are returned with HTTP 200 OK. All response status codes other than 200 OK are the ones to look at.