Sage 100

 View Only
Back to discussions
Expand all | Collapse all

Error when starting Sage v2018 Premium

  • 1.  Error when starting Sage v2018 Premium

    Posted 08-12-2019 11:10
    Hi
    Migrated customer from 2017 Advanced to 2018.7 Premium (didn't want 2019 due to third party enhancement needed).
    Install on a new box.
    When I start Sage I get a White Box with the following (pix 1)
    0345
    Error #10: Illegal pathname specified
    2>

    I close the white box, try to start Sage again and get (pix 2)
    Sage 100 is not set up properly
    Please run Workstation Setup to configure this workstation

    I answer OK and launch Sage a third time and it's the charm - it starts as designed!
    If I close Sage and start it back up with a short amount of time, it starts as designed.  If i let it sit for awhile or close out of the server and log back in, I get the sequence of events above.
    I uninstalled and installed workstation setup​.  Still get the same messages except I now have to 'run  as Administrator'
    Sage and Sql are on the same server and currently Local System Account is running the Sage service and NT Service\MSSQL$SAGESQL2018 is running the SQL Server Instance.  
    I am a local administrator

    I haven't yet tried installing to a workstation and seeing if others get the same problems.
    Any ideas on how to resolve?

    Nancy

    ------------------------------
    Nancy Hanson
    Blytheco LLC
    Eagan MN
    ------------------------------


  • 2.  RE: Error when starting Sage v2018 Premium

    Posted 08-12-2019 11:15
    Did you by any chance use something like "localhost" when setting up the SQL connection from Sage?  That won't work.
    We usually set up the Sage service to run using a domain account which is also a local administrator.

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------



  • 3.  RE: Error when starting Sage v2018 Premium

    Posted 08-12-2019 11:19
    I remember seeing that option "localhost\instance name" but I believe I changed it to 'server\instance'.  Is there a way to validate what I did?

    I'll have IT try changing the service account.

    ------------------------------
    Nancy Hanson
    Blytheco LLC
    Eagan MN
    ------------------------------

    Original Message


  • 4.  RE: Error when starting Sage v2018 Premium

    Posted 08-12-2019 11:24
    There is a Sage program on the server for managing the SQL server connection.  Look there for the server path.

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------

    Original Message


  • 5.  RE: Error when starting Sage v2018 Premium

    Posted 08-12-2019 13:09
    I looked in the Sage Sql Settings Utility and the Database Server says the correct server name and instance.
    Is that what you were referring to?

    ------------------------------
    Nancy Hanson
    Blytheco LLC
    Eagan MN
    ------------------------------

    Original Message


  • 6.  RE: Error when starting Sage v2018 Premium

    Posted 08-12-2019 14:45
    Yes, that is what I meant.
    Did you try to run the workstation As Admin?

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------

    Original Message


  • 7.  RE: Error when starting Sage v2018 Premium

    Posted 08-12-2019 15:42
    Hi
    I did run as Admin.  No change.  
    I log into the server, launch Sage 3x to get it to launch.  I can close Sage but stay logged into server and Sage will open correctly after those first 3x.  
    Once I log off server and log back on, I have to launch Sage 3x to get it to open.
    UAC is turned off.  I ran wksetup as Admin.  I've uninstalled/installed wksetup.  
    Frustrating!
    N

    ------------------------------
    Nancy Hanson
    Blytheco LLC
    Eagan MN
    ------------------------------

    Original Message


  • 8.  RE: Error when starting Sage v2018 Premium

    Posted 08-12-2019 16:18
    Does it work first time if you use MAS90 mode? 
    If it does, I'd suspect something wrong with SOTA.INI

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------

    Original Message


  • 9.  RE: Error when starting Sage v2018 Premium

    Posted 08-12-2019 16:27
    @Nancy Hanson How long is the path to Sage? In the pvxplus manual  ​Illegal Pathname Specified usually means the filename is too long. 

    *******
    Illegal pathname specified

    Invalid filename on a SAVE, OPEN, LOAD, RUN or CALL directive.

    Possible Reasons:

    • Filename too long, contains invalid characters or has invalid syntax. A null string is an invalid pathname.
    • In [TCP] – an invalid IP or DNS address. 

    ------------------------------
    Michelle Forsey
    Eide Bailly, Inc.
    801-456-5470
    ------------------------------

    Original Message


  • 10.  RE: Error when starting Sage v2018 Premium

    Posted 08-12-2019 17:00
    Or maybe your path needs to be enclosed in quotes?

    ------------------------------
    - Brett
    ------------------------------

    Original Message


  • 11.  RE: Error when starting Sage v2018 Premium

    Posted 08-12-2019 17:06
      |   view attached
    Here is a copy of my SOTA.ini from my 2018 Premium install if it helps?

    ------------------------------
    Michelle Forsey
    Eide Bailly, Inc.
    801-456-5470
    ------------------------------

    Attachment(s)

    ini
    sota.ini   1 KB 1 version
    Original Message


  • 12.  RE: Error when starting Sage v2018 Premium

    Posted 08-13-2019 10:52
    Michelle,
    The server name has an underscore in it. Can that be a problem?
    Sage_doclink. 
    IT is willing to rename after I uninstall.  Thoughts?

    ------------------------------
    Nancy Hanson
    Blytheco LLC
    Eagan MN
    ------------------------------

    Original Message


  • 13.  RE: Error when starting Sage v2018 Premium

    Posted 08-13-2019 11:06
    That is likely:
    https://blogs.msdn.microsoft.com/dstfs/2009/06/16/problems-configuring-tfs-2010-when-resource-has-underscore-_-in-name/ 
    "...The issue here is that underscore is not a valid character for FQDN's and as such cause issues with...".


    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------

    Original Message


  • 14.  RE: Error when starting Sage v2018 Premium

    Posted 08-13-2019 20:06

    HERE is where I intended to say "Nice Find @Kevin Moyes!!" 

    :)​



    ------------------------------
    Michelle Forsey
    Eide Bailly, Inc.
    801-456-5470
    ------------------------------

    Original Message


  • 15.  RE: Error when starting Sage v2018 Premium

    Posted 08-13-2019 20:14
    I was finally able to sit down and read all the replies and I agree 'Nice Find' @Kevin Moyes.  IT is skeptical that an _ in the server name could be a problem but he is willing to play along with me! 
    I did try the 'run as mas90', didn't change anything.  Going to have the server renamed tomorrow.
    Now, next question - how do I prepare this rename of server?  Do I backup the Sql DB's and the Sage Program files and do an uninstall?  Rename the server, then install again?  At what point do I restore the DB's to Sql?  Does IT need to make a new instance for me to restore to and point to during install?
    Thanks
    Nancy
    ​

    ------------------------------
    Nancy Hanson
    Blytheco LLC
    Eagan MN
    ------------------------------

    Original Message


  • 16.  RE: Error when starting Sage v2018 Premium

    Posted 08-13-2019 20:30
    I would treat it like you were moving servers. Just so it registers the dll's again if needed. Check out KB 85470 It's like stereo instructions, but follow-able.

    For SURE full backup the DB's (Including MAS_Reports and MAS_Users) 

    When you reinstall Sage, point it to the same instance, and it should recognize the DB's are already there. If you get a popup saying it detected a MAS_System you should be able to merge them (No biggie unless 3rd party is installed??).  Update/test the SQL utility and the data. 
    There is another KB I am looking for about moving Servers.. I'll post it when I find it. :) 
    Good Luck!!!

    ------------------------------
    Michelle Forsey
    Eide Bailly, Inc.
    801-456-5470
    ------------------------------

    Original Message


  • 17.  RE: Error when starting Sage v2018 Premium

    Posted 08-13-2019 20:38
    @Steve Iwanowski talked about something like this in his SQL class... but this is the other article I was thinking of... I think.

    ​https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=54724&sliceId=1&isLoadPublishedVer=&docType=kc&docTypeID=DT_Article&stateId=14302&cmd=displayKC&dialogID=650339&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl&openedFromSearchResults=true 


    Cause

    When you restore a Microsoft SQL Server database on a different machine, you cannot access the database until you fix the permissions. The problem is that the user in the database is an "orphan".



    Resolution

    Run this script in SQL Query against the database with the issue.

     

     

    EXEC sp_change_users_login 'Auto_Fix', 'MAS_Reports'

    GO

    EXEC sp_dropuser 'MAS_Reports'

    GO

    EXEC sp_grantdbaccess 'MAS_Reports'

    GO

    EXEC sp_addrolemember 'db_datareader', 'MAS_Reports'



    ------------------------------
    Michelle Forsey
    Eide Bailly, Inc.
    801-456-5470
    ------------------------------

    Original Message


  • 18.  RE: Error when starting Sage v2018 Premium

    Posted 08-14-2019 09:33
    I wonder if reinstalling is needed though.  Rename the server, use the Sage SQL settings utility to update the path to SQL, update any Sage paths / shares (Paperless...) and see if it works.  Since it will be the same SQL instance (on a renamed server) there would be no SQL permission issues.

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------

    Original Message


  • 19.  RE: Error when starting Sage v2018 Premium

    Posted 08-14-2019 10:36
    That's a good point. 
    We had an IT company move a Sage Premium back in the 4.5 days and ran into a bunch of naming and permissions issues, I may have PTSD from that. But I be you're right.

    ------------------------------
    Michelle Forsey
    Eide Bailly, Inc.
    801-456-5470
    ------------------------------

    Original Message


  • 20.  RE: Error when starting Sage v2018 Premium

    Posted 08-14-2019 09:21
    The safest thing would be to wipe everything out and redo the migration from v2017. Of course, this assumes they didn't do anything Live in v2018.

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------

    Original Message


  • 21.  RE: Error when starting Sage v2018 Premium

    Posted 08-15-2019 10:06
    Any update @Nancy Hanson?​

    ------------------------------
    Robert Wood
    Consultant
    90 Minds
    Ocala FL
    352-615-5898
    ------------------------------

    Original Message


  • 22.  RE: Error when starting Sage v2018 Premium

    Posted 08-15-2019 10:21
    ARGHHHHHHHH!  
    I tried the install last night.  IT renamed the server from Sage_DocLink to SageDLink (shorten and removal of _).  The instance name changed to reflect and all databases were showing.
    I installed v2018, pointed to the server/instance (had to browse for it), and while I didn't do a conversion (yet), I set the service, and tried logging in.  It is giving me the same issues (error 10 illegal pathname specified).  I did uninstall again and installed pointing to the new instance IT created (just in case this happened) and I played with it just briefly and need to get back to it today.
    I'm not sure why IT is using Sql 2014 when he also have 2017 installed but that's beside the point.  However, I have to go back and look but I believe I was told by this forum not to use the server/instance of (localhost)/instance - correct? I didn't use it but was wondering if I should. 
    I'm so frustrated, I can hardly think straight anymore.  They have 23 companies of which 16 have payroll so would rather not start over with a fresh VM but may need to.
    On another note - he created my user name with $ at the end, that doesn't affect any of this does it?  Not sure why he's so stuck on _ and other characters.  Now I'm just venting!
    N

    ------------------------------
    Nancy Hanson
    Blytheco LLC
    Eagan MN
    ------------------------------

    Original Message


  • 23.  RE: Error when starting Sage v2018 Premium

    Posted 08-15-2019 10:26
    Venting is good - that's what we're here for!!

    ------------------------------
    Therese Logeais, Technology Integrators
    ------------------------------

    Original Message


  • 24.  RE: Error when starting Sage v2018 Premium

    Posted 08-15-2019 11:11
    Never use "localhost" when referring to the SQL instance because workstations would never be able to find the SQL server (needed for printing).  If the machine name doesn't work, the server's IP address should be fine.
    As long as the SQL version is on the SPM, it should work.
    Don't install too deep into a folder structure.  Long paths can cause an Error 10.
    I've also seen strange things with multiple partitions.  The default SQL data directory was set to a small C-drive, instead of the larger D-drive, and Sage couldn't create databases...

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------

    Original Message


  • 25.  RE: Error when starting Sage v2018 Premium

    Posted 08-15-2019 12:09
    In addition to what Kevin mentioned about not using local host, it is possible that the SQL name is not the same as the server name.  They are typically the same but it can be changed and there can be more than one SQL instance configured on the same SQL server.  So verify the SQL server name. ​

    ------------------------------
    Doug Higgs
    Assistant Technical Support / Building Maintenance Specialist
    Midwest Commerce Solutions, Inc
    ------------------------------

    Original Message


  • 26.  RE: Error when starting Sage v2018 Premium

    Posted 08-15-2019 12:13
    Thanks for the tips.
    I'm going to see if he'll spin me up a new VM and start completely over.  Hopefully 2nd time around is better with a clean install, proper naming, etc.
    N

    ------------------------------
    Nancy Hanson
    Blytheco LLC
    Eagan MN
    ------------------------------

    Original Message


  • 27.  RE: Error when starting Sage v2018 Premium

    Posted 08-15-2019 12:16
    Check Wayne's list (posted recently) on preparations.  UAC off during the software install, running autorun As Admin... use the "sa" login during the install, not Windows authentication for SQL.

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------

    Original Message


  • 28.  RE: Error when starting Sage v2018 Premium

    Posted 08-16-2019 00:19
    I'm going to go ahead and move this over to Sage 100 since the urgency has dropped off. Please keep updating the thread.

    ------------------------------
    Robert Wood
    Consultant
    90 Minds
    Ocala FL
    352-615-5898
    ------------------------------

    Original Message


  • 29.  RE: Error when starting Sage v2018 Premium

    Posted 09-25-2019 21:15
    Hey Everyone
    Finally got this install resolved.  After installing 'every which way but loose!'  I asked IT to wipe the server clean. He complied and I installed fresh and all went well.  Then....IT tells me they found remnants of a poor/incomplete/corrupt operating system install.  Not sure how he could see that, will need to ask, so I can tuck that one away for future.
    Well that's about 20 hours I'll never get back.  I was starting to question my own abilities after having so many problems with this one install.
    Thanks for the suggestions to help resolve this issue.
    Nancy

    ------------------------------
    Nancy Hanson
    Blytheco LLC
    Eagan MN
    ------------------------------

    Original Message


Related Content