I install quadrant and everything is fine. I am installing the repository on SQL Server 2008 on another machine. The database gets created successfully by the install process. I can see it and connect to it through the vs server explorer. But I cannot run Quadrant. I do not have SQL Server Installed at all on the local machine.

Well, thanks for all the suggestions. I still can't make it work unless there is repository on the local machine. The command-line argument seems to work (i.e. it seems like it's trying to use it), but it still times out. I'm just going to embrace themystery and move on. I also just noticed the comments in the readme about x64 clients and x32 sql server. This may be my issue, because I'm running Vista x64 and my server is 32bit server 2008. In any case, I'll assume all of this will get cleared up in the real product.

~Bill

Hi,

Working with a remote SQL server instance should not be a problem when using Quadrant. However, connecting to yourdatabase with sysadmin privileges is required in order to run Quadrant properly... Have you made sure you areconnecting to this remote SQL server instance with sysadmin privileges?

For more info on this and other issues, please take a look at the Release Notes.

Hope this helps,
M.

That doesn't seem to be the problem. I am in the sysadmin group on the remote database. The problem seems to be that Quadrant is trying to find a local database. There is a fairly long timeout when I start Quadrant, followed bythe messageabout Named Pipes possibly not being enabled on the database (note this happens when I run Quadrant, not when I install the Repository).Named pipes areenabled on the remote database. I've done this on two completely different networks now, at home and at work and the result is the same. As far as I can tell, there is no configuration anywhere that is even telling Quadrant to try to use the remote server. The setup obviously works, because the Repository instance is being created on the remote server (and deleted if I uninstall). How exactly does Quadrant know which database to use for it's initial repository? I dont see any .exe.config and there do not seem to be any command line arguments to Quadrant.exe. Is it possible that you must have a local database for startup and then you can connect to a remote one?

the Release Notes mentions the following as a Software Requirement for Running Quadrant locally:

Software Requirements

• Windows Installer 4.5
  • To run setup, Windows Installer 4.5 is required. If you do not have it installed, setup will not continue.
  • Note that a system reboot is required by Windows Installer. After installing, launch the code name "Oslo" setup program again.
• .NET Framework 3.5 SP1
  • .NET Framework 3.5 is required for "Oslo" setup to work properly. During setup, you will be prompted to install .NET Framework 3.5 SP1 if it is not installed.
• SQL Server 2008 Express or higher SKU.
• Visual Studio 2008 Standard or higher SKU (optional)
  • Visual Studio is not required for "Oslo" but for full functionality with Visual Studio and "M" integration, users must have Standard or higher SKU.

SQL Server 2008 Express (or higher SKU) needs to be installed on the Local Machine running Quadrant

---

VSS

Hello

Quadrant does have a command line argument BootConnectionString. From the command line pass the connection string for the remote server you want to connect to:

Quadrant.exe "/BootConnectionString=Connection Timeout=300;Data Source={SERVER NAME HERE};Initial Catalog={REPOSITORY DB NAME HERE};Integrated Security=True"

I hope this helps

Well, thanks for all the suggestions. I still can't make it work unless there is repository on the local machine. The command-line argument seems to work (i.e. it seems like it's trying to use it), but it still times out. I'm just going to embrace themystery and move on. I also just noticed the comments in the readme about x64 clients and x32 sql server. This may be my issue, because I'm running Vista x64 and my server is 32bit server 2008. In any case, I'll assume all of this will get cleared up in the real product.

~Bill

I posted the following reply on another thread, it might be of use:

I had slightly different error - Quadrant couldn't open the database file \\<server_name>\Profile$\<user_name>\Application Data\Microsoft\Quadrant\Quadrant.3.0.1803.10.<Domain Name>.<user_name>.mdf". I think this has to do with the using of roaming profiles (???).

Anyhow it seems that Quadrant was copying the Quadrant.mdf and Quadrant.ldf files from C:\Program Files\Microsoft Oslo\1.0\bin to the above location, so I created a new database via management studio called Quadrant.3.0.1803.10.<Domain Name>.<user_name>, then stopped the server and replaced the newly created mdf/ldf files (default SQL server 2008 location, ie. C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA) with the ones from C:\Program Files\Microsoft Oslo\1.0\bin. I also needed to add my AD login as a user to the Quadrant database - with db_accessadmin/db_owner/Repository... roles.