InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comTue, 21 May 2013 20:30:18 GMT20http://www.sqlservercentral.com/Forums/Topic709066-5-1.aspxGranting "Full Control" on the folders, solved the issue.Thu, 07 May 2009 10:57:24 GMTsivaprasadhttp://www.sqlservercentral.com/Forums/Topic709066-5-1.aspx[font="Verdana"][size="2"]Yes, it looks like the new service account does not have access to the folders specified. Try giving the new service account full access to the folders and see what happens. I am assuming that giving full permissions will resolve your issue.[/size][/font]Mon, 04 May 2009 05:28:20 GMThemanth.damecharlahttp://www.sqlservercentral.com/Forums/Topic709066-5-1.aspxWhile replacing the SQL Server Service account with new Windows Domain account getting the below error message for the User Database files which are not on the default database path. It seems to be of the new service account does not have privileges on this folders.2009-05-03 20:09:00.88 spid15 Starting up database 'UserDB_UAT'. 02009-05-03 20:09:00.88 spid15 udopen: Operating system error 5(error not found) during the creation/opening of physical device D:\UserDB_UAT\UserDB_UAT_Data.Mdf. 02009-05-03 20:09:00.88 spid15 FCB::Open failed: Could not open device D:\UserDB_UAT\UserDB_UAT_Data.Mdf for virtual device number (VDN) 1. 02009-05-03 20:09:00.88 spid15 Device activation error. The physical file name 'D:\UserDB_UAT\UserDB_UAT_Data.Mdf' may be incorrect. 02009-05-03 20:09:00.88 spid15 udopen: Operating system error 5(error not found) during the creation/opening of physical device D:\UserDB_UAT\UserDB_UAT_Log.Ldf. 02009-05-03 20:09:00.88 spid15 FCB::Open failed: Could not open device D:\UserDB_UAT\UserDB_UAT_Log.Ldf for virtual device number (VDN) 2. 02009-05-03 20:09:00.88 spid15 Device activation error. The physical file name 'D:\UserDB_UAT\UserDB_UAT_Log.Ldf' may be incorrect. 02009-05-03 20:09:00.88 spid15 Device activation error. The physical file name 'D:\UserDB_UAT\UserDB_UAT_Log.Ldf' may be incorrect.Sun, 03 May 2009 11:08:14 GMTsivaprasad