I finally figured out what the problem was and I hope this may help out someone else in the future. This was a conversion from BDE to Firebird initially. The main computer that is acting as the TS server for some reason was pointing to the workstation as its database server. Very strange how or why this would happen. I was unsure where to point this as it didn't seem to work pointing it to itself as the server. Using the TS Server Admin/Diagnose this computer, I pointed it to the MAIN.FDB was located. I discovered this was the correct file based on the extension and that it was located in the same Dir that the previous BDE database was. After doing this I then needed to open the  "View Network Database" in the TS Admin and select the database and chose register. After that I went to the workstation and fixed the settings in there and Voila everything worked as expected. It is unfortunate that I did not have access to the Knowledgebase when trying to figure this out. The Sage people while trying to be helpful to help me gain access to that part of the portal took too long to be very helpful. 

I hope this helps someone in the future.

Thanks for all who responded.

-Dave

I finally figured out what the problem was and I hope this may help out someone else in the future. This was a conversion from BDE to Firebird initially. The main computer that is acting as the TS server for some reason was pointing to the workstation as its database server. Very strange how or why this would happen. I was unsure where to point this as it didn't seem to work pointing it to itself as the server. Using the TS Server Admin/Diagnose this computer, I pointed it to the MAIN.FDB was located. I discovered this was the correct file based on the extension and that it was located in the same Dir that the previous BDE database was. After doing this I then needed to open the  "View Network Database" in the TS Admin and select the database and chose register. After that I went to the workstation and fixed the settings in there and Voila everything worked as expected. It is unfortunate that I did not have access to the Knowledgebase when trying to figure this out. The Sage people while trying to be helpful to help me gain access to that part of the portal took too long to be very helpful. 

I hope this helps someone in the future.

Thanks for all who responded.

-Dave

Actually that's problematic, Dave. The database should not be in a shared location, should not be named MAIN.FDB, and there may be additional issues that should be resolved.

The installation parameters changed when we went to SQL in 2016, and the method you are using is what we would have recommended prior to that. 

During the install it's highly recommended to use the defaults to get the install correct. It can easily be corrected, but we should chat/talk to her all the info communicated with your specifics.

I would recommend you contact Sage support for assistance to correct these potential issues. Your client will appreciate it. 

Note that access to the Sage Knowledgeable for Timeslips requires no credentials. Merely go to sagekb.com and enter your search query.