Hi,

After much turmoil I've got Windows Vista Ultimate RTM installed on my machine. Unfortunately the LLBLGen installer craps out mid install with

"The installer has encountered blah blah. The error code is 2869."

Theres nothing of any help in the event log about it.

Here's what Otis has said about this in a previous thread:

Otis wrote:

Running the installer on vista rc1 gives an error at the end of the install, error 2869. Looking it up via google it's something cryptic with error dialog which isnt an error dialog (?). I've the feeling it's something with Vista, dunno. Anyone else had this as well?

edit: hmm, sounds like a vista prob: http://forums.asp.net/1388938/ShowThread.aspx

edit2: solution: If you're going to install the demo on Microsoft Vista RC1 or earlier, please follow these steps, as you'll otherwise run into the 2869 error: 1. Create a new .bat file in the same folder as the one the LLBLGenPro20.msi file is in. 2. Add the following text 'msiexec /i LLBLGenPro20.msi' and save the file. 3. Right click the .bat file and select 'Run as Administrator'.

I've no idea why this happens, probably when the installer tries to create the registry keys for VS.NET to find back the runtime libs...

See this link for the whole thread:

http://www.llblgen.com/TinyForum/Messages.aspx?ThreadID=7477#41448

Alrighty I'll give it a go tonight. Cheers

This worked for me. Might be a good idea to patch this so it goes automatically for vista in the next build.

JuanV wrote:

This worked for me. Might be a good idea to patch this so it goes automatically for vista in the next build.

It's part of the windows installer system we're using at the moment and part of the fact that we create some registry keys for vs.net 2005, so visual studio can find the runtime libraries and displays them in the list of dlls when you add a reference in vs.net. This registry addition is what causes the problems mostly, as on vista you're not allowed to do so unles UAC is disabled. Also, sometimes the user is administrator and has the rights to create regkeys but still this doesn't work because the installer is started from explorer and not from the command line.

It's not that assemblies who are in the GAC are shown in the list of assemblies to reference, the locations are obtained from the folders defined in the registry for vs.net 2003/5. Great huh, when teams from the same company work together so closely .

Anyway, for v2.5 we'll use NSIS as installer system and hopefully this will overcome this issue.

Thanks for the info, this helped me out. I am getting back into a project that's still on 2.0 and ran into this issue. For posterity, you may need to add an absolute path to the bat file since msiexec runs from windows\system32 and will not be able to find the msi without a full path (at least that's what I ran into). So in my case I did this:

msiexec /i e:\download\LLBLGenPro20.msi

Thanks!