I am using the UltiDev server to provide an 'offline' version of a site that people can run locally when disconnected.

I have a wrapper app that starts the server, and it mostly works good. A couple of people are running into issues that appear to be related to launching the server and generate a popup message box with the title 'Failure to Launch' and body text "LookupAccountName failed. Error 1332"

The web server is running at this point, but the only message in the log appears to be "Starting hosting ..."

Any suggestions on how best to go about trouble shooting this? So far I've been unable to reproduce the problem locally.

Thanks -- that wasn't a particularly detailed error report!

I'm using UltiDev Web Server Pro 2.0.19

The wrapper app is a .NET 4 application that handles background updates to our web app, and provides a few control

functions (access to logs, deleting cached data).

It mainly just launches UWS.InteractiveServer.Clr4x86.exe with the command line:
/port=9001 "/path=(location of web folder under %APPDATA%)" /vdir=/ /browser=nobrowser

The wrapper runs with elevated permissions

I haven't been able to reproduce the problem, but I've uploaded a (literal) screenshot that I received: https://s3.amazonaws.com...bucket/ultidev-1332.PNG

I've also heard that stopping and restarting will 'fix' the problem intermittently -- may take multiple attempts.

The problem has been reported on both XP Pro SP3 and Win7 x64 Pro (fresh install, not in a domain)

I'll try and get the event log details.

Thanks for your help!

Thanks for the suggestions.

After some trial and error I was able to reproduce the error. Turns out that in both (independent) cases the machine name had been changed after installing. Ironically we'd only switched to trying out the UltiDev server recently, so having two reports of the same obscure error within 24 hours made me assume it was something more fundamental.

I got the same error by installing the server, then changing the machine name and rebooting. In one case I know the machine was actually removed from a domain rather than renamed, but presumably this has the same effect.

Running the 'Repair Server Configuration' option doesn't fix the issue. With the logging turned on there is nothing in the log beyond the 'Starting hosting...' line

Clearly this isn't a common use case ... I was just unlucky enough to run into it twice at once! Still, it might be helpful if the error message could be popped up with the principal name that was being attempted ... that probably would have made the cause more obvious.

Digging around in the configuration files & registry also couldn't identify anywhere that was caching a name, but I must have missed it. It would be a bonus if the repair tool could redo whatever was caching the credentials.

But hopefully anyone running into it in the future will find this via Google ...

Thanks for a great embeddable web server. After fighting with IIS Express for a year or so this is proving much more pleasant!

Wow -- thanks for the amazingly fast response!

Using the new build it reports the error:
LookupAccountName buffer length detection failed for user "iewinxpzz\ieuser". Win32 Error: 1332

Which definitely helps with diagnosis.

Interesting the machine name isn't iewinxpzz ... nor was it when the software was installed.

Initially the machine was iewinxp, it was then changed to iewinxpzz and then again to something else. Not sure why the iewinxpzz value is sticking, changing it repeatedly again doesn't change the result. Seems to survive an install/uninstall cycle too .. and I can't find that string in the registry anywhere - no idea where it is still coming from!

Message was deleted by a Moderator.