Sage 100

 View Only

  • 1.  StarShip issue with v2019 Premium Product Update 2 Errors

    Posted 07-30-2021 21:52
    Any StarShip expert who can help our technician with this install / setup would be extremely helpful.  Or at least pointer on what may be going on.  V-Tech was not able to figure it out.  Client just moved from Sage 100 2019 Standard Product Update 2 to Sage 100 2019 Premium Product Update 2


    When we launch the starship client, we navigate to Setup -> Source Interface -> Sage 100 4.1 – 2020 -> My companies -> Add Company.

    When we click on add company and select one specific company, it runs constantly and does not finish. Their other companies were added fine here. Once we check the logs, we discover something interesting, quoted below.

    The other companies log files did not have this chunk of issues in them. We have tested IOTest with this company, and it works fine.

    To troubleshoot this, I created a TST company and copied the problem company data into it in Sage 100. I was then able to add the TST company to the Sage 100 4.1 – 2020 Source Interface in Starship successfully.

    After this, to further test, I logged into Sage 100 and into the TST company, did a test ship in Sales Order, and clicked on the Starship button, and got the error below. In Starship, there is not a Sage 100 2019 Starship Link as a Source.

    Please let me know if further clarification is needed.

     ERROR RECEIVED WHEN CLICKING STARSHIP BUTTON IN SAGE 100 IN WORKING COMPANY.

    Starship Error re:

     

    STARSHIP ERROR LOG FOR PROBLEM COMPANY:

    "2021.07.30 09:38:08.579 *** INFO ***     (Administrator, LMS-ERP02) pscript.newobject: enter BM_BillOption_SVC

    2021.07.30 09:38:08.582 *** INFO ***     (Administrator, LMS-ERP02) Error in BuildValuesList : [BM_BillOption_SVC] [LUM] [Module J/C is not on file.] <NewObject Error: 90>

    2021.07.30 09:38:08.582 *** INFO ***     (Administrator, LMS-ERP02) RetrieveFieldList.BuildValuesList for BILLOPTION2

    2021.07.30 09:38:08.584 *** INFO ***     (Administrator, LMS-ERP02) newobject BM_BillOption_SVC

    2021.07.30 09:38:08.584 *** INFO ***     (Administrator, LMS-ERP02) pscript.newobject: enter BM_BillOption_SVC

    2021.07.30 09:38:08.588 *** INFO ***     (Administrator, LMS-ERP02) Error in BuildValuesList : [BM_BillOption_SVC] [LUM] [Module J/C is not on file.] <NewObject Error: 90>

    2021.07.30 09:38:08.588 *** INFO ***     (Administrator, LMS-ERP02) RetrieveFieldList.BuildValuesList for BILLOPTION3

    2021.07.30 09:38:08.590 *** INFO ***     (Administrator, LMS-ERP02) newobject BM_BillOption_SVC

    2021.07.30 09:38:08.590 *** INFO ***     (Administrator, LMS-ERP02) pscript.newobject: enter BM_BillOption_SVC

    2021.07.30 09:38:08.594 *** INFO ***     (Administrator, LMS-ERP02) Error in BuildValuesList : [BM_BillOption_SVC] [LUM] [Module J/C is not on file.] <NewObject Error: 90>

    2021.07.30 09:38:08.594 *** INFO ***     (Administrator, LMS-ERP02) RetrieveFieldList.BuildValuesList for BILLOPTION4

    2021.07.30 09:38:08.596 *** INFO ***     (Administrator, LMS-ERP02) newobject BM_BillOption_SVC

    2021.07.30 09:38:08.596 *** INFO ***     (Administrator, LMS-ERP02) pscript.newobject: enter BM_BillOption_SVC

    2021.07.30 09:38:08.599 *** INFO ***     (Administrator, LMS-ERP02) Error in BuildValuesList : [BM_BillOption_SVC] [LUM] [Module J/C is not on file.] <NewObject Error: 90>

    2021.07.30 09:38:08.599 *** INFO ***     (Administrator, LMS-ERP02) RetrieveFieldList.BuildValuesList for BILLOPTION5

    2021.07.30 09:38:08.601 *** INFO ***     (Administrator, LMS-ERP02) newobject BM_BillOption_SVC

    2021.07.30 09:38:08.601 *** INFO ***     (Administrator, LMS-ERP02) pscript.newobject: enter BM_BillOption_SVC

    2021.07.30 09:38:08.604 *** INFO ***     (Administrator, LMS-ERP02) Error in BuildValuesList : [BM_BillOption_SVC] [LUM] [Module J/C is not on file.] <NewObject Error: 90>

    2021.07.30 09:38:08.605 *** INFO ***     (Administrator, LMS-ERP02) RetrieveFieldList.BuildValuesList for BILLOPTION6

    2021.07.30 09:38:08.606 *** INFO ***     (Administrator, LMS-ERP02) newobject BM_BillOption_SVC

    2021.07.30 09:38:08.607 *** INFO ***     (Administrator, LMS-ERP02) pscript.newobject: enter BM_BillOption_SVC

    2021.07.30 09:38:08.610 *** INFO ***     (Administrator, LMS-ERP02) Error in BuildValuesList : [BM_BillOption_SVC] [LUM] [Module J/C is not on file.] <NewObject Error: 90>

    2021.07.30 09:38:08.610 *** INFO ***     (Administrator, LMS-ERP02) RetrieveFieldList.BuildValuesList for BILLOPTION7

    2021.07.30 09:38:08.612 *** INFO ***     (Administrator, LMS-ERP02) newobject BM_BillOption_SVC

    2021.07.30 09:38:08.612 *** INFO ***     (Administrator, LMS-ERP02) pscript.newobject: enter BM_BillOption_SVC

    2021.07.30 09:38:08.615 *** INFO ***     (Administrator, LMS-ERP02) Error in BuildValuesList : [BM_BillOption_SVC] [LUM] [Module J/C is not on file.] <NewObject Error: 90>

    2021.07.30 09:38:08.615 *** INFO ***     (Administrator, LMS-ERP02) RetrieveFieldList.BuildValuesList for BILLOPTION8

    2021.07.30 09:38:08.617 *** INFO ***     (Administrator, LMS-ERP02) newobject BM_BillOption_SVC

    2021.07.30 09:38:08.617 *** INFO ***     (Administrator, LMS-ERP02) pscript.newobject: enter BM_BillOption_SVC

    2021.07.30 09:38:08.620 *** INFO ***     (Administrator, LMS-ERP02) Error in BuildValuesList : [BM_BillOption_SVC] [LUM] [Module J/C is not on file.] <NewObject Error: 90>

    2021.07.30 09:38:08.620 *** INFO ***     (Administrator, LMS-ERP02) RetrieveFieldList.BuildValuesList for BILLOPTION9

    2021.07.30 09:38:08.622 *** INFO ***     (Administrator, LMS-ERP02) newobject BM_BillOption_SVC

    2021.07.30 09:38:08.622 *** INFO ***     (Administrator, LMS-ERP02) pscript.newobject: enter BM_BillOption_SVC

    2021.07.30 09:38:08.625 *** INFO ***     (Administrator, LMS-ERP02) Error in BuildValuesList : [BM_BillOption_SVC] [LUM] [Module J/C is not on file.] <NewObject Error: 90>

    2021.07.30 09:38:08.625 *** INFO ***     (Administrator, LMS-ERP02) RetrieveFieldList.BuildValuesList for TAXCLASS"

     

     

     



    ------------------------------
    [Sue] [Dunn]
    [Client Advisor]
    [MicroAccouting Solution]
    [Milwaukee] [WI]
    [414.587.4641]
    ------------------------------


  • 2.  RE: StarShip issue with v2019 Premium Product Update 2 Errors

    Posted 07-30-2021 22:43
    We're the StarShip Link programs installed with the Sage 100 programs, or are you using the BOI interface?

    ------------------------------
    Doug Higgs
    Midwest Commerce Solutions, Inc
    (312) 315-0960
    Chauffeur, Chef, and Personal Assistant to Sprinkles
    ------------------------------



  • 3.  RE: StarShip issue with v2019 Premium Product Update 2 Errors

    Posted 07-31-2021 09:13
    It's the Link Programs

    ------------------------------
    [Sue] [Dunn]
    [Client Advisor]
    [MicroAccouting Solution]
    [Milwaukee] [WI]
    [414.587.4641]
    ------------------------------

    Original Message


  • 4.  RE: StarShip issue with v2019 Premium Product Update 2 Errors

    Posted 07-31-2021 16:14
    Have you tried running MAS_switch.exe in D:\Program Files (x86)\V-Technologies\StarShip\Client?  Also, verify that the correct version of the StarShip link program is installed with the Sage 100 v2019 Premium installation and that V-Techologies has enabled StarShip link and not the BOI interface.  If you have already verified these, then you may ask V-Technologies to disable the link and enable the BOI interface to see if you get the same behavior.

    ------------------------------
    Doug Higgs
    Midwest Commerce Solutions, Inc
    (312) 315-0960
    Chauffeur, Chef, and Personal Assistant to Sprinkles
    ------------------------------

    Original Message


  • 5.  RE: StarShip issue with v2019 Premium Product Update 2 Errors

    Posted 08-01-2021 11:27
    Thanks Doug,  I've given the suggestion to our Tech Consultant who is managing the install.  He will most likely need to have V-Technologies assist tomorrow.

    ------------------------------
    [Sue] [Dunn]
    [Client Advisor]
    [MicroAccouting Solution]
    [Milwaukee] [WI]
    [414.587.4641]
    ------------------------------

    Original Message


  • 6.  RE: StarShip issue with v2019 Premium Product Update 2 Errors

    Posted 08-03-2021 20:41
    Wanted to post an update to this.  We got it resolved.  Turned out that there had been some data issues during the Migration and apparently this was not an issue in ProvideX but once the data was moved to SQL Starship had issue with one of the records.  The file that housed the record was GL_COMPANYACTIVEBATCH.  Once that record was removed Starship worked just fine.  

    This ticket can be moved from Urgent support. Thanks for the prior input.

    ------------------------------
    [Sue] [Dunn]
    [Client Advisor]
    [MicroAccouting Solution]
    [Milwaukee] [WI]
    [414.587.4641]
    ------------------------------

    Original Message


Related Content