Showing posts with label vwd. Show all posts
Showing posts with label vwd. Show all posts

Sunday, February 12, 2012

Cant connect to membership provider db

I've started developing an ASP.net 2.0 app with VWD Express.

The default membership provider db of SQL Server 5005 Express is not installed on my host servers. So my workaround has been to use a Full blown SQL Server 2005 DB as a custom membership provider declared in web.config.

This works fine on the production server. However, when i try to login from my development app I get Exception # 40 can't connect to SQL server membership provider.. Moreover, my app configuration confirms there is problems connecting to this server in my development environment.


How can I solve this and bring my development app up & running again?

many thanks

If you have access to your Production SQL Server from your development environment, the problem is probably due to your connection string.


For my development, I use SQL Express on my local development box and SQL Server for production. There are two things that you have to do. Keeps separate scripts for changes to the database (from development to production). In addition, a separate web.config for production and development to hold your connection strings.

Friday, February 10, 2012

Cant connect to any database not owned by servername\ASPNET

I'm developing an intranet application and am using the Express versions of VWD and SQL Server 2005 for initial development before obtaining full licensed versions.

Database connections work fine when testing from within VWD but when testing from browser, unless the database owner is the IIS servername\ASPNET, there are various errors depending on the specific connection settings, i.e.

Login failed for user ''. The user is not associated with a trusted SQL Server connection.-

Receive this error when a GridView is connected to a remote SSE db.

--

SELECT permission denied on object 'Table_1', database 'TEST', schema 'dbo'.

Receive this error when GridView is connected to local SSE db not owned by servername\ASPNET.

--

Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.

This happens when using any control that is connected to SSE db created in VWD and stored in App_Data folder (owner is the user logon name)

--

Any help or ideas would be appreciated. I want to have all local data stored in App_Data folder.

Thank you.

You need to set SQL Server to use both Windows and SQL Server, that is covered below. Post again if you still need help.

http://msdn2.microsoft.com/en-us/library/ms188670.aspx