Not able to upload Sage 50 CA-premium on Cloud after updating to 2020.2 . Struggling for last 5 days. Will any one please advise about it.

SOLVED

After updating Sage 50 CA 2020.2, I can not upload the company for remote excess. I can not upload the company for remote excess. I have tried all the procedures given on your sites but without any success. I (sysadmin) and the users can not work without remote excess and thus the backlog is increasing.

Parents
  • 0
    SUGGESTED

    Hi

    Thanks for reaching out. We've got a conversation with troubleshooting resources on this post here. I'd suggest reviewing the suggestions and listing what you've tried.

    Warm Regards, 
    Erzsi

  • 0 in reply to Erzsi_I

    Hi Erzsi, Thank you for your guidance, Have been done, but to no avail.  Sage dial is not as cooperative as they are supposed to be.......  Please note that I can open sage drive to download old companies, but can not Upload/Share  new company with updated version 2020.2 on Remote Data Access.

    Will appreciate your referring my case to some technical department who can solve this issue.

    Best Regards/AHK

  • 0 in reply to AHK

    Hi

    Is this concerning your account GIT with account ending #40xxxxxx475? I see Sage 50 CA on there. I've forwarded your comment to the Sage 50 support team to see if they can have someone reach out internationally at the phone number listed on your account ending 009xx-xxxxx625. Will update you with any news. 

    Warm Regards, 
    Erzsi

  • 0 in reply to Erzsi_I

    Hi Erzsi,

    Thank you and Yes Azzano called me but due to time difference our office was closed for the day, so he emailed instructions, which I followed but did not succeed. I have informed him and let me hope he comes up with some other suggestions.

    Best Regards/AHK

  • 0 in reply to AHK

    Hi Erzsi,

    Your Chat and Call support are not able to help. 

    Will you please forward my case to some senior Annalist, or If possible suggest any other alternate 'method'.

    Best Regards/AHK

  • 0 in reply to AHK

    Hi

    Thank you for the update, I've sent a follow up to the team asking that a callback be scheduled. Should be able to update you shortly.

    Warm Regards, 
    Erzsi

  • 0 in reply to Erzsi_I

    Erzsi Thank you,

    Awaiting call from callbacks.

    Best Regards/AHK

  • 0 in reply to AHK

    Hi Eszi,

    Through the help of yr chat supporter -Erika, was able to SHARE company, but not able to access this company from my other locations, whereby restricting my  operations. 

    Please advise/direct my problem to concerned persons.

    Best Regards/AHK

  • 0 in reply to AHK

    Hi

    I see that you were on chat today. Noting the 10 hour time difference that Mauro mentioned. I've asked the Sage 50 CA support management to schedule a call for 7 am PST (4pm your time) tomorrow. Will update you with any news. 

    Warm Regards, 
    Erzsi

  • 0 in reply to Erzsi_I

    Update that the team has availability today at 1pm PST (11:00pm your time)... The only 7:00am PST (4:00pm your time) slot next available is Wednesday the 22nd which may be too long for you to wait. Feel free to email me at [email protected] your availability. I believe the last few attempts we tried to reach you at the phone number ending 7625 of your office.

  • 0 in reply to AHK

    Following this thread with interest.  I have a similar problem - unable to share an existing company.  I am, however, able to share a newly-created company with no transactions.  Chat suggestions did not resolve anything. It is especially interesting to read that there was support team availability at exactly the same time I was repeatedly getting the voice system telling me (in so many words) "nobody here to help you. Have a look at our wonderful web resources. click."  Something that has been happening for two days now.

  • 0 in reply to Kath Hooson @ ORS

    I cannot open companies after doing the update. I waited on hold for 3.5 hours the other day and we had to restore backup. I was to reshare company after the call which sounded easy but I cannot share. Nothing happens! Now I have another company doing the same thing. I need to be able to work remotely and I can't. I also have a company that cannot open their data files. Worked with Mauro today and now I have to go into their office tomorrow morning at 7:30 with a USB key to try to restore their data. This is unacceptable. Who is paying me for these lost hours. I have probably spent 20 hours in the last couple of weeks trying to get this update to work for my companies and I NEED to have remote access. I am working off USB keys again. Please do another update that actually works!

  • +1 in reply to Erzsi_I
    verified answer

    Thank you Erzsi, for your continuous support. Through the help topics from your web pages, have overcome the problem and now able to log on and share the company  from other comp. If possible please inform call person  not to call me to save their time.

    RECTIFYING THE BASIC FAULTS IN 2020.2

    1.  I have noticed that my accountant can use the same email ID and password as -sysadmin-  for opening Remote Data  Access, which makes it not possible to access program by sysadmin or other user as a message props -( can not open the company as some other user has opened the company, try later). Please change this method to allow each users to use separate ID/emails and password, so multi users can Access  it simultaneously.

    2. In updated version of 2020.2 , the users have right/access to change their user names and passwords, which is not in the interest of sysadmin/owners of the program, as users are free for manipulations, if his services are discontinued.

    3. To Backup the data, one has to close the program Mode from Multi-Users to Single-User, which not convenient, it must have a system in both the Modes to switch without closing the program.

    Please make sure to change the above  faults.

    Best Regards

  • 0 in reply to Kath Hooson @ ORS
    SUGGESTED

    Murphy (he of the Laws) must have his attention elsewhere today.  I got in the queue, first try, at 17:44 UCT (10:44 PDT). Received the call-back 1:03 later (18:47 UTC), by a fellow whose name I missed, but who was in South Africa.  After a couple of preliminaries to establish exactly the steps to reproduce the symptoms of the failure, the first suggestion worked.  We removed all the other users but sysadmin, and the company shared successfully.  Here's hoping this will be my last post on the subject.  Actual time on call was 9 minutes.

Reply
  • 0 in reply to Kath Hooson @ ORS
    SUGGESTED

    Murphy (he of the Laws) must have his attention elsewhere today.  I got in the queue, first try, at 17:44 UCT (10:44 PDT). Received the call-back 1:03 later (18:47 UTC), by a fellow whose name I missed, but who was in South Africa.  After a couple of preliminaries to establish exactly the steps to reproduce the symptoms of the failure, the first suggestion worked.  We removed all the other users but sysadmin, and the company shared successfully.  Here's hoping this will be my last post on the subject.  Actual time on call was 9 minutes.

Children