Unable to run FB on a Longhorn server

Hi,

we upgradet our server to Windows Longhorn (build 6001) and are unable to run FinalBuilder (5.0.0.53).

Windows shows up an error message that the FinalBuilder Console stopped working correctly and closes the process.
I’m sorry that I can’t provide more detailed information about this error but there are no log files or detailed error messages.

ciao,
pat

FinalBuilder is not yet supported on Longhorn. We not yet done any testing on Longhorn, that will be done when it reaches release candidate status.


My colleague reported the above error and I found out the following. Perhaps the error is not related to Longhorn (64 bit) and you can provide a work around for us?If I run FinalBuilder 5 as “Evaluation Version”, it runs without problems. Only if I release the software with our license key, the EXE crashes.I attached the LOG of Microsoft’s Process Monitor (http://www.microsoft.com/technet/sysinternals/processesandthreads/processmonitor.mspx) in CSV format and it reports a “BUFFER OVERFLOW” when trying to access the registry key of the license (line 1118).Logfile.zip (20.363 KB)

I have seen this problem before with other license validation schemes. You need to exempt FinalBuilder5.exe and ActionStudio.exe from data execution prevention (DEP). On Vista, go to Computer… Properties… Advanced system settings… Performance Settings… Data Execution Prevention tab… and add the two EXEs to the exception list. (You should find the DEP tab in a similar place on Longhorn, XP SP2, and WinServer2K3.)

I suspect that the license key is used to somehow generate code which is then executed. The software should clear the NX bit so that DEP doesn’t teardown the process when the product is licensed.

Hi

James is correct, the problem is caused by the licensing software we used, the work around is to exempt finalbuilder from DEP. We are waiting on the protection software vendor to correct this problem (we reported it some time ago). Unfortunately, every other protection system we have looked at has a similar problem, or doesn’ work at all on Vista/Longhorn.