We have Sage 2022 running on a server setup (which was initiated about 16 months ago) and never had an issue accessing the database up until about a month ago. Since then, albeit intermittingly and starting on October the 4th of this year the "Can Not Access Database. Error = 49153" has now appeared about 5 times. In each case a server reboot does the trick but doesn't answer as to why this keeps happening.
It happened again today so another server reboot was done and all good for the time being. But before we rebooted we verified that the actual service was running which it was.
As per suggested we have checked to make sure "Allow remote connections" is checked in the SQL Server. Which it is. TCPIP is enabled and a static port is being used (1433).
According to their IT people the SQL Server 2012 is fully patched.
So we are not sure if MS Updates are causing some issues?
We also started to look at the SQL log files being created and noticed these entries:
"Error: 18456, Severity: 14, State: 38.
Login failed for user 'NT SERVICE\ReportServer'. Reason: Failed to open the explicitly specified database 'ReportServer'. [CLIENT: 10.48.1.8]"
So not sure if the above message may indicate something else going on but thought we would mention here.
Thanks in advance for any input.
It happened again today so another server reboot was done and all good for the time being. But before we rebooted we verified that the actual service was running which it was.
As per suggested we have checked to make sure "Allow remote connections" is checked in the SQL Server. Which it is. TCPIP is enabled and a static port is being used (1433).
According to their IT people the SQL Server 2012 is fully patched.
So we are not sure if MS Updates are causing some issues?
We also started to look at the SQL log files being created and noticed these entries:
"Error: 18456, Severity: 14, State: 38.
Login failed for user 'NT SERVICE\ReportServer'. Reason: Failed to open the explicitly specified database 'ReportServer'. [CLIENT: 10.48.1.8]"
So not sure if the above message may indicate something else going on but thought we would mention here.
Thanks in advance for any input.