After windows update, we get a Server Does Not Exist or Access Denied. However, the server is available and mapped in the network and the station was working before the update.
After windows update, we get a Server Does Not Exist or Access Denied. However, the server is available and mapped in the network and the station was working before the update.
HI Alvah,
Can you please let me know what page you are trying to launch?
Was the Server name, User name, Password, Database and Connection timeout configured in Store Operations Administrator >> File >> Configuration?
If so, do you get an error when you click Test Database Connection?
Thank you in advance.
We are currently migrating servers (2005 to 2008) and our host backed up the SQL database and transferred it to the new server.
I have transferred the website files and changed the IP address in the connection string and the global.asa file.
So technically speaking we have a mirror image on the new server, but when I try to launch a page that connects to the SQL I get the following error.
SQL_Server_does_not_exist_or_access_denied Upsers
Hi Tom,
Where are you getting the error?
Are you able to connect without issue on the computer running SQL Server?
_______________________________________________
Just a note that Mainstream support for Microsoft Dynamics RMS 2.0 ended on July 10, 2016; and extended support ends on 7/13/2021:
support.microsoft.com/.../search
This is less than 9 months from now; and you can continue using RMS after this date but technical support will not be available.
I would recommend checking with your partner in regard to what they may recommend as a replacement system after the extended support end date.
Thank you in advance.
Your post is contradictory. You said it does not exist or access denied, but you also say it is available?
Sometimes MS updates changes the firewall settings, make sure that the SQL Server service is running on the server, then check that the protocols IP, especially is still enabled and finally make sure that the firewall is setup correctly, normally port 1433. If the service is running and protocols are still ok turn the firewall off on both machines and see if that resolves it. If so, then it is a firewall issue.
André Arnaud de Cal... 291,735 Super User 2024 Season 2
Martin Dráb 230,466 Most Valuable Professional
nmaenpaa 101,156