I agree, it looks like SQL server configuration issue. Have you applied any SQL updates?
Modern versions of SQL (similar to Windows Server) are locked down, so only crucial components or services run. If you're accessing the finance system remotely, the likes of Named Pipes plays a crucial role.
Other basic things you can try are resetting SQL services, as this also can clear issues.
Just standard server updates this morning after the initial problem was logged. There were no specific SQL updates visible.
The use of Named Pipes was implemented for a connection to correctly work through our VPN method. This seemed to resolve a previous issue we had with the user who was directly connected to the domain. I have switched the user between the two available methods today to see whether it worked and it made little to no difference.
I will try resetting the services which I assume (and am likely wrong) is just stopping and starting on the server?
Hi, not sure if I had this one, but check if the SQL service is running, the password for the user running the service may have been changed or the permission to run as local service revoked. I know MS just changed a lot of security holes concerning stored passwords in services and GPO's
@Paul_Fielder , how exactly does one see if the 'run as a local service' has been revoked?
One of my main issues with dealing with the software is that it is difficult for me to replicate the issue. So I have to wait for it to occur again before knowing that it is still hapening. This is causing a lot of issues with the Finance team here because there is only so much I can do and only so much Civica are willing to do.