I am just trying to set up DagDig with DigiTV and DigiGuide. when I right click and select 'record with DabDig' I get the following error: c:\{path}\dabdig.vbe Line 524 Char 1 Active X component can't create object 'Scripting.Dictionary' 800A01AD Microsoft VB Script runtime error.

I use Windows XP Sp2 and have Norton Internet Security installed.

Any ideas?

Hmmm - when I have come across that before it seemed to be due to a corrupt or very very old version of the Windows Scripting Host software.

Being old seems unlikely given that you are on XP SP2.

So perhaps something has gone wrong with the Windows Scripting software itself.

I suppose that it could be the anti-virus (etc) code - but I would have expected a problem to be reported via their software.

Perhaps you could try using to re-install Windows Scripting Host - from MS.

DABDig creator

Edited by Paul Webster on Wednesday, December 28, 2005 - 3:10:47 PM

Thanks for that - I thought it was sorted, but now I get "Can't find script engine 'VBScript.Encode' for script 'c:\{path}\dabdig.vbe'."

Really appreciate the assistance!

That sounds like Windows Scripting Host can not work out how to handle a .vbe file(as opposed to a .vbs).

What did you do to make you think that you had resolved the problem?

(might give me a clue about what has gone wrong)

For example - did you move Windows at some point from one drive to another or to a different directory?

If so - then it suggests to me that there is a registry key pointing to the old location.

Hacking the registry might get round that problem - but could leave others lurking.

DABDig creator

After downloading and installing WSH the error message changed and took longer to show (hence 'thought it was sorted').

I wondered whether I had done something daft when installing digiguide and dabdig; so I have now gne back to a restore point before either was installed, re-installed WSH, digiguide and dabdig (in that order). Back to square 1 I'm afraid! Any more ideas?

Here is a simple piece of VBScript that will hopefully show the problem - and also show when it is fixed ... just save it as vbtest.vbs (remember to tell Notepad to save as "All files" or similar - otherwise it will be called vbtest.vbs.txt and will not work)

wscript.Echo("Starting - if you do not see 'Ending' then there was a problem")
Set objStrings = CreateObject("Scripting.Dictionary")
objStrings.Add "String1","Hello World"
wscript.Echo("Ending")

then double-click on it from Windows Explorer to run it.

First show that this repeats the problem - then ...

Try:

Start/Run/Cmd

<enter>

this should bring up the "DOS" box.

Then type:

regsvr32 scrrun.dll

This will re-register part of the Windows Scripting Host.

Check for any error messages.

Then re-run the test above.

DABDig creator

Still got the problem:

re-registered scrrun.dll

DllRegisterServer in scrrun.dll succeeded.

Tried your test script again:

Starting - if you do not see 'Ending' then there was a problem

Same problem:

Script: C: \Documents and Settmgs\TV\My Documents\vbtest. vbs

Line: 2

Char: 1

Error: ActiveX component can't create ob]ect: 'Scripting.Dictionary'

Code: 800A01AD

Source: Microsoft VEScript runtime error

Try this one then ...

regsvr32 wshom.ocx

then run my little test vbs file again

and if still not working - then - just in case - can you disconnect from the internet and then temporarily disable your anti-virus software just in case it is really that that is causing the problem.

Other prople who have hit similar problems - although unrelated to my stuff ... but just to let you know that you are not alone ...

try this Google search.

DABDig creator

Edited by Paul Webster on Friday, December 30, 2005 - 5:50:09 PM

Tried re-registering scrrrun.dll - no joy I'm afraid!

Also fully stopped the NAV, tried again - no difference.

This is becoming a fascinnating challenge - at least for me.

Are you willing to give me remote access to your machine so that I can poke around the registry and try various tools to see if I can work out what has gone wrong with VBScript?

If you are then send me an email and propose a suitable time and I'll see what I can do.

DABDig creator

I don't suppose this was ever resolved?

I've just installed DabDig for the first time and run into exactly the same problem

As it happens ... it was resolved.

Short version: aardvark reinstalled Windows and all was well

However, there are a couple of suggestions that I had that we never got around to trying.

For example this thread.

Just wanted to double-check - are you getting exactly the same error as aardvark first reported

i.e.

"c:\{path}\dabdig.vbe Line 524 Char 1 Active X component can't create object 'Scripting.Dictionary' 800A01AD Microsoft VB Script runtime error."

or as his later report:

"Can't find script engine 'VBScript.Encode' for script 'c:\{path}\dabdig.vbe'."

plus - have you tried any of the steps that I outlines in this thread and were you able to repeat the problem with my tiny test script shown further up the thread (vbtest.vbs)?

DABDig creator

I was getting exactly the first error...

but I then tried re-installing Windows Script 5.6 and now I'm getting exactly the second error!

Yes I can repeat exactly with your test script.

I haven't tried the various other dll re-registering tricks, and I hadn't come across the other thread you mentioned. I am at work now, so some things to try later.

What my attempts to fix this have revealed is that it is likely to be a permissions problem. The Administrator user can run your script, but my usual Power User login can't. I tried putting my Power User in the Administrator Group but this didn't seem to help.

My suspicion is that some MS security update is having unintended effects on my PC's ability to run scripts.

Aha - ok - I had come across a couple of people, through searching the web, that had found that running various scripts as Administrator and non-Administrator (but member of Admin group) were getting the original error.

I didn't get a chance to try this suggestion out with aardvark - but ...

first get back to the starting point where you were getting the ActiveX error message using vbtest.vbs

then ... edit vbtest.vbs and inset an additional line at the top

Dim objStrings

If that makes it work from the non-admin account then there must be some special place that MS is storing undeclared variables and it is failing to write to it when the requestor is missing a particular permission.

DABDig creator

I managed to get back to having at least some basic VB scripting working, only through the magic of system restore.

Tried adding the declaration as you suggested, but still the same problems unfortunately - but thanks for trying anyway.

I'll see if I can research how to diagnose security problems like this, but I'm a VBScript newbie, so a bit of an uphill stuggle I expect.

Just glad I only have to program Unix computers to earn a living!

Damn.

Another one to try ...

regsvr32 c:\Windows\System32\VBScript.dll

(change the path to the real location of your WBScript.dll if it doesn't work)

Another thought - were you logged in as the Windows Administrator account (rather than as a member of the Admin group) when you re-installed Windows Scripting Host?

DABDig creator

Edited by Paul Webster on Thursday, January 12, 2006 - 7:35:07 PM