• FEATURES
  • PRICING
  • MARKETPLACE
  • CASE STUDIES
  • BLOG
  • Shipment error: No Storage Type specified for In Transit Containers

    Posting on behalf of @Shannon_Dalton,

    We have a fresh instance of OS-v1.1_RC3. In the shipping module, I received the error message “No Storage Type specified for In Transit Containers”.

    I have created storage containers for both In Transit and Sponsor locations to accept all storage types.

    Is there a step that I am missing to be able to ship specimens?

    Hi @Shannon_Dalton,

    OpenSpecimen automatically creates a In Transit site, a storage type with name " Shipment Container" and a storage container with name “Shipment Container” at the time of deployment.

    You can check them by searching from Administration->Site->Edit, Administration->Storage Type->Edit and Administration->Storage Container->Edit

    Could you please make sure that default Site/Storage type/Storage Container are present in the system and you haven’t made any changes in these in-built storage type and container ?

    ~Nitesh

    Hi Nitesh,

    I went to Administration → Site → Edit and selected In Transit, but received a system error. Attached is the server log. The java error is towards the bottom.

    Thanks,
    Shannon server[1].log (450.8 KB)

    Hi @Shannon_Dalton,

    It seems like the address id for the default site is not inserted while deployment. Please run the below SQL, this will resolve the issue:

    update catissue_site set address_id = 1 where name like ‘In Transit’

    We have noted this issue, will fix and include in next build.

    ~Nitesh

    Hi @nitesh_marwaha

    We applied the fix above, however still experiencing the same issues with “No Storage Type specified for In Transit Containers.” After applying the fix, I noticed that only a few of the available containers are listed in the pull down menus while logging in new specimen collections.

    Thanks,
    Shannon

    serverError.log (413.7 KB)

    Here is the server log.

    Thanks,
    Shannon

    Hi @Shannon_Dalton,

    In the attached server log, I didn’t see any shipment related error. Everything seems to be fine in the server log.

    Will have to check on your server.

    ~Nitesh

    Hi @nitesh_marwaha,

    What does the CommonAddEditAction failure signify? See the server log message below:

    2015-04-22 11:07:44,979 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/openspecimen]] (http-openspecimen.winship.emory.edu%2F170.140.137.147-443-6) Stinger-Filter: using default parameter rule for parameter sendTimeHour

    2015-04-22 11:07:45,289 INFO [STDOUT] (http-openspecimen.winship.emory.edu%2F170.140.137.147-443-6) ERROR 11:07:45,289 (CommonAddEditAction) - Common Add/Edit failed…No Storage Type Specified for In Transit Containers

    2015-04-22 11:08:41,523 INFO [STDOUT] (http-openspecimen.winship.emory.edu%2F170.140.137.147-443-4) ERROR 11:08:41,523 (DataSourceConnectionManager) - dao.method.without.implementation

    I have created storage containers for In Transit site to include all classes of specimens and specimen types. In the storage type form, there is no place to designate site. Is there another item that needs to be created first to fire off the branching logic for In Transit containers?

    Thanks,
    Shannon

    OS Storage Container In Transit.pptx (257.4 KB)

    Hi @Shannon_Dalton,

    The error states that storage type is not specified for In Transit Contianer. This storage type and container created automatically at the time of deployment. The screenshots you attached is fine. Please try to open the “In Transit Container” from Adminnistration->StorageContainer->Edit and check whether it has Storage type assigned or not.

    The other thing you can do, Create a new site, Storage type, Storage container associating to the newly create storage type and site.

    For the system configuration you can refer the videos: https://catissueplus.atlassian.net/wiki/x/BwAv

    ~Nitesh