Connectivity Issues Between Sage 100 2023 Advanced+SQL to DocLink on One VDI, But Not The Other?

SOLVED

Hello,

We recently upgraded from Sage 100 2018 to Sage 100 2023 (March 15th to be exact). At this time, we also opted to move away from using virtual machines (VMs) in favor of using a master VDI image machine that can then push out to a VDI pool of computers. The upgrade itself seemed to go relatively smoothly all things considered, but users have noted that using the VDI pool machines (now assigned to each user vs. being open to any user) is significantly slower to process common actions within Sage 100. We worked with our network administrators to allocate even more resources to these machines, but that didn't really seem to help much. Our current VDI is running through Denver, Colorado and we're mostly stationed around the upper Midwest, so we thought setting them up closer to the users' physical locations would help speed things up. We had our net admins do a fresh install to a select group of test pool machines on a Chicago VDI and our sample/test users had all reported operation times have sped up, but we've somehow lost the ability to have Sage 100 recognize DocLink (pushing invoices and whatnot from Sage 100 into DocLink).

Our net admin team used the exact same master computer to push all the same things as they did previously to our Denver VDI pools and we have no issues with Sage 100 communicating properly with DocLink at that location, so it's only an issue with our Chicago VDI pool. Has anyone else here experienced a similar issue and if so, what were the steps you did to correct this odd issue? We were hoping to migrate our users from the Denver instance over to our Chicago one, but obviously with the current issue our testers experienced at the Chicago location, we cannot proceed with this plan. We are also rapidly approaching our fiscal year end, so we need to figure out a solution soon because the current Denver load times are going to significantly hinder our finance team's year-end processing.

Any help will be appreciated!

Parents Reply
  • +1 in reply to btmlinesoft
    verified answer

    So after a bit more digging and working directly with the users who had experienced this issue, it was determined they were using a mismatch of Sage 100 credentials and their DocLink ones, which would 100% cause them to not authenticate properly. So, the key is to ensure your users understand the proper credentials to type in when they're within Sage 100 and want to push invoices over to DocLink.

Children
No Data