Error at line 183 (init.htm) 8007007E
GenoPro Home  |  Get Started With My Genealogy Tree  |  Buy  |  Login  |  Privacy  |  Search  |  Site Map
 
GenoPro Support Forum
Home        Members    Who's On
Welcome Guest ( Login | Register )
        


12»»

Error at line 183 (init.htm) 8007007E Expand / Collapse
Author
Message
Post #21304 Posted 4/6/2008 5:44:07 AM


Forum Writer

Forum WriterForum WriterForum WriterForum WriterForum WriterForum WriterForum WriterForum Writer

Group: Customers
Last Login: Yesterday @ 3:59:18 AM
GenoPro Version: 2.0.1.4
Posts: 57, Visits: 280

I moved all my genograms to my new computer running Vista Home. 

I downloaded and installed the latest version of GenoPro I could find (2.0.1.4).

I updated a genogram which I had not touched since September 2007 without any problems, but when I tried to generate a report (English narrative report {EN}) it generated following error

Generating report to 'D:\Genealogy - Web Site\'
Cloning document Staes - Degrave - Beyen - Boels...
Opening configuration file Config.xml for skin 'English Narrative Report'...
Validating picture cache...
Loading Dictionary.xml...
[0.00]
Processing template 'init.htm'...
Error at line 183, position 1 (init.htm):
8007007E

I looked for the init.htm file but could not find it, so I presume it is a built-in one.

There is another post in this forum that deals with this specific error (see Error 8007007E while generating report) specifying that this error can be generated when loading the VBScript engine, and means that "The specified module could not be found".  Any idea which module this might be?

 Another post also mentions the init.htm file but with error 8002801D (see Error at line 182 (init.htm) : 8002801D). Any relation?

The funny thing is that I have a full VB6 development environment installed on this Vista system, so I really don't know what module to look for.

Post #21305 Posted 4/6/2008 6:10:20 AM


Famous Writer

Famous WriterFamous WriterFamous WriterFamous WriterFamous WriterFamous WriterFamous WriterFamous Writer This user is an important contributor to the translation of GenoPro This user is an important contributor to the GenoPro community This user is a contributor to FamilyTrees.GenoPro.com 

Group: Customers
Last Login: Today @ 11:23:19 AM
GenoPro Version: 2.0.1.6
Posts: 424, Visits: 1,124
Init.htm line 183 is:

Set oShell = CreateObject("WScript.Shell")

Maybe due to a missing Script file? Genopro or Ron will be able to explain a bit more in detail.
If you're using the '\Customized English Narrative Report\*' skin, you should have init.htm in the Dir.
To do so, select the 'English Narrative Report {EN}' skin, click on 'New Skin...' and Genopro should create the Dir mentioned above, i.e. '\Customized ...
JC

Update:

Go to this ad http://www.vistax64.com/vista-installation-setup/67281-windows-vbscript-5-6-a.html and follow the Ramesh tip. The answer may be to register/re-register the VBScript.dll file! I'm no specialist but I don't think you'll harm your system anyway.

Post #21307 Posted 4/6/2008 7:57:39 AM


Forum Writer

Forum WriterForum WriterForum WriterForum WriterForum WriterForum WriterForum WriterForum Writer

Group: Customers
Last Login: Yesterday @ 3:59:18 AM
GenoPro Version: 2.0.1.4
Posts: 57, Visits: 280
I tried the Ramish trick but it did not help.  Same error on same line.
Post #21308 Posted 4/6/2008 8:16:03 AM


Forum Writer

Forum WriterForum WriterForum WriterForum WriterForum WriterForum WriterForum WriterForum Writer

Group: Customers
Last Login: Yesterday @ 3:59:18 AM
GenoPro Version: 2.0.1.4
Posts: 57, Visits: 280
I also installed Service Pack 6 for Visual Basic 6 (VB6SP6, which I had installed on the XP system).  This does not help neither.
Post #21309 Posted 4/6/2008 9:27:49 AM


Grand Master

Grand MasterGrand MasterGrand MasterGrand MasterGrand MasterGrand MasterGrand MasterGrand Master This user is a contributor to FamilyTrees.GenoPro.com This user is an important contributor to the GenoPro community 

Group: Customers
Last Login: Today @ 6:34:28 PM
GenoPro Version: 2.0.1.5
Posts: 1,048, Visits: 4,776
VB6 is quite a different animal to VBScript, the first is compiled whilst the second is an interpreted language. They just happen to share a similar name and some language semantics.

I suggest you download and install Windows Script 5.7. This should already be on Vista but somehow your installation appears corrupt.


'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
Post #21311 Posted 4/6/2008 2:28:36 PM


Forum Writer

Forum WriterForum WriterForum WriterForum WriterForum WriterForum WriterForum WriterForum Writer

Group: Customers
Last Login: Yesterday @ 3:59:18 AM
GenoPro Version: 2.0.1.4
Posts: 57, Visits: 280
Silly me.  I believed VB6 and VBS shared big parts of the run-time code.  Another illusion blown away.

Anyhow, Windows Script 5.7 aborted during the installation, claiming that there is "not enough storage space available".  On a system with 3GB of main memory and 258 GB free on the system disk partition, this looks suspicious if you ask me.  And yes, I ran the installation as administrator.

Post #21334 Posted 4/10/2008 4:18:00 AM


Forum Writer

Forum WriterForum WriterForum WriterForum WriterForum WriterForum WriterForum WriterForum Writer

Group: Customers
Last Login: Yesterday @ 3:59:18 AM
GenoPro Version: 2.0.1.4
Posts: 57, Visits: 280
I found a remark in one of the Vista forums about Service Packs and their side-effects.  They recommend to remove and re-install the SP.  So I removed Vista/SP1 (which I had installed last week) but this did not change anything.  I re-installed SP1, still no change.  The error persists.

Is there a simple way to generate this error (without the use of GenoPro)?  If I could isolate the code it would be easier to debug and get support from MS.

Post #21337 Posted 4/10/2008 6:56:35 AM


Legendary Master

Legendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary Master This user is an important contributor to the translation of GenoPro 

Group: Administrators
Last Login: Today @ 10:45:33 PM
GenoPro Version: 2.0.1.6
Posts: 3,393, Visits: 13,955
Nand (4/10/2008)
I found a remark in one of the Vista forums about Service Packs and their side-effects.  They recommend to remove and re-install the SP.  So I removed Vista/SP1 (which I had installed last week) but this did not change anything.  I re-installed SP1, still no change.  The error persists.

Is there a simple way to generate this error (without the use of GenoPro)?  If I could isolate the code it would be easier to debug and get support from MS.

No wonder why so many are downgrading from Vista to XP.  My sister purchased a notebook loaded with Vista and could not run the software that was necessary for her work, including printers and accounting software.  In the end, we installed XP.

Post #21371 Posted 4/14/2008 3:40:57 PM


Forum Writer

Forum WriterForum WriterForum Writer