EDITOR'S NOTE: Share your Windows and .NET discoveries, comments, problems, solutions, and experiences with products and reach out to other Windows & .NET Magazine readers (including Microsoft). Email your contributions (400 words or less) to [email protected]. Please include your phone number. We edit submissions for style, grammar, and length. If we print your submission, you'll get $100. Submissions and listings are available online at http://www.winnetmag.com/articles. Enter the InstantDoc ID number in the InstantDoc ID text box.
My company recently installed Microsoft Internet Security and Acceleration (ISA) Server 2000 on a Windows 2000 server with Service Pack 2 (SP2). The installation went fine, but afterward some ISA Server services wouldn't start. We rebooted the server and received an alert that some services wouldn't start. When we checked NT Event Viewer, we found several system events that stated <Application name> is not a valid Win32 application.... Not only was ISA Server having problems, so were several other services. We searched some newsgroups and formed the hypothesis that long filenames had somehow been disabled on the computer.
In an attempt to fix the problem, we opened a registry editor (regedit.exe) and navigated to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services registry subkey. This subkey contains information related to all Win2K services. We found the ISA Server subkeys and saw that the ImagePath values contain long filenames. We added quotation marks to the beginning and end of each ImagePath value. After we rebooted the server, all the ISA Server services started. We repeated this process for the other services that had been causing problems, and they subsequently all started as well.
We later discovered that the likely cause of the problem was that the registry subkey that enables long filenames was set incorrectly. We started regedit and navigated to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\Win31FileSys-tem registry subkey. If the parameter Win31FileSystem is set to 0, long filenames are supported on FAT32 file systems. If this parameter is set to 1, long filenames aren't supported—only DOS 8.3 names are supported. We set Win31FileSystem back to 0 and rebooted the machine. All the services, including ISA Server, then started.
