C1 Community

Hey, i have a wierd problem. I am using the WS with a WC in my site. I have a SQL Database backend. My connectonstrings all provide sql credentials (username/password)

When debugging in VS 2005 (builtin webserver) the site runs perfectly and as expected.

When i publish my site to the local IIS though, the WS status bar display the following error:

"Error while saving data to file."

I get this error when i try and commit any action! From simply navigating to another day on the webcalcander control, to trying to add appointments. The wierd thing is; my sql profiler displays all data transactions completeing, and if i 'refresh' the page, all my changes have taken effect - even though i get this error message.

Im not sure what the problem could be, im really stumped actually. Maybe a permissions issue? I am using the demo version of the product.

Hi,

The problem is that C1WebSchedule can't save data to the local file.
Default value of the DataFilePath property is "~/C1WebScheduleData.xml".
Please, check that your ASP .NET application directory contains this file and WebServer (ASP.NET application thread) has write permissions fot this file.
This file is used to store information that is not bounded to the database.

With Best regards, Dmitri.

Thanks for the reply Dmirti, i had a hunch it was this and fixed the issue a little while back. I ended up having to create a seperate Application Pool under the IIS settings to give permission to the component to write to this file. Nothing else worked...

We're having the same problem.  We have given write permissions in IIS and directory level write permissions and are still having the same problem.   Could you please tell what specific settings are needed in IIS.  We are having the same problem on Windows XP and Windows Server 2003.

We're unclear when you state "give permission to the component" .  We are not sure what you are referring to as "component" .  Do you mean the website, directory...?

 Please help and thank you.

The way to assign permissions posted by dmitri_m should work, if is not, you need to assign ASP.NET Machine Account write permissions to the root path of your website.

Best Regards,

Igor.