- Occasionally [DBNETLIB][ConnectionOpen (PreLoginHandshake ()).General network Error Native Code 11 on Undocked machines with Client Operating Systems after starting the machine
- The SQL Service is not started, although the machine is already up and running
- The fact that the SQL Service is not yet started or did not start in time has nothing to do with GoldMine application itself but unfortunately, the visible error message appears only GoldMine itself.
- Undocked machines are usually based on Client Operating systems which means they start differently than a Server OS which may delay the SQL Service to start.
In order to minimize the occurrence of this behavior, here are some recommendations what a user can try.
A. Certain Anti Virus applications may cause a performance delay especially when all MS SQL related files are scanned on the startup of the machine.
While there is no information available if and which Anti Virus app is used on your side here some links which might be helpful to exclude MS SQL files from such scanning
- Articles about excluding Microsoft SQL from Antivirus applications
B Also other services of the OS and/or applications may lead to a temporary overload of the machine. Microsoft recommends, therefore, for example, to set services which are not necessarily directly on the startup to set them on an Automated (Delayed) start INSTEAD of an Automated start as when 'all' services which are set to Automated start in services.msc start almost at the same time it leads to a bottleneck
- Changing Windows OS Services if they are not directly GoldMine related is outside of the GoldMine Support boundaries, which means GoldMine Technical Support may not be able to assist or even adjust the system, but below are some links available, which should help to understand how to configure the Windows system and services.
- Articles about delaying automated starts of services in Windows
C. Create a Batch file which can be executed on demand by the user (for example a StartSQL.bat file on the desktop)
- The following information is provided as-is, without any warranties and at the user's own risk. (there are no risks expected as the batch file content only tries to stop and start the SQL Service).
- Usually, on undocked machines, a Microsoft SQL Express edition is installed with the default instance SQLExpress the batch file can look like
NET STOP MSSQL$SQLExpress
NET START MSSQL$SQLExpress
- If another SQL Edition has been installed as a default instance then the batch file can look like
NET STOP MSSQLSERVER
NET START MSSQLSERVER
- If another instance name was set up then the batch file can look like
NET STOP MSSQL$INSTANCENAME
NET START MSSQL$INSTANCENAME
e.g. if the instance is GMSQL the batch file looks like
NET STOP MSSQL$GMSQL
NET START MSSQL$gmsql