jonpfl


All,

When I create a new project and try to use the WSAT security tab, I get the following :

There is a problem with your selected data store. This can be caused by an invalid server name or credentials, or by insufficient permission. It can also be caused by the role manager feature not being enabled. Click the button below to be redirected to a page where you can choose a new data store.

The following message may help in diagnosing the problem: Unable to connect to SQL Server database.

I am using VS2005 beta2 with a local copy of SQL Server Express.

I am new to all of this so a little help would be great

Thx
jonpfl



Re: Web Site Admin Tool problem in VS2005

mountvaleste


I got EXACTLY the same problem.

@ jonpfl: did you find out how to fix that probelm

pls help

cheers





Re: Web Site Admin Tool problem in VS2005

jonpfl

Nope, never did figure it out since I had to work on something else and have not had a chance to go back and look into it.

If you figure it out, please let me know : jonp@NOSPAMtampabay.rr.com

Thx
jonpfl





Re: Web Site Admin Tool problem in VS2005

another_noob

I also have the exact same problem. Did any of you manage to solve it




Re: Web Site Admin Tool problem in VS2005

another_noob

I just solved the problem. If you still haven't, feel free to contact me.




Re: Web Site Admin Tool problem in VS2005

doph

Please tell how you fixed the problem.

feel free to drop a copy to Sasha _AT_ bolotnov.info




Re: Web Site Admin Tool problem in VS2005

Stefan_MS

Also - can you try this on a clean machine with an install of the RTM versions of VS 2005 + Sql Server Express

With a new install you should be able to create a file-based website where the services database is automatically created for you.  If things still don't work on the RTM bits:

1.  Create a page in your app with one line of code:  Membership.CreateUser("foo","baz")

2.  Run the page

Then post the stack dump and the error message here.

Thanks!




Re: Web Site Admin Tool problem in VS2005

JacobEgholm

I had the same error. It was caused by this tag i web.config

<identity impersonate="true" userName="xxxxxx" password="xxxxx" />

Remove it or change the username and password to a valid user.






Re: Web Site Admin Tool problem in VS2005

Ganesh Rangarao

Could you please share with me how you solved his issue

when I click the "Security Tab" I get the following error:

There is a problem with your selected data store. This can be caused by an invalid server name or credentials, or by insufficient permission. It can also be caused by the role manager feature not being enabled. Click the button below to be redirected to a page where you can choose a new data store.

Thanks for looking into it.






Re: Web Site Admin Tool problem in VS2005

Ben Chambers

i am responding to you regarding the security tab in web site admin tool. please could you point me to the solution



Re: Web Site Admin Tool problem in VS2005

joeydj

hi all,

this one might interest you

start>run>control>administrative tools>internet information services

in the IIS rightclick default website>click on properties> click on asp.net

in the asp.net click version2> then click edit global configuration.

take a look at the connection string property for LOCALSQLSERVEr

its pointing to (.)\SQLEXPRESS

regards

joey






Re: Web Site Admin Tool problem in VS2005

Hussain Noordin

Ganesh ,

did you ever resolve this one






Re: Web Site Admin Tool problem in VS2005

Ahmed Abbas

This issue sometimes relates to SQL Express not having permissions to access its files on the local machine. You probably accidently changed the permissions on the folders by inheritence.

Goto:

Start->Control Panel->Administrative Tools->Event Viewer

In "Event Viewer (Local)" on the left select "Application". You will then find some errors caused by "MSSQL$SQLEXPRESS" service. The event code (Error code) for these errors are 17204 and 17207. Open these up and they should look something like this:

17207:

FCB::Open: Operating system error 5(Access is denied.) occurred while creating or opening file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf'. Diagnose and correct the operating system error, and retry the operation.

17207:

FCB::Open failed: Could not open file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf for file number 2. OS error: 5(Access is denied.).

Take note of the folder in this example "C:\Program Files\Microsoft SQL Server". Set permissions on this folder and all its contents to be accessable by the "NT AUTHORITY\NetworkService" or "NETWORK SERVICE" user on your machine. Change permissions at your own risk.

Alternatively you can try change the user that the SQL Server services run on to the same as your login but not sure if that will work.






Re: Web Site Admin Tool problem in VS2005

alienseiya

Hi

I've been trying to solve the "There is a problem with your selected data store" error message with no success. My laptop's got Windows XP Home edition and I have enabled the IIS thing (grabbed some files off Win2000 Professional). I got as well VB2005 Express Edition, SQL 2005 Express Edition and of course Web Developer 2005 Express Edition.

In your post, you suggested that you have solved this problem... Could I ask you how please

Many thanks

Christian





Re: Web Site Admin Tool problem in VS2005

ObieOne

I just resolved this issue for my local machine.

In the web.config file I changed / added the following:

<connectionStrings>

<remove name="LocalSqlServer" />

<add name="LocalSqlServer" connectionString="Integrated Security=SSPI;Data Source=YOURMACHINENAME ;Initial Catalog=aspnetdb;" providerName="System.Data.SqlClient" />

</connectionStrings>

The problem was the Data Source wich was pointing to .SQLEXPRESS. I just typed in the machine name and everything is ok.

Please mention that SSPI is integrated security. If you deside to deploy your application you migth want to change this to some anonimous webuser account.

Extra notice;

If you would like to use the admin wizard on an external machine eg. a server make sure u keep the instance at LocalSqlServer.

The wizard appears to be using this name in hard code.

Arno