|
Wow i must be the first person to try quadrant!
I've installedthe OsloMay CTP, on a machine running Windows 7 RC, and SQL 2008 Express with Advanced Services Sp1,
the installation went ok,
however when i FIRST ran quadrant, i got
"Quadrant requires a user with sysadmin privaleges"
did a reboot:
now i get after a long delay
"
Unable to connect to Quadrant Repository: A network-related or instance-specfic error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Shared Memory Provider, error: 40 - Could not open a connection to SQL Server)
"
the instance IS set for remote connections. I've turned my firewall off (McAfee)..
any suggestions on where to look to figure this out???
| | Adam E | OK I've figured it out, but it may be a bug:
I have office business contact manager installed:
i had DISABLED that instance of sql server. it was also the first SQL server instance on my pc (it came with it)..
seems thatQuadrant is looking, not for the "default" instance, but for the FIRST instance.
unfortunately, Quadrant's attached itself to this instance...
is there anyway of changing SQL Server instance ID/ or indexes?
Adam
- Marked As Answer byAdam E Wednesday, May 27, 2009 9:56 AM
-
| | Adam E | Hello,
The error is due to a SQL Server login error. I guess you may be trying to log into SQL Server with OS integrated validation. When you installed Oslo CTP, you did it as Admin (i.e. granted Oslo Setup admin rights through UAC window).
It turns out that now you are trying to use Quadrant with a non-admin account, and when it tries to load and queries repository for viewer's config, your user is not allowed to browse Quadrant's repository because it is not the user that set up that database.
Solution: Either you grant your OS user access to repository DB or you execute Quadrant with admin privileges (right click on Quadrant's icon, Run as Admin..)
Hope my guesses were correct and this helped you.
Regards,
M.
Happy Oslo Team member! | | Miguel Llopis | Hello Adeze, This issue and workaroundis documented in the ReadMe (under "C:\Program Files\Microsoft Oslo\1.0"):
Microsoft code name "Quadrant" requires SQL SysAdmin server role privileges
"Quadrant" will surface an error and exit if the current user does not have SysAdmin server role privileges under the running instance of SQL Server. If you installed SQL yourself on your machine (versus an administrator or other form of installation), typically you are included in the SQL SysAdmin server role using the installation option.
Workaround: Add the current user’s credentials to the SQL SysAdmin server role and restart "Quadrant".
Also, checkout known issues section in the release notes: http://msdn.microsoft.com/en-us/oslo/releasenotes.aspx#whatsnew
Thanks,
Stephane - Proposed As Answer bysnyombaMSFTWednesday, May 27, 2009 5:59 AM
-
| | snyomba | i've tried running Quadrant as admin (run as admin..),
i've also made sure that my sql express IS the default instance (when i enter my pc name in SQLMS to connect, it comes up with the correct instance).
The repository is all there.
after i've uninstalled, reinstalled oslo and sql express instances ALL DAY...
i'm still getting
"Unable to connect to Quadrant repository:
... (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
"
I've been trying all the resolutions to 'solving SQL Connectivity'...
i notice that when i run Quadrant--
it always comes up with 'Quadrant didn't shut down properly, do you want to reset the quadrant database?" message.. then itsresource usage is around 5-6mb and remains fairly static..
i've monitored SQL Server, and no connections seem to be being made.
if its simply a matter of turning UAC off.. i can try that..
i've made sure my account is in 'sysadmin' role too.
i've tried shared memory/np/tcp combinations to sql server...
i've tried .udl files.. but since i don't knowexactlywhat the connection string Quadrant has hardcoded.. its hard to tell.
there must be a way of knowing this??
I'm going nuts...
btw my pc name is called "ADAM-PC"... the hyphen couldn't be causing a problem????
thanks
Adam
| | Adam E | OK I've figured it out, but it may be a bug:
I have office business contact manager installed:
i had DISABLED that instance of sql server. it was also the first SQL server instance on my pc (it came with it)..
seems thatQuadrant is looking, not for the "default" instance, but for the FIRST instance.
unfortunately, Quadrant's attached itself to this instance...
is there anyway of changing SQL Server instance ID/ or indexes?
Adam
- Marked As Answer byAdam E Wednesday, May 27, 2009 9:56 AM
-
| | Adam E | Hello,
For this release there is no way to manually specify the SQL Server instance that Quadrant attaches to.
Thanks,
David | | David L Zhang | David,
After my Quadrant (May 09 CTP) failed to connect to the Repository, I clicked View... Sessions... and then on the first entry, I edited the Server field, which was previously ".", to read SYS020\SQLEXPRESS (SYS020 is my machine's name, but localhost should have worked too), and it successfully connected to the Repository.
-Matthew | | Matthew Wilson _diakopter_ | Diakopter, That'll work, but note that there's the section on: The "Oslo" Repository must deployed to the default instance on the target machine in order to view "Quadrant" Samples
in http://msdn.microsoft.com/en-us/oslo/releasenotes.aspx#installingon the release notes. There are limitations to this approach for the time being, and some parts of the sample documentation rely on the default instance being in use. Basically, when using the samples, the quadrant configuration relies on the instance being the default in order to associate correctly. It won't cause any major errors, but it will prevent quadrant from working as expected. Additionally, what David mentioned was still true, however, David is talking about the Quadrant configuration database, that is created per-user of Quadrant, which cannot be redirected to another location, yet. Hope that clarifies what David was talking about. Andrew | | Andrew Pilley | Hi Matthew,
I am having the same problem. Setup went normally, the Repository database was created on the default SQL instance, but now Quadrant can't connect. I am using windows authentication and both my personal logon and the SQL logon account have sysadmin role on the SQL Server.
In your post you mention that you used View... Sessions... to change the SQL Server reference, but you don't say where these selections are found.
What program/utility do I need to run to access these menu choices?
Thanks,
Bob | | Bob Sculley | Hi Bob,
View -> Sessions are menu options available in Quadrant. I don't think these menu options are ever disabled.
Thanks,
Rohit
This posting is provided "AS IS" with no warranties, and confers no rights. - Edited byRohit Patkar - MSFT Sunday, June 14, 2009 1:09 AMupdated to more appropriate statement
-
| | Rohit Patkar - MSFT | Hello Rohit,
I'm having the same problem as Bob. Quadrant does not come up far enough to see those menu items. Is there another way?
Thank you.
KS. - Proposed As Answer byK Sampat Tuesday, July 21, 2009 10:55 PM
-
| | K Sampat | I got it working.
Quadrant requires an SQL server on the local machine to start-up apparently.
Once I installed a local server, Quadrant started up. After that, I was able to connect to my remote sql server.
I've played with Oslo for a little bit now. It is clearly CTP quality - could not get LoadUml to work at all.
For now, my modeling needs are met by Visio connected to SQL. Will relook at Oslo as it matures further. | | K Sampat | 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 theusing of roaming profiles (???).
Anyhow it seems that Quadrantwas copying theQuadrant.mdf and Quadrant.ldf filesfrom 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.
Cheers, J | | jacsparkie | 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 theusing of roaming profiles (???).
Anyhow it seems that Quadrantwas copying theQuadrant.mdf and Quadrant.ldf filesfrom 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.
Cheers, J
Hey Jacsparkie, This issue is commonly caused because the SQL Server doesn't have write permissions to your profile. In this case, i'm assuming that SQL Server is running as the Local System account, or some other non-domain account. This means it won't have write access to your profile on the server, since its account won't be your user account, and not trusted by the server to access your files. This does mean that Quadrant's configuration won't follow you around if you move between systems, which will certainly be inconvenient. The workaround you've used will certainly work. I don't know ofa way that you'd be able to get SQL Server to useyour server-side profile with any reliability, but I'll raise it with the team to ensure that this situation is considered and catered for (or at least, documented). I wouldn't recommend trying to run an instance of SQL Server as your local account, as the file locking would certainly be a problem, as would network latency. Hope this clarifies the situation you had. Andrew Pilley | | Andrew Pilley |
|
index > Microsoft Codename 'Oslo' > Quadrant can't start