90 Minds Community

 View Only

  • 1.  Sage SQL instance issues VERY WEIRD

    Posted 12-31-2020 14:07
    Hi All,    In my career in IT/Sage I seem to be a magnet for weird issues and this one is close to the top of the list.  Have a client on premium 2019.   Thier IT company was looking into putting the server on Azure.   They created a copy of the Sage/SQL server in Azure & did some testing.  (of course ran into some issues.)   They shut down the Azure version (or so it seems).  They use a RDP solution called Parallels.  In the past week they have recreated two user profiles on Parallels (admittedly am not very familiar with it).  Both of these users are having issues in Sage that make it appear that they are connecting to the testing server in Azure.  (FYI,,on the Azure server, I changed the MAS_Reports password )  The the first user with the issue was having problems printing, getting an error regarding a login error.   Now they have a second user that entered batches in SO Invoice entry yesterday.  Now that the profile has been "recreated" (I am not sure what this means). they no longer see the batches.  But they are there when I log into the Parallels server and look   Since basically it is an RDP server and everyone should be using the same client install I am totally baffled. .     This may sound familiar to @Alnoor Cassim.  I am hoping that someone can point me to anything to look at..   I debated on posting this is urgent issues but it is only two users at this point. 

    Thanks     ​​& Happy New Year!!

    ------------------------------
    Bob Osborn
    Consultant
    ACI Consulting
    ------------------------------


  • 2.  RE: Sage SQL instance issues VERY WEIRD

    Posted 12-31-2020 23:21
    Hi Bob - Happy New Year!

    I am thinking you treat this as 2 "normal" Sage issues to troubleshoot for these 2 users.  My gut feel is the Parallels client, before and after the reset of the 2 users, is not the actual cause of the 2 issues. The timing of the shutdown of the Azure instance for sure is noteworthy but probably a red herring as well.

    If you want to make absolutely sure, one way, albeit a lame way, is to shadow the one with printing login issue, open their command prompt and type SET > set.txt (or some equivalent) then review it. There are certain environment variables that would tip you off that the RDP is running on an Azure instance, especially if it's a Windows Virtual Desktop (WVD).

    Once you rule that out and know they are in fact logging into the production Sage/SQL server, for the user that can't see their batches, any chance it was setup as a Private Batch? Also if you were logged in to Sage as ACI where you saw all the batches, try logging in as the Sage user who created the batch to see if its a Role security thing (or maybe they looked in the wrong company code :-)  For the user with the printing issue / login issue, just post a screenshot here and go thru the normal troubleshooting paces. I'm guessing overall these are "par for the course" issues for them.

    ------------------------------
    Alnoor Cassim

    Email: alnoor@asifocus.com
    Ph: 949-689-9887
    Orange County, CA
    ------------------------------



  • 3.  RE: Sage SQL instance issues VERY WEIRD

    Posted 01-04-2021 11:45
    We had a customer's IT persist in trying to get a 3rd party remote-ap connection ("2X") working with Sage 100, but eventually they gave up (err... they were forced by the customer to give up) and went with the M$ option. 
    Our disclaimer was: if it's not supported by Sage, we can't help you get it working.  Period.

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



  • 4.  RE: Sage SQL instance issues VERY WEIRD

    Posted 01-04-2021 12:59

    Hi Kevin,

       Sort of the story with this client.  We were not their original reseller.   I get the impression that the last reseller sort of gave up dealing with their IT (which is a large IT company).     And as a "better" solution to 2X (which has been surprisingly stable) they wanted to move to Azure and use Sage as a remote app..  (LOL)   The president of the IT company emailed my boss to say that we should tell Sage that they should "fix" the issue with Azure compatibly.

     

    Thank you,

     

    Bob Osborn

    ACI Consulting

    p 714.282.0378 ext. 402    f 714.282.0235

     

    Bob@ACIconsulting.com

     

     ACISignature1                  

    MCP_SE_Small.bmp

    This communication, including attachments, is confidential and may contain proprietary information intended only for the proposed recipient. Please notify the sender and delete this message if you believe that you have received this message in error or if you are not the proposed recipient. Unauthorized disclosure, copying, or distribution of the information is strictly prohibited.

     

     

     

     




    Original Message


  • 5.  RE: Sage SQL instance issues VERY WEIRD

    Posted 01-04-2021 13:26
    If they are on a supported platform (meaning Microsoft Remote App, or Citrix), then create a ticket and let the IT people deal with Sage.  Windows Server 2019 DataCenter in on the SPM now (for v2020).

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

    Original Message


Related Content