Re: Profile Problem
- From: "Ken Cox [Microsoft MVP]" <BANSPAMkjopc@xxxxxxxxxxxxxxxxx>
- Date: Sat, 16 Sep 2006 10:08:47 -0400
If you're using Access, you need the Access provider.
There's code here for that:
http://download.microsoft.com/download/5/5/b/55bc291f-4316-4fd7-9269-dbf9edbaada8/SampleAccessProviders.vsi
Ken
Microsoft MVP [ASP.NET]
"shapper" <mdmoura@xxxxxxxxx> wrote in message
news:1158357978.511755.256260@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello,
I added some profile properties to my web.config file.
Then I started to use my profile properties in a page class and I get
an error:
An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under the default settings SQL Server does not allow remote
connections. (provider: SQL Network Interfaces, error: 26 - Error
Locating Server/Instance Specified)
Description: An unhandled exception occurred during the execution of
the current web request. Please review the stack trace for more
information about the error and where it originated in the code.
SQLExpress database file auto-creation error:
The connection string specifies a local Sql Server Express instance
using a database location within the applications App_Data directory.
The provider attempted to automatically create the application services
database because the provider determined that the database does not
exist. The following configuration requirements are necessary to
successfully check for existence of the application services database
and automatically create the application services database:
1. If the applications App_Data directory does not already exist,
the web server account must have read and write access to the
applications directory. This is necessary because the web server
account will automatically create the App_Data directory if it does not
already exist.
2. If the applications App_Data directory already exists, the web
server account only requires read and write access to the applications
App_Data directory. This is necessary because the web server account
will attempt to verify that the Sql Server Express database already
exists within the applications App_Data directory. Revoking read access
on the App_Data directory from the web server account will prevent the
provider from correctly determining if the Sql Server Express database
already exists. This will cause an error when the provider attempts to
create a duplicate of an already existing database. Write access is
required because the web server accounts credentials are used when
creating the new database.
3. Sql Server Express must be installed on the machine.
4. The process identity for the web server account must have a local
user profile. See the readme document for details on how to create a
local user profile for both machine and domain accounts.
I am using a Microsoft Access database and Asp.Net 2.0.
I think the problem is when the system tryies to create the necessary
tables, in my Microsoft Access database, for profile.
Could you tell me how to solve this?
Thanks,
Miguel
.
- References:
- Profile Problem
- From: shapper
- Profile Problem
- Prev by Date: Re: Leaf Node in SiteMapPath
- Next by Date: Re: Left and Right hand splitting and resizing
- Previous by thread: Re: Profile Problem
- Next by thread: Event within an Event Issue
- Index(es):
Relevant Pages
|
