Installer does not create permission for user in database
Peter Wass 11 years ago • updated by anonymous 7 years ago • 5
The Service Account user is not created in the Database and therefore the service cannot start. I would expect that the user would be created if the database is being created.
Customer support service by UserEcho
Moved to v4.1 for consideration as this could be problematic and all of the ramifications should be thought out.
This may be possible with CREATE LOGIN and CREATE USER (see http://msdn.microsoft.com/en-us/library/ms173463.aspx).
Although we should discuss whether this is actually desirable.
Should be examined in v4.1.1 for LITE; currently a new database will need to be given permissions manually.
Definitely believe it should be option 1 as you have indicated below. This is consistent with the FIM model, which sets an expectation we can follow.
Agreed (SQL auth in SQL is supposed to be only there for legacy support - surprised it is still supported).
The installer now creates the login (for the instance) and the user (for the database) if they are not already there. Permission is granted to the Identity Broker database (db_owner).