SageForum for UK versions of Sage 50- Help and support.

Hi guys, thanks for the responses.

Well, i've had a fun saturday. I installed line50 v13 on the local pc's of those that needed sage but couldn't run it from TS.
The only way to get it to work when reading the data on the server was to make the users domain admins (which i didn't want to do for security reasons). Setting them as Administrators didn't work.
This then gave them full read/write access to everything and hence line50 worked from a local install but reading data over the network.
I then checked line50 from TS to see if would work since making the users domain admins. Nope, still wouldn't work, yet they could read/write files to the relevent directories.
This morning our account manager has just informed me that they can ALL now run line50 FROM TS ?!?!?!?! Yet i've altered nothing since saturday.
Totally bizarre! The only thing i can think of is a delayed propagation of permissions, but have been told that's not possible and that they are instantaneous!

I'm still stumped, but it seems for now, that everything works again?!

Well, b*gger that! One user who was on holiday yesterday cannot get into sage via terminal services.
Rang Sage and they have finally come out and said "sorry, we don't support terminal servers, not our problem"

So am back to square one with this user. Permissions are the same as the others! God i hate I.T.....oh, and Sage

k.jacko wrote:Hi guys, thanks for the responses.

This then gave them full read/write access to everything and hence line50 worked from a local install but reading data over the network.

Sage users need FULL permissions, not just read and write permissions

I still would like to know why they can not read/write files over the network.

This appears to be an issue with your server, not Sage. If you cannot, read write and create files in the sage directory, then the OS permissions are not "FULL" for that user and Sage needs FULL permission.

Hi Everyone,

I was looking around for a solution on a Sage problem I have when I saw the messages in this post.
It's amazing how similar they are! (to the extend that I first thought it was someone from our company posting it).

Anyway, I'm having EXACTLY the same problem with Sage in our enviroment (Sage Line 50 2007 with all updates, running on Terminal Servers 2003,....)

After trying EVERYTHING (including giving full admin right to all Sage users, playing around with GPO/permissions/local computers/encryption...) without any success, a colleague found this (weird) solution:
1) Create a new user in AD that you copy from an existing user that works with Sage (hopefully you still have at least one in your environment)
2) Logon with this new user on Terminal Server and launch Sage. This will obsviously gets you to the splash screen and stop.
3) DO NOT KILL THE SAGE APPLICATION, but just logoff the session. This will bring a message from Sage Saying ("are you sure you want to quit" - say "yes")
4) when the user is logged off, add it to the "Domain Admins" group.
5) WHEN YOU ARE 100% SURE that the replication is done on your domain, log back on with the new user on your terminal server and launch sage again.
This will again fail and you will be stuck at the splash screen.
6) Same as above, DO NOT KILL THE SAGE APPS but logoff instead.
7) log back on the terminal (with domain admin rights) and launch Sage again... that should give you the company selection screen and Sage should now work fine.
log off, remove the domain admin rights from the user and log back on... and it should work fine!

I know it sounds long and strange, but this works for me everytime (I've tried it 3 times arlready with different users).

Hope this works for you too.

Cheers,
Steph

This is what we found on http://www.readallaboutit.org.uk/forum/ ... IC_ID=1328

You must be able to write files to the Sage Data Directories of the companies in the company file - that is to be able to write files to the company data folders that appear in the list when you start Sage.

You can test this by going into the folders where the data is kept and copying in a file or creating one with right-click mouse button.

It is a problem with the shortcut as far as we can see - if you look at the properties you can see it runs a file from within common files on the %programfiles% directory I(usually c:\program files\common files)

but it has an shortcut pointing to the flash screen via the file: "C:\Program Files (x86)\Common Files\Sage SBD\SBDDesktop\v11\SBDDesktop.exe" {11A022ED-3870-4039-8967-DD88A57AC117} -SBDSplash="Defaultsplash.bmp"

This seems to make it run the old file: C:\Program Files (x86)\Sage\Accounts\Sage.exe which falls over

To circumvent this we just went and added a new shortcutwith no other splash screens or anything and it appears to work fine.

Could you clarify what the target of the shortcut you made was.

Just to clear this up - having tested this thoroughly the other night it does actually work best with the original shortcut on your desktop but you MUST have write permissions to all the company folders that appear in your company file.

When you open <drive letter:>\programdata\sage\accounts\2013\ and look at the file 'company' you need to be able to write files to every folder in the list otherwise Sage 2013 will not load.

It is a real pain as not everyone in our company needs access to the same company but as they all use the terminal server we have to give everyone read and write permissions to all!

Once you have permission to write data to each of the folders holding the data to all of the Sage companies then you can load Sage 2013 but not before.

Please Sage can you change this and just let us load the list of companies whether we can see the data or not? It will make it easier for companies who have different finance staff for different holding companies etc.

Sage requiring full access to the data directory is clearly explained in the installation documentation, not that anyone ever reads any documentation, so is not a surprise.

You can relocate the data folder to a different location other than <drive letter:>\programdata\sage\accounts\2013\ and you can give different users different access rights to that directory so not sure what the problem is.

There are some manuals specifically aimed Citrix which is a very similar environment
http://support.makingithappen.co.uk/sage-50-manuals.htm

My problem is slightly different. We have just had to remove and re-install Sage on our terminal server due to a ransomware attack. I use it on the terminal server two days a week when I work from home and three days on a network PC in the office.

Since re-installation on the TS, I can only get as far as the company selection screen. As soon as I put in my user name and password and click on OK, Sage just disappears. It's fine on the network PC, it's just remotely that I have this problem.

It may be this:

"if the splash screen appears briefly then disappears after installing the Sage 50 Accounts v22 - February, April or May 2016 Improvements update, please follow these steps:

Windows key > in the search box type %temp% > Enter.
Double-click the SageAccounts folder.
Note: There's a SageAccounts folder and a Sage Accounts folder. You must double-click the one which has no spaces in the folder name.

Double-click the Q3 Update folder, or if this doesn't appear, the latest update folder available, for example, Q2 Update.
Locate and right-click SBDDesktopUpdateInstaller.msi > choose Uninstall > Yes.
Note: If you get the message that the installation package could not be found, this suggests an issue with the Windows install process and you should contact your IT support.

Right-click SBDDesktopUpdateInstaller.msi > choose Install.
"

Check the access right on the c:\ProgramData\Sage directory and all it's sub directories

I would set it to full access for everyone, allow inheritance and overwrite the permissions on all subdirectories.