Table of Contents |
---|
...
In current versions of NorthStar Order Entry, Web Admin has a tool specifically for this task. Choose "Fix SQL Authentication" on the Utilities page.
localhost:8082/webadmin/utilities.html
Procedure for previous versions of Order Entry
...
If you are using Windows 10, SQL Server Configuration Manager may not be listed in the Start menu. In this case go to Start → Run and run one of the following commands:
- "SQLServerManager12.msc" (SQL Server 2014)
- "SQLServerManager11.msc" (SQL Server 2012)
- "SQLServerManager10.msc" (SQL Server 2008)
it is also found in C:\Windows\SysWOW64\ labelled SQLServerManager11.msc
Step 2: Putting SQL Server in single-user mode
Make sure all NorthStar Order Services are stopped
In the "SQL Server Services" node, stop all SQL Server services. Make a note of which ones were started, you will need to restart them in step 4.
Find the SQL Server service named "SQL Server (SQLEXPRESS)". The instance name might be something other than "SQLEXPRESS", but the name should just be "SQL Server". Right-click and click Properties.
Under the Startup Parameters tab, add a new parameter "-m
" (this is a hyphen and a lowercase m, with no whitespace).
Save these settings and restart ONLY the "SQL Server (SQLEXPRESS)" service.
...
Restart SQL Server and continue with step 4.
Login Failed. The login is from an untrusted domain and cannot be used with windows authentication
Follow these steps to disable loopback:
Click Start, click Run, type regedit, and then click OK.
Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
Right-click Lsa, point to New, and then click DWORD Value.
Type DisableLoopbackCheck, and then press ENTER.
Right-click DisableLoopbackCheck, and then click Modify.
In the Value data box, type 1, and then click OK.
Exit Registry Editor.
Restart the computer.
Should look like this:
Method 2 on the microsoft page here: https://docs.microsoft.com/en-us/troubleshoot/windows-server/networking/accessing-server-locally-with-fqdn-cname-alias-denied