Installation and deployment Questions on installation, system configuration and deployment to the live server.
Version 5.x > Installation and deployment > New website: error because of SQL schema View modes: 
User avatar
Certified Developer v7
Certified  Developer v7
emanuele.firmani-aduno-gruppe - 10/20/2010 6:50:17 AM
   
New website: error because of SQL schema
I have a web site running Kentico 5.0 and everything is fine.
I tried to install a new one using Kentico 5.5, but I'm experiencing some issues.
I always use the ApplicationPool (domain\apppooluser) identity to create new websites. The given user is member of the group xxxAdminDB and the group is granted as db_owner in the database where I installed Kentico.

1 - Kentico 5.5 adds the user to the DB users: why does it so? I tried to delete it, but it add it each time I try to create a new website.

2 - Kentico adds the user and set its default schema to 'domain\apppooluser', not dbo. This way it gets an exception because the SQL statement is not well formet (you should alway encapsulate the schema between [...])

I was able to solve it by changing:
- the default schema of the user domain\apppooluser in the DB Security configuration
- the schema of all tables, procedures and views

I'm still not able to remove the user from the Security/Users because Kentico readd it.


Hope I was clear enough.
Thanks for your support
Regards
Emanuele Firmani

User avatar
Kentico Developer
Kentico Developer
kentico_helenag - 11/3/2010 3:12:58 PM
   
RE:New website: error because of SQL schema
Hello,


do you use the Windows authentication in DB installer? Can you use a SQL Server account in Step 1 of Database installer?


Best regards,
Helena Grulichova

User avatar
Certified Developer v7
Certified  Developer v7
emanuele.firmani-aduno-gruppe - 11/4/2010 1:35:17 AM
   
RE:New website: error because of SQL schema
Yes I use the Windows authentication in DB installer (application pool identity).
I'm sorry, but for security reasons, SQLServer user are not allowed in my company, so I cannot use it.

Thanks
Regards
Emanuele Firmani

User avatar
Kentico Developer
Kentico Developer
kentico_helenag - 11/8/2010 7:01:31 AM
   
RE:New website: error because of SQL schema
Hello,


There should be the "sa" user in your database by default. Is it a problem to use this user?


Best regards,
Helena Grulichova

User avatar
Certified Developer v7
Certified  Developer v7
emanuele.firmani-aduno-gruppe - 11/8/2010 7:04:03 AM
   
RE:New website: error because of SQL schema
Sorry, I'm not allowed.
Have you been able to reproduce my issue, by using the Application pool identity?

User avatar
Kentico Developer
Kentico Developer
kentico_helenag - 11/18/2010 6:33:23 AM
   
RE:New website: error because of SQL schema
Hello,


we were not able to reproduce the issue. The owner was "dbo".

1. Did you create the database by yourself or was it created by install process?

2. My steps were:
I assigned the application pool to domain user.
I created the domain user login in database which is granted with dbcreator role (permission).
I installed the database by install process (/CMSInstall/install.aspx).
The schema was dbo.


Did you make different steps?


Best regards,
Helena Grulichova

User avatar
Certified Developer v7
Certified  Developer v7
emanuele.firmani-aduno-gruppe - 11/18/2010 6:41:19 AM
   
RE:New website: error because of SQL schema
1. The database was created by our DB admin (the default properties are not OK in our environment, we need to specify UNC folders, etc).

2. We assigned the AppPool to the Windows user
We assigned the Windows user to an AD group.
We granted the AD group as DB owner for the given DB.
We installed Kentico attaching it to the existing DB.

Thanks
Regards
Emanuele Firmani

User avatar
Kentico Developer
Kentico Developer
kentico_helenag - 11/18/2010 7:22:05 AM
   
RE:New website: error because of SQL schema
Hello,


could you please try to create a new database by the standard install process (not attach it to an existing database)? Could you please check the DB user once again? It seems it could be a SQL server related issue as we were not able to reproduce it.


Best regards,
Helena Grulichova