These forums are read-only and considered to be an archive. Please use the new Community for future interaction and posts.

There was an error retrieving the XML data.

I am getting this error when uploading a file:
"There was an error retrieving the XML data. Internal server error".

When I look at the webserver logfiles I see this line:

148.177.129.213 - - [14/Mar/2006:12:35:46 +0000] "POST /fv/action.asmx/GetUploadProgress HTTP/1.1" 500 0 "http://files.fffs.be/fv/upload.aspx?rootPath=%2Fprivate&relativePath=Cappaert%20Luc&refresh=1" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727)"

How can I resolve this issue ?
Cappaert Luc 3/16/2006 2:03 AM
more information on this error ...
I used the fiddlertool to capture the actual response from the webservice ... It appears to have something to do with the date/time format ...

HTTP/1.1 500 Internal Server Error.
Date: Thu, 16 Mar 2006 22:17:41 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
MicrosoftOfficeWebServer: 5.0_Pub
X-AspNet-Version: 1.1.4322
Cache-Control: private
Content-Type: text/plain; charset=utf-8
Content-Length: 48

String was not recognized as a valid DateTime.
Cappaert Luc 3/16/2006 5:20 PM
OK - I found the solution myself ;-)
I had been playing around with the Culture settings in the web.config ... apparantly FileVista does not like any culture other than en-US :-(

Maybe something that Cem can have a look at ?
Cappaert Luc 3/16/2006 5:25 PM
Hi Luc,
Actually FileVista likes every culture :) it will also support multi-language soon.

I guess you changed the culture setting in appSettings node
 <add key="Culture" value="en-US" />
and not in ASP.NET default setting node
 <globalization/> 

I am not sure which build you have but it may be small bug in earlier builds so I am sending you the latest builds of DLL files.

Please replace the DLL files and do the same changes in the web.config. See if this fixes the problem, let me know.
Cem Alacayir 3/16/2006 10:24 PM
Hi Cem,

your guess is correct ;-)

I had a version of march 2nd 2006 - replaced it with the files you supplied ... everything seem to be working fine.

Thanks for the support.
Cappaert Luc 3/17/2006 1:10 AM
I am having this same problem. Should I upload new dll's? Where can i get them?
Joel Szwarga 10/27/2006 6:16 PM
Hi Joel,
Are you sure you are having the same problem because you purchased the product on August which means you should already have the updated DLLs. Anyway I am sending you the files via email.
Cem Alacayir 10/28/2006 7:12 AM
Hi, 

I faced the same problem. I am not sure what happen is it? It works fine until today the problem is triggered. 

I used the mentioned tool "fiddlertool" in the previous email and try to trace out the error, but only the following information are captured. 

HTTP/1.1 500 Internal Server Error
Date: Sun, 21 Sep 2008 10:54:16 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 3026

I am using fileVista 2.9 version. 

Regards,
Ken
ken 9/21/2008 4:03 AM
still have the same problem, after checking with the fiddlertool I got:

HTTP/1.1 500 Internal Server Error
Date: Sun, 21 Sep 2008 20:37:03 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 3037
solomax 9/21/2008 1:45 PM
please be so kind to help. I just purchased this for a custumor and is very glad to have bought this product because of the great solution it can bring but we need to use it quick.
solomax 9/21/2008 1:47 PM
Internal server error is a very generic error and can be caused by several things that are misconfigured on the server.

For example, in the case of solomax, we have found that the problem was that the user NETWORK_SERVICE did not have Modify permissions on c:\windows\temp. This was preventing ASP.NET from compiling the pages because ASP.NET couldn't write to the temporary files location.

If you are sure permissions are not the issue, please reinstall ASP.NET (v2.0 SP1), in some cases this kind of strange problems are solved by doing this.
Cem Alacayir 10/16/2008 7:27 AM
We tried install the trial version.
When try to login, it prompts me error
"There was problem retrieving the XML data.
Internal Server Error (Error 500)"

We have made use of your forum and did a google search on that error message. But couldn't come out with a solution.

Please support.
Victor 11/4/2008 1:12 AM
Please run

C:\windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i

And check the permission on these folders:

c:\windows\temp
C:\windows\Microsoft.NET\Framework\v2.0.50727\Temporary Asp.NET Files 
Cem Alacayir 11/18/2008 2:01 PM
I have similar problem, but in my case, I can login and perform administration tasks, and also list subfolders of ROOTs thats Local, but, when I try to  list subfolders of a root that is located on Network Shares I get the same error message (after a long time waiting).
Please Help! This must be solved before I purchase this grat software.

Thanks in advance.
Geraldo Magella 11/20/2008 1:27 PM
Accessing network shares (UNC paths) is different than local folders in regards to user context.

By default, ASP.NET applications run under the context of NETWORK SERVICE or ASPNET users but when accessing a network resource, the other machine will not recognize those users as they are local users. So you need to run the application under the context of a common user which you can add to the ACL of the network share with the required permissions. 

If there is a domain, you can use a domain user for this purpose. When you include the below settings in web.config:

<authentication mode="Windows" />
<identity impersonate="true" userName="SomeUserX" password="Password123" /> 

FileVista will be executed directly under the identity of SomeUserX and not under system accounts like NETWORK SERVICE or ASPNET. So, you need to make sure SomeUserX can access the share. If you are connected to a domain, this would be easy because you would go to the other machine and give permissions directly to this domain user as you  can select him in the list.

However, you can not select and add a user of another computer if there is no domain. In this case you need to create a user with same name (eg. SomeUserX) and password on the other server and use this common user for the impersonation setting above. FileVista is dependant on Windows permissions so you should first try in Windows if you can access the share with the user SomeUserX that is created on both machines. If Windows can access then FileVista will be able to access too.
Cem Alacayir 11/27/2008 8:08 PM
Thanks for you feedback Cem Alacayir, but I well aware of this behavior as I administer a webcluster and this is a reality for all my websites. I tried to change the configuration as you said, but i'm getting the same error.
Geraldo Magella 11/28/2008 3:26 AM
Ok, Geraldo's problem seems to be the timeout issue, as he said his root folder (pointing to the network share) has 170 subfolders and  he got the error after waiting for few minutes.
170 is not a big number, the important thing is the depth of the subfolders. I recommended him to increase the execution timeout in web.config: 

<httpRuntime executionTimeout="1000">
Cem Alacayir 12/1/2008 2:29 PM
I jsut did a new installation from source, (We have had this running for a customer previously - running great) and I ran into this error.

I solved it by adding NETWORK SERVICE to c:\windows\temp with modify permissions.

Thanks for the post, I was very happy to find it.

Leon
Leon Benson 4/16/2009 10:34 AM