Very Computer

My computer is a stand alone NT 4.0 server connected to an ADSL line to the
Internet.

When I go to install the Service pack (SP 4), logged in as Administrator,
it asks for my password, which I then type.

However, it then gives me the following message:

The entered password failed verification, please check your password.

Any idea what this messsage is?  Iasume that I need to be an administrator
to install the SP, but as far as I can tell I am.

Any help would be appreciated.  Thanks.

Cheers

Leigh

Quote:> I have SQL 6.5 installed on NT 4.0 (SP 4).  This is the version that came
> with Visual Studio 97 (Enterprise edition).
> When I go to install the Service pack (SP 4), logged in as Administrator,
> it asks for my password, which I then type.
> The entered password failed verification, please check your password.

A.  Try the following checklist :-

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

2.  SQL Server is dependent on network functionality - even for the set-up
routines.  Specifically it needs to use named-pipe/mailslot functionality.  
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
192.168.1.1 as the IP address and 255.255.255.0 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.

3.  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.

4.  Other software packages can also interfere with SQL's install - typically
they interfere with named-pipes/mailslot connectivity and 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

5.  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.

6.  If it still isn't installing then check the *.OUT files in the
<sql>\install directory for clues as to what is going on.

7.  If the .OUT files indicate that ISQL cannot connect to the SQL Server to
run scripts then you can try the following unsupported hack (it's worked for
me though) by modifying the servicepack's setup.inf.  After modifying the
setup script 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 = "."
    endif

 Neil Pike MVP/MCSE
 Protech Computing Ltd
 (Please post ALL replies to the newsgroup only unless indicated otherwise)