|
|
 Posted 15/06/2005 10:38:06 |
|
|
IF.NET 4.2 Coming Soon
Group: Administrators
Last Login: Today @ 15:10:38
Posts: 1,957,
Visits: 3,021
|
|
AlvistChicago (6/13/2005)
Unfortunately, the problem persists after these steps. I even granted everything except full access for the NETWORK SERVICE user to the folders in question. I still got the error when first hitting the page (subsequent refreshing it doesn't seem to appear). Hi Tim, I'll be providing RC3 later this everning. This will present a more informative message to help determine the exact exception that occured. Can you hold out until this is available?
Kindest Regards,
Ryan Healey
Director / Developer
 Explore our products...
http://demos.instantasp.co.uk/
|
|
|
|
| Posted 18/06/2005 20:52:53 |
|
|
Junior Member
Group: Customers
Last Login: 14/02/2006 08:11:01
Posts: 31,
Visits: 108
|
|
Problem with skin objects: The data at the root level is invalid. Line 1, position 1.Problem with skin objects: The data at the root level is invalid. Line 1, position 1. Is the error it gives now that we have RC3 running in our test environment.
|
|
|
|
| Posted 20/06/2005 14:58:09 |
|
|
Junior Member
Group: Customers
Last Login: 14/02/2006 08:11:01
Posts: 31,
Visits: 108
|
|
| I tried to find where this error is generated but can't. Is there some way to disable it as it's not causing any forum problems for us other than the fact the error message is displaying? I'd like to install the RC3 version onto our public site, but can't as long as this message continues to appear.
|
|
|
|
| Posted 21/06/2005 11:17:16 |
|
|
Junior Member
Group: Customers
Last Login: 14/02/2006 08:11:01
Posts: 31,
Visits: 108
|
|
| Should I repost this? I'm not sure if anyone is noticing these updates to the thread as it's on the second page now.
|
|
|
|
| Posted 21/06/2005 14:35:59 |
|
|
Support Supremo
Group: Customers
Last Login: 13/11/2008 12:44:07
Posts: 568,
Visits: 2,507
|
|
| Dear AlvistChicago, could you please open a ticket at my.instantasp.co.uk and give me a access to your application, as well as describing how you found this problem, so I can see what the problem is first hand?
|
|
|
|
| Posted 22/06/2005 08:47:04 |
|
|
Junior Member
Group: Customers
Last Login: 14/02/2006 08:11:01
Posts: 31,
Visits: 108
|
|
I will open a ticket. Actually, we do have a version running on what I believe is a public webserver now. I've just been told our IP has been wide open to visitors for a while. I'll see what I can do about granting access. We're running IIS6 and Windows 2k3 Server.
|
|
|
|
| Posted 22/06/2005 09:56:46 |
|
|
Junior Member
Group: Customers
Last Login: 14/02/2006 08:11:01
Posts: 31,
Visits: 108
|
|
| When I go to "New Support Ticket", for some reason it says my support has expired, and I see no options to add a ticket.
|
|
|
|
| Posted 22/06/2005 09:59:05 |
|
|
Junior Member
Group: Customers
Last Login: 14/02/2006 08:11:01
Posts: 31,
Visits: 108
|
|
| BTW: As you've changed the error to be more descriptive, perhaps you could direct me to where I can disable this error?
|
|
|
|
| Posted 23/06/2005 05:50:56 |
|
|
Forum Member
Group: Forum Members
Last Login: 03/07/2007 14:57:02
Posts: 56,
Visits: 195
|
|
Through all three RC releases, all of the users on my site have received error messages related to skin and language objects upon signin. With the release of RC3, the message has gotten much longer, and appears like this:
Problem with skin objects: The data at the root level is invalid. Line 1, position 1.Problem with language objects: The data at the root level is invalid. Line 1, position 1. I do not have any custom skins at all and did a clean install of the files - I have checked all the database tables and settings, and everying is set to Classic/English, but these problems still persist. Any insight on how to finally get rid of this error would be greatly appreciated - this is an upgrade of a existing 3.4 forum. |
Cristiano Diaz
SLuniverse.com
|
|
|
|
| Posted 27/06/2005 08:40:36 |
|
|
Junior Member
Group: Customers
Last Login: 14/02/2006 08:11:01
Posts: 31,
Visits: 108
|
|
| If I could only be directed to the point where this error is produced, I would gladly just disable the reporting of this error as it causes no problem with the working of the forum. The error message itself however prevents us from being able to use it in a public test setting, as every other reported bug would be this gigantic error message.
|
|
|
|