- \n
- Overview<\/a><\/li>\n
- pCon and vS-Plugin have disappeared after an update<\/a><\/li>\n
- Connection to the database failed<\/a><\/li>\n
- System Requirements for SQL Server Installation<\/a><\/li>\n
- Problems with language during installation<\/a><\/li>\n
- Manual correction if server access fails<\/a>\n
- \n
- Check if the SQL Server service is running:<\/a><\/li>\n
- Check if all logs are enabled:<\/a><\/li>\n
- Check if login works with user sa:<\/a><\/li>\n
- Was the SQL Server installation unsuccessful or did it end with errors?<\/a><\/li>\n
- Access from a PC system to a central SQL server:<\/a><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
\n\npCon and vS-Plugin have disappeared after an update<\/h4>\n
Once an update for pCon.planner is performed via pCon.planner itself and not via the vS-Installer, pCon.planner will be uninstalled when attempting to reinstall via the vS-Installer. The following step must be performed for this:<\/p>\n
- \n
- Reinstallation of pCon-Planner<\/li>\n
- Reinstall vS Plugin<\/li>\n<\/ol>\n<\/div>\n
\n\nConnection to the database failed<\/h4>\n
This happens when a new Windows user logs 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:<\/p>\n
- \n
- Open the vS installer after the new user has logged in, and enter the user and email account at the top, as well as the MS SQL server, user, and password under Configuration.<\/li>\n
- Start the vS-Installer on the user where the initial installation was performed. Under Tools, you can then save the configurations to a desired location by clicking on Backup Registry. As soon as the new user logs in, they can import the data by double-clicking the previously created file.<\/li>\n<\/ul>\n<\/div>\n
\n\nSystem Requirements for SQL Server Installation<\/h4>\n
To install SQL Server on a system, the following prerequisites must be met:<\/p>\n
- \n
- Windows 10 Professional must be installed as the operating system as a minimum requirement.<\/li>\n
- For your language, also install only the SQL server in the language of the operating system used (e.g., German).<\/li>\n
- Administrative rights on the system are necessary.<\/li>\n<\/ol>\n<\/div>\n
\n\nProblems with language during installation<\/h4>\n
Visual-STORE is always delivered with a German package MS SQL Server. If you use an English or Swiss Windows, it will always lead to an abortion during installation.
\nThe following solutions:<\/b><\/p>\n- \n
- Install the German language for your system and activate it.<\/li>\n
- Use the MS SQL Server English package (we can also provide this upon request).<\/li>\n<\/ol>\n<\/div>\n
\n\nManual correction if server access fails<\/h4>\n
Is the SQL Server installed on your system, but you're still encountering issues?.<\/p>\n
\nCheck if the SQL Server service is running:<\/h4>\n
- \n
- Open the SQL Server Configuration Manager Console.<\/em><\/li>\n
- Check here if the service SQL Server (Instance Name)<\/em> runs, if not start this one and change the startup mode to Automatic.
\n<\/em><\/li>\n<\/ol>\n<\/div>\n\nCheck if all logs are enabled:<\/h4>\n
- \n
- Open the SQL Server Configuration Manager Console.<\/em><\/li>\n
- Look here at the points Configuration<\/em> and activate all protocols (TCP\/IP, Named Pipes, Shared Memory).<\/em><\/li>\n
- Please perform for all configurations.<\/li>\n
- Start the service afterwards SQL Server (Instance Name)<\/em> new.<\/li>\n<\/ol>\n<\/div>\n
\nCheck if login works with user sa:<\/h4>\n
- \n
- Open the SQL Server Management Studio.<\/em><\/li>\n
- Choose under authentication SQL Server Authentication.<\/em><\/li>\n
- Use the administrator here A <\/em>(alternatively your own created admin access) with its assigned password.<\/li>\n
- If it fails here, you can now log in as a local user, as follows:<\/li>\n
- Authenticate again Windows Authentication<\/em> rearrange.<\/li>\n
- Connect, select, and then you must create your own administrator on the SQL server.<\/li>\n
- At the point Security<\/em> can you in the submenu Registrations<\/em> set up your own administrator.<\/li>\n
- With the administrator now created, you can log in to the SQL Server Management Studio<\/em> test it. To do this, close and reopen the Management Studio and perform steps 2-3 again. If this was successful, you can use this data and in VStore Installer<\/em> for accessing the visual-STORE database.<\/li>\n<\/ol>\n
![](\"https:\/\/support.visual-store.de\/wp-content\/uploads\/2023\/07\/image-2.png\")
<\/p>\n<\/div>\n\nWas the SQL Server installation unsuccessful or did it end with errors?<\/h4>\n
- \n
- Evaluation of the error message; if it becomes too complex here, our support team will need to assist.<\/li>\n
- A restart of Windows and then restarting the SQL Server installation often helps as well.<\/li>\n
- Windows Updates running in parallel with the SQL Server installation cause problems; let them finish, then restart Windows and try the SQL Server installation again.<\/li>\n<\/ol>\n<\/div>\n\n
Access from a PC system to a central SQL server:<\/h4>\n
- \n
- The central SQL server must be accessible from the PC system in the LAN.<\/li>\n
- On the central SQL server, all Protocols<\/em> and the service SQL Server Browser<\/em> to be activated.<\/li>\n
- The SQL Server Browser service must be in the Automatic startup mode.<\/li>\n
- Firewalls on both the client and the server can hinder communication with the SQL Server. Microsoft provides a HowTo on how to configure firewalls accordingly.<\/li>\n
- All necessary databases for visual-STORE must be installed on the central SQL server.<\/li>\n
- On the clients, it must be done once per user and user profile VStore Installer<\/em> executed and the data for accessing the SQL server is stored.<\/li>\n
- The name of the central SQL server (field: MS SQL Server<\/em>In VStore Installer<\/em> is the following combination Server-Name\\SQL-Server Instance <\/em>Ex. MeinServer\\VSSQL<\/em>Instead of the server name, the IP address can also be specified for the server. The name of the SQL Server instance can also be different; this is set during the SQL Server installation at the beginning.<\/li>\n<\/ol>\n<\/div>\n<\/div>","protected":false},"excerpt":{"rendered":"
FAQ SQL-Server Sollten Probleme bei der Installation vorkommen, hier einige Hinweise zur Vorgehensweise. \u00dcbersicht \u00dcbersicht pCon und vS-Plugin sind nach einem Update verschwunden Verbindung zur Datenbank geht schief Systemvoraussetzungen f\u00fcr die SQL-Server Installation Probleme mit der Sprache bei der Installation … Read More<\/a><\/p>","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-121","page","type-page","status-publish","hentry"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/support.visual-store.de\/en\/wp-json\/wp\/v2\/pages\/121","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/support.visual-store.de\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/support.visual-store.de\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/support.visual-store.de\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/support.visual-store.de\/en\/wp-json\/wp\/v2\/comments?post=121"}],"version-history":[{"count":5,"href":"https:\/\/support.visual-store.de\/en\/wp-json\/wp\/v2\/pages\/121\/revisions"}],"predecessor-version":[{"id":1588,"href":"https:\/\/support.visual-store.de\/en\/wp-json\/wp\/v2\/pages\/121\/revisions\/1588"}],"wp:attachment":[{"href":"https:\/\/support.visual-store.de\/en\/wp-json\/wp\/v2\/media?parent=121"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- Choose under authentication SQL Server Authentication.<\/em><\/li>\n
- Look here at the points Configuration<\/em> and activate all protocols (TCP\/IP, Named Pipes, Shared Memory).<\/em><\/li>\n
- Check here if the service SQL Server (Instance Name)<\/em> runs, if not start this one and change the startup mode to Automatic.
- Open the SQL Server Configuration Manager Console.<\/em><\/li>\n
- Check if all logs are enabled:<\/a><\/li>\n
- pCon and vS-Plugin have disappeared after an update<\/a><\/li>\n