Sage 100

Install of 2014 Advanced on a new server, onsite with the customer and the technical staff. They gave full control permissions to the Sage folder, but when the workstation launches, it says ""Unable to create a session object. The workstation may have been corrupted. Re-install Workstation Setup."" I found that KBA and have followed all of the suggested resolutions. Nothing is fixing the problem. Does anyone know more about this?

Terminal server workstation or local? If terminal server, do users have permissions to the c:\sage\client folder (forget actual path) but it's where the client installs to on the tserver?

It's a local network. No terminal server.

The client runs on the server. The workstations have UAC off. We are installing as local admin.

Is the firewall off onThe server? Does it run in mas90 mode?

They say the firewall is off. I just determined that not all of the workstation files are being written to the workstation's C drive. Doesn't that mean that the local admin user they are logging in as doesn't have rights to the C drive?

Have you created an inbound rule on the server for the port?

No. The tech guy says the firewall is turned off so we don't need to.

Interesting. The server path in the sota.ini file wasn't correct, or wasn't liked by the workstations. We manually changed it and now it's working.

To wrap this up, I'm letting you all know that the core problem was permissions after all. The IT guy added the Everyone group to the share, and then the install worked by the book. I gave him the install guide ahead of time, but he admitted that he briefly glanced at it and then ignored it.

I make it even simpler for them - if people don't have full rights to \mas90 and all subfolders then they will have problems eventually.