Hi! This issue has been fixed now and will be in the next public release of the manager. The process of finding and running the workflow foundation scripts is now: 1. Look for the files in %windir%\Microsoft.NET\Framework\v3.0\Windows Workflow Foundation\SQL\EN 2. Look for the files in C:\WINDOWS\Microsoft.NET\Framework\v3.0\Windows Workflow Foundation\SQL\EN 3. Log an error to the logfile, but let the installation continue I have tried installing different language-versions of .NET FW 3, but the scripts always end up in the \SQL\EN\ folder, let me know if you have found something that contradicts this. If an unexpected error still occurs; catch it, log it and continue the installation. To work around this problem with the current version of the manager, make sure that the files SqlPersistenceService_Logic.sql and SqlPersistenceService_Schema.sql are located in the C:\WINDOWS\Microsoft.NET\Framework\v3.0\Windows Workflow Foundation\SQL\EN folder and make sure that they are not locked by some other process. Also try to give EVERYONE read access to the files should the problem still occur.

I experienced the same problem during the install of RC2 even though the files were located in C:\WINDOWS\Microsoft.NET\Framework\v3.0\Windows Workflow Foundation\SQL\EN. I also granted Everyone FULL access to the .sql files in question, but that didn't help either. Finally I downloaded RC2 as an offline package and ran the installer again, and this time it worked! I'm not sure why the offline package would work better (some security related feature maybe?), but hey, it worked for me anyway. =)