Jump to content
TNG Community

Census Plus DOM Source


MadRanger

Recommended Posts

Post is in the wrong Forum (now moved to the Addons forum by Roger)

Good afternoon,

Is anyone else experiencing repeated errors when importing Interactive Viewer Data?

In the last hour I have received the following error on 5 of the last 6 imports. The only successful import was immediately following a reboot. I have even reinstalled the MOD. The import process worked once earlier in the day.

"The string http://interactive. was not found. DOM Source is not from the interactive viewer.

Please use the Import Old Viewer US Census Plus Data button."

The old viewer brings up an empty matrix.

Using TNG v10.0.1

MOD v10.0.0a

Thanks,

Regis

www.CarrFamilyTree.com

Link to comment
Share on other sites

Post is in the wrong Forum (now moved to the Addons forum by Roger)

Good afternoon,

Is anyone else experiencing repeated errors when importing Interactive Viewer Data?

In the last hour I have received the following error on 5 of the last 6 imports. The only successful import was immediately following a reboot. I have even reinstalled the MOD. The import process worked once earlier in the day.

"The string http://interactive. was not found. DOM Source is not from the interactive viewer.

Please use the Import Old Viewer US Census Plus Data button."

The old viewer brings up an empty matrix.

Using TNG v10.0.1

MOD v10.0.0a

Thanks,

Regis

www.CarrFamilyTree.com

Regis,

Please attached the DOM source that you are having a problem with, as well as provide the URL link on Ancestry for the census that you created the DOM Source from.

Link to comment
Share on other sites

Ken,

The latest DOM is attached (possibly-no indication it attached so I will also send to your personal account ); the url is

http://interactive.ancestry.com/6742/42444...el=ReturnRecord

Thank you,

Regis

Regis,

Is this the only census you are having a problem with? It appears to be a basic viewer generated DOM source. However, it will not import correctly in the basic viewer.

Link to comment
Share on other sites

Is this the only census you are having a problem with?

Ken,

There were 5 failures earlier and I developed a 6th minutes ago (attached) trying to work my way thru the problem.

I retried the Kelly-Lana-1880 DOM and got the same error message. I tried using the basic viewer to import and got a message: Transcript ID & is already in the database. After selecting the ampersand in the message (which would normally be the full ID) there was nothing to import - although an empty matrix did display.

I finally saw the error message when the new attachment failed - it is now attached as a txt.

Related url: http://interactive.ancestry.com/6742/42444...el=ReturnRecord

I am not processing the data selection using basic viewer - nor when I import. And am still getting the error.

I will go back at this in the morning - with a break for a funeral out of town. So far it appears I am the only one facing the problem.

Thank you,

Regis

Pace_Dreadzil_1850.txt

Link to comment
Share on other sites

Dave Foster

Ken,

I too have this problem today with the only 2 census imports I have tried, one UK 1911, one UK 1901.

The UK 1901 entry is spread across 2 pages, so just deal with 1911.

I am searching for Daisy Headland in 1911, using Firefox.

The ancestry.co.uk url is:

http://interactive.ancestry.co.uk/2352/rg1...rnSearchResults

The transcription file is attached.

If you need more, I will gladly provide any help I can.

Rgds,

Dave Foster

1911_F1933_Headland_Edwin.txt

Link to comment
Share on other sites

Ken,

I too have this problem today with the only 2 census imports I have tried, one UK 1911, one UK 1901.

The UK 1901 entry is spread across 2 pages, so just deal with 1911.

I am searching for Daisy Headland in 1911, using Firefox.

The ancestry.co.uk url is:

http://interactive.ancestry.co.uk/2352/rg1...rnSearchResults

The transcription file is attached.

If you need more, I will gladly provide any help I can.

Rgds,

Dave Foster

Dave,

Thanks for attaching the DOM source file. I will be posting a new version of the Census Plus International mod later today after I finish testing. Ancestry has changed their DOM source generator once again.

Link to comment
Share on other sites

Dave Foster

Dave,

Thanks for attaching the DOM source file. I will be posting a new version of the Census Plus International mod later today after I finish testing. Ancestry has changed their DOM source generator once again.

Ken,

I suppose you have tied to get Ancestry to warn you about these changes - and just been ignored?

My experience with Ancestry is that they don't respond very quickly.

Thanks for the info.

Regards,

Link to comment
Share on other sites

Ken,

I suppose you have tied to get Ancestry to warn you about these changes - and just been ignored?

My experience with Ancestry is that they don't respond very quickly.

Thanks for the info.

Regards,

I have posted a new version of the Census Plus International mod that should resolve the import problems for all census series as well as the max_join_rows issue which requires that you create indices for the tables.

Link to comment
Share on other sites

Dave Foster

I have posted a new version of the Census Plus International mod that should resolve the import problems for all census series as well as the max_join_rows issue which requires that you create indices for the tables.

Ken,

Everything is fine now.

Thanks yet again for your sterling work.

Regards

Dave

Link to comment
Share on other sites

Jan wrote in an email: "I just upgraded Census Plus International to version 10.0.0.1a, but can't read the DOM files from Ancestry."

Regis replied: "I have had the same issue (for several days – but for some reason I can get the DOM read on the 2nd try; not elegant, but it has kept me busy. I am using MOD 10.0.0.1 since I was unaware of today’s release. "

Ken,

I installed MOD 10.0.01a this morning and the attempt to load the first DOM resulted in a message that the DOM could not be read. I saved the record again and simply overwrote the same file and the file loaded.

The attached DOM will not load - first attempt:The string http://interactive. was not found. DOM Source is not from the interactive viewer.

The corresponding URL is: http://interactive.ancestry.com/7602/00411...el=ReturnRecord

And after posting this message I went back, saved the record again (simply over-wrote the first DOM) and was then able to load the DOM. I have in the past manually added the .txt suffix and that seemed to work as well. In retrospect, it seems that regardless of suffix added or not, the 2nd saved file always works.

Regis

Walsh_Edward_1900.txt

Link to comment
Share on other sites

Ken,

I installed MOD 10.0.01a this morning and the attempt to load the first DOM resulted in a message that the DOM could not be read. I saved the record again and simply overwrote the same file and the file loaded.

The attached DOM will not load - first attempt:The string http://interactive. was not found. DOM Source is not from the interactive viewer.

The corresponding URL is: http://interactive.ancestry.com/7602/00411...el=ReturnRecord

And after posting this message I went back, saved the record again (simply over-wrote the first DOM) and was then able to load the DOM. I have in the past manually added the .txt suffix and that seemed to work as well. In retrospect, it seems that regardless of suffix added or not, the 2nd saved file always works.

Regis

Regis,

I thought I had sent you the fixes for v10.0.0.1 to test before I posted them to the wiki. It would have been nice to receive feedback that the fix did not always work.

It appears that Ancestry does not always generate the DOM Source the same way so I am re-engineering that fix.

Link to comment
Share on other sites

I thought I had sent you the fixes for v10.0.0.1 to test before I posted them to the wiki. It would have been nice to receive feedback that the fix did not always work.

Ken, you did send the v10.0.0.1 fix to me and I did test it. It worked fine until a few days ago. Since I had a workaround I did not bother you - except to chime in on Jan's query. :)

Regis

Link to comment
Share on other sites

Ken, you did send the v10.0.0.1 fix to me and I did test it. It worked fine until a few days ago. Since I had a workaround I did not bother you - except to chime in on Jan's query. :)

Regis

OK, but if you would have said something, I might have fixed it in the v10.0.01a. :-( No problem. I will be fixing all the Imports and creating a v10.0.0.2 since I am adding new messages to hopefully catch the situation in the future.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...