Archive for April, 2014


‘Login failed for user ‘.’ Please run System Administration to check company settings.’ error

2013 - Login failed for user

Check the following points:

  • Ensure the Windows user has been linked to the relevant Sage user in System Administration.
  • The Windows user, e.g. ‘JohnBull’, has been included as a user in the ‘Sage Users’ group which is set up as part of the installation process.
  • Check that the ‘Sage Users’ and ‘Sage Administrators’ groups have sufficient permission to access the Sage shared folder (by default, C:\Sage).
  • The ‘Sage Services’ user set up as part of the installation process must have sufficient security permissions on the Sage shared folder.
  •  IIS v8 only – Ensure ‘HTTP Activation’ has been enabled within .NET 4.5 as per the below:

2013 - Login failed for user_IISv8HTTPactivation

Advertisements

I am a bit late posting about this. But at the beginning of April Sage 200 2013 R2 was released.

This isn’t a simple Service Pack, and should be treated as a “New Release”. The key thing here is the introduction of some new features, as well as bug fixes and roll up of fixes from Sage 200 2013 SP1. That said this is the only version of Sage 200 2013 that will now be shipped.

The issues fixed are documented in Sage 200 2013 R2 Release Notes released by Sage.

Please also be aware of updates to the ‘Deployment and installation Guide’ and the ‘System Requirements’.

Part of this release see the introduction of functionality which allows you to analyse Stock Item Sales Order Lines, to Projects. This is quite exciting for me, as I was actually involved in the first workshop at Sage Newcastle, to brain storm how this would work. So to see it come to life some 4 may be even 5 years later is brilliant.

 

Ctayts