Monday, February 23, 2009

Community Server shared membership

Step to configure Community Server with an existing membership database.

Create Community Server Database manually

Step 1.) Add a new connection string in CS web.config that points to your sites membership database.

Step 2.)Update your providers
(Membership, Profile, and/or Role) to use the new connection string

Step 3.) Change the CS application name to your sites application name.
The applicationName property exists in Membership, Profile and Role Provider tags.
AND in the database cs_SiteSettings.ApplicationName.


Step 3.)Add CS stored procs to you mainsites database.
* cs_Membership_GetUsersByName
* cs_Membership_IsUserNameTaken
* cs_Membership_RenameUser
* cs_Membership_ChangePasswordAnswer
* cs_Membership_ValidatePasswordAnswer
* cs_Profile_GetPropertiesForUsers
* cs_Role_Get
* cs_Roles_CreateRole
* cs_Roles_UpdateRole
* cs_Roles_GetRoleIdsForUsers
* cs_Roles_Get

Step 4.)Copy CS roles to you mainsites aspnet_Roles table.
make sure to enable identity insert

Step 5.)Copy CS Users to you mainsites aspnet_Users table.
make sure to enable identity insert

Step 6.)Copy CS User to Roles mapping to you mainsites aspnet_UsersInRoles table.
make sure to enable identity insert

System.Runtime.InteropServices.COMException

I received a pop up error with the message System.Runtime.InteropServices.COMException. This happened when I was trying to reload a project that somehow got unloaded.

Resolution:
  1. Once the solution opens, right-click on the unavailable project and select Edit project_file_name.vbproj.
  2. Scroll to the bottom of the page, and delete the ProjectExtensions section.
  3. Save the page.
  4. Right-click again on the unavailable project, and select Reload Project.
  5. Your project should now be available and you should be able to see all your project files.

SQL Authentication login error

I was trying to connect to Sql Server Management Studio today using SQL Server Authentication and received a Microsoft SQL Server, Error: 18452. "The user is not associated with a trusted SQL Server connection."

PROBLEM: Cannot login with any account using SQL Server Authication because the Server Authentication mode does not allow it. (We need to change it so SQL Server Authentication is allowed).

SOLUTION:
Step 1.) Log into Management Studio using Windows Authentication
Step 2.) Right Click on the Server and select Properties
Step 3.) Select the Security page from the left side navigation.
Step 4.) Select SQL Server and Windows Authentication mode.
Step 5.) Press OK
Step 6.) Right click on the Server and select Restart

You should now be able to login with the account that requires SQL Server authentication.

Hope this helps.

Reference:
http://chkiran.wordpress.com/2008/06/20/sql-server-authentication-not-working/

Error trying to create a Database Diagram in Sql Server 2005

Today I tried to create a Database Diagram in SQL Server 2005 and received a pop up error message:

Sql 2005 Database diagram support objects cannot be installed because this database does not have a valid owner

SOLUTION:
EXEC sp_dbcmptlevel 'yourDB', '90';
go
ALTER AUTHORIZATION ON DATABASE::yourDB TO "yourLogin"
go
use [yourDB]
go
EXECUTE AS USER = N'dbo' REVERT
go

Thank you Shahed for posting the solution on
http://geekswithblogs.net/shahed/archive/2007/11/19/116940.aspx