Please note that the Firebird server is not required to be installed on the web server at all.
If restarting IIS doesn’t help in your case, I suggest you to ensure that the following security permissions are set for the Firebird databases.
• ASPNET for XP or NETWORK SERVICE for 2003 Server – full control on the dist folder
• IUSR – full control on the dist folder
In addition, grant write rights for the data folder in IIS.
Make appropriate security changes and reset the IIS.
Wednesday, January 18, 2006
Firebird problem continued
If you are experiencing the following screen after launching the newly installed Sitecore with Firebird database enabled and the application pool problem is not the case, please follow the steps below in order to make it work.
Please note that the Firebird server is not required to be installed on the web server at all.
If restarting IIS doesn’t help in your case, I suggest you to ensure that the following security permissions are set for the Firebird databases.
• ASPNET for XP or NETWORK SERVICE for 2003 Server – full control on the dist folder
• IUSR – full control on the dist folder
In addition, grant write rights for the data folder in IIS.
Make appropriate security changes and reset the IIS.
Please note that the Firebird server is not required to be installed on the web server at all.
If restarting IIS doesn’t help in your case, I suggest you to ensure that the following security permissions are set for the Firebird databases.
• ASPNET for XP or NETWORK SERVICE for 2003 Server – full control on the dist folder
• IUSR – full control on the dist folder
In addition, grant write rights for the data folder in IIS.
Make appropriate security changes and reset the IIS.
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment