Sage 100

 View Only

  • 1.  Logicity error after 'server image' migration

    Posted 04-29-2025 13:06

    A client of ours is using Logicity 1.9.3.0 with Sage 100.  We performed a server migration (via 'server image') but now Logicity is yielding the below 'Failed to open the connection' error, although everything else works fine.  Hoping someone has an idea or two as to what could be causing this.  I'm still thinking permissions even though no luck using administrator.

     



    ------------------------------
    Brett Zimmerman
    Net at Work
    Greater Boston Area
    ------------------------------


  • 2.  RE: Logicity error after 'server image' migration

    Posted 04-29-2025 13:09

    Can you run / refresh the report manually using CR designer?  Maybe there is an issue with the data source (server name change / IP address change / broken DSN...).



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



  • 3.  RE: Logicity error after 'server image' migration

    Posted 04-29-2025 19:57

    What happens if you go through the edit actions? I think it's going to take you through another few configuration screens and maybe there's something in there?



    ------------------------------
    Wayne Schulz
    wayne@s-consult.com
    Schulz Consulting
    (860) 516-8990
    CT
    ------------------------------



  • 4.  RE: Logicity error after 'server image' migration

    Posted 04-30-2025 01:59

    If Kevin's idea to check the report and data source doesn't fix it, I would use the Edit button to record the existing settings and then recreate a new RRD file. Also, note that LogiCity is no longer being distributed.and is at "End of LIfe".



    ------------------------------
    Dan Burleson
    Software Consultant
    Connex Software
    Corvallis OR
    541-829-1054
    ------------------------------



  • 5.  RE: Logicity error after 'server image' migration

    Posted 04-30-2025 10:47

    Thanks for the suggestions!  So it seems we were able to temporarily fix it by renaming/deleting temp file(s) in regedit, specific to the referenced filename in the error.  So still working on a real fix.

    We went through everything but recreating each job. That would take a very long time to do with all of the reports they are using and I don't know if we are willing to do it.  We are going to try recreating one.
     
    It seems like Logicity has its own "verify database" which is hanging. We can open the stalled temp file and fix it in Crystal, but it looks like every time we refresh the report we have to repeat that step. There are 100's of reports involved, and the ones that are working will not e-mail.



    ------------------------------
    Brett Zimmerman
    Net at Work
    Greater Boston Area
    ------------------------------

    Original Message


Related Content