109 SQL error

109 SQL error

Post by Giovanni » Mon, 22 Mar 1999 04:00:00

When I install SQL server, the installation break on start
SQLExecutive. In the Event viewer there is this error:
The SQLExecutive service terminated with service-specific error 109.
What means?

109 SQL error

Post by Neil Pik » Tue, 23 Mar 1999 04:00:00


> When I install SQL server, the installation break on start
> SQLExecutive. In the Event viewer there is this error:
> The SQLExecutive service terminated with service-specific error 109.

Q.     I'm having trouble installing SQL Server.  What could be going wrong?
(v1.19 1999.03.22)

A.  Try the following check-list of things that could go wrong.  I've never
known anyone not to install SQL after following these instructions.  (If you're
the first then let me know)

1.  Make sure you have administrator level permissions on the machine in
question, as SQL needs to create registry entries, services etc.

2.  Make sure the machine is of the required spec to run the version of SQL you
are installing.  I.e. if it is SQL EE then make sure you have NT EE.  For SQL 7
you need a 100% Intel pentium compatible chip or an Alpha etc.  There is a
full-list in another faq entry.

3.  If you have tried to install SQL before then manually clean-up all the
files/registry entries as follows :-

Remove the <sql> directory and everything under it
Remove the <sql> dir from the path (use control panel/system for this)
Remove the SQL registry entries using regedt32/regedit. These are :-
   (All versions)
   (6.0 and above.)
   (7.0 and above)
   HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server 7

4.  If SQL is complaining about not enough space being there, then this could
be due to a known bug when there is between <n> times 4,295,917 KB and <n>
times 4,367,417 KB.  To get around this either create temporary files to use
space up, or start the SQL setup program as follows.  Spacing is important.

     <sqldir>\i386\setup /t SpaceChecking = Off

5.  SQL Server is dependent on network functionality - even for the set-up
routines.  Specifically it needs to use named-pipe/mailslot functionality (on
NT machines - see number 6 for Win9x).  These usually require a network card to
be present.  If you don't have a network card then go to control
panel/networks, choose add adapter and then add the Microsoft loopback adapter
- which is just a dummy driver, no hardware involved.  This needs to have
working network protocol(s) bound to it.  Let whichever protocols you have use
default parameters, EXCEPT for tcp-ip.  If you are using this then do NOT
specify dhcp assigned address, use as the IP address and as the subnet mask.  This is a standard RFC1918 non-routed IP
address so shouldn't clash with any dial-up address you may be given by an ISP.

If the server service does not start after installing the loopback adapter and
you get the following message in the event log, then you need to re-install
your *NT* service pack to synchronise your NT networking files.  "The server
service terminated with the following error: Not enough server storage is
available to process this command"

One way of testing that the named-pipes functionality works is to run the
makepipe and readpipe utilities that come with SQL Server.  Run makepipe in one
command window.  Then run readpipe in another.  If these work (i.e. the
readpipe connects to makepipe and closes it down) then it is a good indication
that networking functionality is ok.

6.  If you're installing SQL 7 on Windows 9x then you have to install Microsoft
Client for Networks via the Network applet in Control Panel.  It must also be
your primary network logon.  Once SQL 7 is installed then it doesn't need to be
your Primary Network Logon, but it still needs to be installed.

7.  Because a named-pipe, used by the set-up routine, is effectively a file as
far as the operating system is concerned, real-time Virus scanners can cause
problems.  Most of these have been fixed so they don't interfere with SQL's
named-pipes, but make sure you're running the latest version of whichever virus
package you use.  But if in doubt, then disable the virus software for the
duration of the install.

8.  Other software packages can also interfere with SQL's install - typically
they interfere with named-pipes/mailslot connectivity by intercepting requests.  
Setup will terminate with an error like 'unable to write to mailslot.....'.  
Shut-down any of these for the duration of the install.  Packages that are
known to interfere with SQL's setup routines include :-

   IIS - Internet Information Server - the web parts, not FTP
   PWS - Personal Web Server
   Exchange Server

9.  If the dial-up networking icon/window appears and tries to make a network
connection, then stop and disable the "Remote Access Autodial Manager" service
via control panel/services.  This is an NT issue rather than a SQL one, but
disabling auto-dial is the easiest way around it.

10.  If you are upgrading make sure that the default database for the "sa"
login is master.

11.  If the error is to do with SQL Performance Monitor counters - SQLCTRxx.DLL
- then try removing the SNMP service and all 3rd party network/server
monitoring tools.  e.g. HP NetServer Agents, Compaq Insight Manager

12.  If the problem is to do with ODBC files not installing (normally a SQL 7
problem), then check that nothing has the ODBC files open.  This could be other
SQL utilities, Exchange, IIS, SNMP Service, Compaq Insight Manager, Backup Exec
and many other services.  Download NTHANDLEX from www.sysinternals.com if you
can't figure out what has the file(s) open.  it could also be that the ODBC
files on your hard-drive have been marked as read-only.  Check with ATTRIB.EXE
or explorer to see if this is the case.

13.  If it hangs on "Setup is now installing the initial SQL Server
configuration" screen, then it could be a timing problem caused by a VERY fast
hard disk subsystem.  Check the instmsb.out file in the <sql>\install directory
and look for the following messages.

   98/01/28 12:28:31.43 spid11   Database 'msdb' cannot be opened - it is
currently being created.  Wait and try query again.

   98/01/28 12:28:31.43 spid11   Unable to proceed with the recovery of dbid
<5> because of previous errors.  Continuing with the next database.

If this is the error then copy the SQL Server installation files to the local
hard disk drive.  Edit the Instmsdb.sql file. Add a WAITFOR DELAY '0:00:01'
statement to the very beginning of the script.

14.  If the .OUT files indicate that ISQL cannot connect to the SQL Server to
run scripts then you can try the following (note this isn't supported, and the
author has only used it to fix servicepack installs so far, but it *may* work
for full installs as well).  After making the change run "setup /t Local = Yes"

   Make a backup of the setup.inf first, then find the following line

   set !ServerName = $(!ComputerName)

   Now add the following 3 lines after it

   ifstr(i) $(!Local) == "Yes"
   set !ServerName = "."

15.  If it still can't connect to the server during install then this could be
a timing problem due to you choosing a non-default codepage/sort-order.  Try
installing using the default settings.  If this works then re-run the setup
program after install and re-build master to the settings you want.

16.  For SQL 7 check the cnfgsvr.out file in <sql>\install.  If you get "An
error occurred while attempting to start the service (5)" then this error means
that the service has got an access denied.  Check that the account you have
asked SQL Server/SQL Agent to start under has the "logon as a service"

17.  Make sure for upgrades that SQL Server has a name.  Run sp_helpserver and
check what name srvid of 0 has.  If it is not there then run sp_addserver
'<servername>', 'LOCAL'

18.  If you're getting a 109 error starting SQL Executive then this is a
permissions problem with the NT account you've supplied not having permissions
to the relevant service or registry keys - HKLM\SOFTWARE\MICROSOFT\MSSQLSERVER.  
The easiest thing to do is install both MSSQLSERVER and SQLEXECUTIVE with the
localsystem account and then go back and change it later.

19.  One or more of the preceding 18 fixes should get the setup routine run
through.  If it still isn't installing then check the *.OUT files in the
<sql>\install directory for clues as to what is going on.

20.  If the setup seems to run ok, but then SQL won't start then try the
From the <sql>\binn directory run the following, making sure that the spacing
and case is correct

   setup /t RegistryRebuild = On

The setup routine will now run and ask you all the normal questions.  Answer
these as if you were performing the install again (same paths etc.) and it will
just update all the registry entries/icons etc.  It will leave the databases

21.  Once installed, if you have trouble registering your SQL Server by name in
SQL EM, then just register it with a name of just a period.  i.e. "." without
the quotes.  This again bypasses the network layer and ensures that a local
named-pipe is used.

 Neil Pike MVP/MCSE.  Protech Computing Ltd
 (Please post ALL replies to the newsgroup only unless indicated otherwise)
 For SQL FAQ entries see
 http://go.compuserve.com/sqlserver (library 1) - latest stuff is always here


1. more Re: SQL Executive error 109 and MS SQL 6.5

I am new to the list, and I have a question about an error
I get when I try to start the MS SQL Executive sevice from
my system control panel.
I get a specific service error of 109.
The diagnostics (see below) seem to indicate that SQL
Executive seems to think I am running MS SQL 6.0 servers.
I have installed and am running SQL Server 6.5
Diagnostic information is at the end of this post.

Is there a registry entry that is messed up?
If so, how do I repair it?

Does anyone know what this means or where I can find
help concercning this?

John Boller

diagnostic info....

Microsoft (R) SQLExecutive 6.50.201
Copyright (C) Microsoft Corporation, 1995, 1996.

3/31/98 8:44:05 PM - ? SQLExecutive started from command line
3/31/98 8:44:05 PM - ? SQL Executive version 6.50.201
3/31/98 8:44:05 PM - ? SQL Server version 0.00.000
3/31/98 8:44:05 PM - ? DB-Library version 6.50.201
3/31/98 8:44:05 PM - ! This version of SQLExecutive requires SQL Server
version 6.5 or later
3/31/98 8:44:05 PM - ? SQLExecutive terminated

2. subscribe

3. 109 and 1058 SQL error

4. VB4 Help File Creation

5. SQL Server Error 109

6. ActiveX telephony, ShowNTel

7. SQL Exectutive server specific error 109

8. View use

9. Error 109 during SQL 6.5 setup

10. SQL Server Error: 109

11. Famous SQL Executive 109 Error

12. Help - SQLExecutive Service Error 109

13. === installtion error 109 ???