Run AutoUpdate Correctly in Windows: Limited User Rights, or Authentication to Connect ShipWorks to SQL Server
ShipWorks is committed to providing seamless and efficient software experiences for our users. We have reinstated the AutoUpdate (AU) feature to ensure that you always have the latest updates and improvements without the need for manual intervention. However, depending on your Windows environment, certain configurations may be required to ensure this feature operates correctly.
This guide is intended for ShipWorks users, particularly those responsible for IT administration, to address the two primary issues that may affect the AutoUpdate feature causing it to be unable to complete the update.
-
Utilizing ShipWorks with a Windows user who does not have admin permissions to install software applications.
-
Connecting the ShipWorks application to SQL Server using Windows Authentication.
To ensure the AutoUpdate feature works smoothly, it is essential to properly configure it. Without the correct settings and the necessary administrative permissions, the ShipWorksUpdater service may not function correctly and will fail to update.
Windows Authentication and AutoUpdate
Previous help documents incorrectly stated that Windows Authentication could not be used with AutoUpdate. This is incorrect. Windows Authentication can be used when configured as noted in the steps below.
You need to take 2 important action steps to ensure AutoUpdate will run correctly. These are:
-
Configure the ShipWorks.exe application to connect to your SQL Server database using Windows Authentication (instead of SQL Server Authentication), and then
-
Ensure ShipWorksUpdater Service Runs as an Admin User when the logged-in Windows user does not have rights to install software.
If you wish for ShipWorks to connect to the SQL Server using Windows Authentication and still allow AutoUpdate to function, follow these steps to Verify Windows Authentication User Permissions:
-
Open SQL Server Management Studio (SSMS).
-
Connect to your SQL Server instance.
-
Navigate to Security & Logins.
-
Locate or add the Windows user account that ShipWorks will use for authentication.
-
Right-click the user and select Properties.
-
Grant Full SQL Server Access:
-
In the user properties window, go to User Mapping.
-
Select the appropriate ShipWorks database.
-
Ensure the user is mapped to the ShipWorks database.
-
Assign the user the
db_owner
role for the ShipWorks database.
-
Ensure ShipWorksUpdater Service Runs as an Admin User when the logged-in Windows user does not have rights to install software
The ShipWorksUpdater service needs to run with administrative privileges to install updates. Follow these steps to configure it properly:
-
Open the Services Management Console.
-
Press Win + R, type
services.msc
, and press Enter. -
Locate ShipWorksUpdater Service.
It may look something like ShipWorksUpdater - 1f067f4f-26e6-4843-bd6c-12389a4a3274.
-
Right-click the service and select Properties.
-
Configure the Service to Run as a Windows Admin User.
-
Go to the Log On tab In the Properties window.
-
Select This account.
-
Click Browse and choose a Windows admin account.
-
Enter the credentials for this Windows user with administrative privileges.
-
Click Apply and then OK.
-
-
Restart the Service:
-
Go back to the Services Management Console.
-
Right-click the ShipWorksUpdater service and select Restart.
-
By following these steps, you can ensure that the ShipWorks AutoUpdate feature functions correctly in your Windows environment. This proper configuration will help maintain the efficiency and reliability of ShipWorks, keeping your operations running smoothly with the latest updates and features.
If you encounter any issues or need further assistance, please contact our support team. We are here to help ensure your ShipWorks experience is as seamless as possible.
Still Need Help?
Please feel free to reach out to one of our awesome Technical Support Representatives in St. Louis. We are happy to help.
Have a comment to share about this article? We'd love to hear from you. You must be logged in to your Support Portal account to leave a comment.
Comments
0 comments