There have been a number of fixes on this are and I am unable to reproduce it.
I have been running the following batch file successfully for over 40 minutes:
rd /Q c:\temp\s1
xcopy /SYQ c:\temp\OpenDS-1.0.0 c:\temp\s1
CALL C:\temp\s1\setup --cli -p 389 -a -w s -n --enableWindowsService
if not %errorlevel% == 0 echo ERROR IN SETUP
CALL C:\temp\s1\bat\status.bat -w s -n
CALL c:\temp\s1\uninstall --cli -a -n -f -q
if not %errorlevel% == 0 echo ERROR IN UNINSTALL
exit /B 0
Concerning the functional tests I have not found a single place where the server
is properly uninstalled (calling the uninstall script). Since the server is not
properly uninstalled (I have seen some code in the functional tests that
basically stops the server and then removes the installation files which is NOT
enough). If the server is not properly uninstalled and the service is still
defined chances are that we encounter issues and we cannot do much about it. We
already provide a manner to clean up the service in an improperly uninstalled
server (using windows-service command line) so this scenario is already covered
for the user. However as far as I can see the functional tests do not clean up
things properly (I am not expert on this area so maybe I am missing something).
If someone does not come with a more precise scenario it is very difficult to
try to figure out if there is really an issue and to solve it.