|
|
|
|
Customers
GenoPro version: 2.0.1.4
Last Login: Tuesday, March 11, 2008
Posts: 18,
Visits: 111
|
hm.I tried deleting that file and it stopped on a new file, much earlier into the session this time, same error message. I did notice before the new build that the error message did not stop on the same file every time, but I thought I would give it a try anyway. I am at a loss, since after reading, the 12019 error can mean so many things (most of which are way over my head).
|
|
|
|
|
Customers
GenoPro version: 2.0.1.4
Last Login: Tuesday, March 11, 2008
Posts: 18,
Visits: 111
|
Ok, may have discovered something...As far as I can remember, upload error always occurred with one of the ship manifest pics. All of those pictures have a # in the name. I removed all the pictures on the report with a # in the name and was able to upload entire report successfully. I renamed all those pics to remove the # and will add them back to the report and try to upload again to test my theory.
|
|
|
|
|
Customers
GenoPro version: 2.0.1.4
Last Login: Tuesday, March 11, 2008
Posts: 18,
Visits: 111
|
Well, I added a few of them back in, renamed without the # and shortened the names a bit and got the error again, indeed on one of those pictures in particular. So, it is something about those pictures (all are from a "series" of photos) that it doesn't seem to like. I will remove that series completely from the report and just continue without them. They aren't wholly necessary, and it seems to work fine so far without them.
|
|
|
|
|
Administrators
Moderators
Customers
Gamma
FamilyTrees.GenoPro.com
Translator
GenoPro version: 3.1.0.1
Last Login: Thursday, January 16, 2025
Posts: 4,886,
Visits: 22,775
|
The problem is not with the naming of the picture. GenoPro make sure the name of a picture is web-friendly, by removing special characters reserved on the web. For instance, the # has a special meaning in a URL.My guess is it is a problem with your Internet Service Provider (ISP) caching the HTTP requests. For instance, each time a picture is uploaded, GenoPro fetches the page upload.ashx. Although the same the same page (upload.ashx) is requested many times, its content is different from one request to another. Is is possible your ISP remembers the value of one page, which causes errors further down the road. The size of your picture may have something to do with the policies of page caching. For instance, a page of one kilobyte is not worth caching, but a page of one megabytes is worth remembering in the cache.
|
|
|
|
|
Customers
FamilyTrees.GenoPro.com
GenoPro version: 3.0.1.5
Last Login: Sunday, January 19, 2020
Posts: 6,
Visits: 71
|
This may or may not help but I am going to pass on my own experience just in case it has any relevance.Some time ago I tried in vain to upload full reports from Genopro to my personal webspace on Freeserve. On each occasion a number of files would upload and then the system would time me out. Technical support from Freeserve were as stumped as I was although they suggested it might be a problem with the hardware firewall installed in my router. On the next upload attempt I noticed that for each file upload a different port was being looked at and the system would fail after using only four or five. I then configured the hardware firewall to allow port scanning and this fixed all the upload problems. I also have a software firewall and other security measures in place which have so far prevented any nasties from scanning my ports. A useful tool to check your system is 'leaktest' from grc.com - just for your peace of mind if you do allow port scanning. I have now changed ISP but can still quite happily upload full reports to my personal web space although I haven't tried the GenoPro family tree site yet. Your problem seems to have some similarities to the one I had so I am hoping that this info might just help. Best wishes
|