FAQ SQL Server

If you encounter problems during installation, here are some hints on how to proceed.

Overview

pCon and vS plugin disappeared after an update

As soon as you execute an update via the pCon-Planner and not via the vS-Installer, the pCon-Planner will be uninstalled when reinstalling via the vS-Installer. To do this, perform the following step:

  1. New installation of pCon-Planner
  2. Reinstalling the vS plugin

Connection to database goes wrong

This happens when a new Windows user is logged in and tries to access the database. The vS-Installer configurations remain only with the user where the initial installation was performed. You have the following options:

  • Open the vS-Installer after the new user has logged in and enter the user and the e-mail account or the MS SQL server, user and password at the top, as well as under Configuration.
  • Start the vS-Installer on the user where the initial installation was performed. Under Tools, you can then click on Backup Registry to save the configurations to a desired location. As soon as the new user is logged in, he can take over the data by double-clicking on the previously created file.

System requirements for SQL Server installation

To install SQL Server on a system, the following requirements must be met:

  1. Windows 10 Professional must be installed as the operating system as a minimum requirement.
  2. For your language, also install only the SQL server in the operating system language used (e.g. German).
  3. Administration rights on the system are necessary.

Problems with the language during installation

Visual-STORE is always delivered with a German package MS SQL-Server. If you use an English or Swiss Windows, it will always cause an abort during the installation.
The following solutions:

  1. Reinstall and activate the German language for your system.
  2. Use the English package MS SQL-Server (we can also provide this on request).

Manual correction, if the access to the server does not work out

Is the SQL server installed on your system, but there are still problems.

Checking whether the SQL Server service is running:

  1. Open the SQL Server Configuration Manager Console.
  2. Check here if the SQL Server (instance name) service is running, if not start it and change the start mode to Automatic.

Check that the protocols are all enabled:

  1. Open the SQL Server Configuration Manager Console.
  2. Look here in the Configuration items and enable all protocols (TCP/IP, Named Pipes, Shared Memory).
  3. Please perform for all configurations.
  4. After that, please restart the SQL Server (instance name) service.

Check if the login with the user sa works:

  1. Open the SQL Server ... Management Studio.
  2. Under Authentication, select SQL Server Authentication.
  3. Use here the administrator sa (alternatively your own created admin access) with its assigned password.
  4. If it already fails here, you can now log in as a local user, as follows:
  5. Switch authentication back to Windows authentication.
  6. Select Connect, and then a separate administrator must be created on the SQL server.
  7. In the Security item, you can define your own administrator in the Logins submenu.
  8. With the new administrator created here, you can test the logon in the SQL Server ... Management Studio. To do this, close Management Studio once and open it again and perform steps 2-3. If this was successful, you can use this data and store it in the VStore Installer for access to the visual-STORE database.

Was the SQL Server installation unsuccessful or ends with errors:

  1. Evaluation of the error message, if it becomes too complex here, our support must assist.
  2. Often, restarting Windows and then restarting the installation of the SQL server also helps.
  3. Windows updates that run in parallel with the SQL server installation cause problems, let them finish and then restart Windows and then the installation of the SQL server again.

Access from a PC system to a central SQL server:

  1. The central SQL server must be accessible from the PC system in the LAN.
  2. On the central SQL server, all protocols and the SQL Server Browser service must be enabled.
  3. The SQL Server Browser service must be in Automatic startup mode.
  4. Firewalls at the clients as well as at the server can hinder the communication to the SQL server. Microsoft provides a corresponding HowTo on how to configure firewalls.
  5. All necessary databases for visual-STORE must be installed on the central SQL server.
  6. On the clients, the VStore installer must be executed once per user and user profile and the data for access to the SQL server must be stored.
  7. The name of the central SQL server (field: MS SQL server) in the VStore installer is the following combination server name\SQL server instance (ex: MyServer\VSSQL). Instead of the server name, you can also specify the IP address to the server. The name of the SQL server instance can also be different, this is defined in the course of the SQL server installation at the beginning.