Page 1 of 1

Problem uploading spread

Posted: Thu 14 Aug, 2008 4:54 pm
by WebWeaver
When I tried to replace a spread I've update, and then tried to just add the spread I received the following error:
Access to the path 'C:/Inetpub/wwwroot/Horizons/Spreads/NAMEOFSPREAD.xml' is denied.

Re: Problem uploading spread

Posted: Thu 14 Aug, 2008 5:47 pm
by Programmer
Maybe if you use a spread and then try to replace it in the same session of using the program you would get that sort of error because of a locking issue on the xml file. That is you either edit, create or deal out a spread, and then you try to replace the same spread by downloading it from the internet. Is that what is happening?

Re: Problem uploading spread

Posted: Thu 14 Aug, 2008 8:12 pm
by WebWeaver
No, I was trying to upload it to the Orphalese site. Not in my personal spreads, but the ones on the site available to download. I edited it in my spreads, and then wanted to update the spread I shared here. I did just try uploading a spread I hadn't made any changes to, and received the same error. Possibly this is a cmod setting on the site, or has something to do with the change in servers?

Re: Problem uploading spread

Posted: Fri 15 Aug, 2008 11:57 am
by Programmer
Sorry, I didn't read your post properly. I think I have fixed the permissions on that folder now. Maybe you could try again and let me know how you get on. Thanks!

Re: Problem uploading spread

Posted: Fri 15 Aug, 2008 3:31 pm
by WebWeaver
Nope, still getting:
'C:\Inetpub\wwwroot\Horizons\Spreads\09 Dark Moon.xml' is denied

Re: Problem uploading spread

Posted: Fri 21 Nov, 2008 2:32 pm
by StaceyUK
I'm getting a similar message when trying to upload a spread except mine has a different xml filename. :-s

Re: Problem uploading spread

Posted: Tue 06 Jan, 2009 11:21 am
by Programmer
I just found this thread again yesterday and noticed I have left it unanswered. I don't know why that problem seemed to persist, but because the whole business of spread uploading and downloading is about to get a major overhaul it is really not worth trying to work out why or how to fix it. Any one having this problem might like to look at the post I am leavning now, regarding the next set of program changes (I will call it "Program Changes January 2009" and post under Programs >> General Discussion).

Cheers,
Richard