I've been trying to get dabdig to work with digiguide (8.0) and digitv beta 3.12 (first b3, now b4).

I keep getting an error message whether or not the digitv app is running. I've tried uninstalling & reinstalling both digiguide and digitv, but keep getting the same problem. Running XP Pro SP2.

Please let me know what I can try to get this working.

Thanks,

Jon.

Error Message -

---------------------------

Windows Script Host

---------------------------

Script: C:\Program Files\DigiGuide TV Guide\dabdig.vbe

Line: 12014

Char: 5

Error: 0x80041001

Code: 80041001

Source: (null)

---------------------------

OK

---------------------------

I'm looking into this - it is not the first time I have had it reported.

It is very very early in the code - and is the first call to the Windows Management Instrumentation (WMI) interface. I call a routine to find the local GMT offset just in case I need it later.

You can disable that piece of code by setting

CheckLocalTimeoffset=0 in your dabdig.ini - however, that might simply make the more fundamental problem move on to somewhere else. However, you might be lucky.

In the FAQ section in the dabdig.htm there is a reference to a couple of other error codes from WMI that have come up because of this call. I would like to find the real cause - but hunting around has not helped yet.

DABDig creator

Edited by Paul Webster on Thursday, November 11, 2004 - 2:20:15 AM

Looks like it's moved on - same error and code but a different line reference. A bit frustrating because I have had it working with older versions of DigiTV, but would like to get it working with this version because of the ability to fix the mpeg stream on recording.

Is there any logging I can send you which might help you to track this down?

Jon.

---------------------------

Windows Script Host

---------------------------

Script: C:\Program Files\DigiGuide TV Guide\dabdig.vbe

Line: 2385

Char: 5

Error: 0x80041001

Code: 80041001

Source: (null)

---------------------------

OK

---------------------------

The issue really should not be to do with the version of the Nebula software (the first issue you saw was well before DABDig even knew that you had DigiTv configured - I use DigiTV 3.12b4 myself).

Is there anything in the Windows Event Log - some sort of permissions problem perhaps.

I have sent you a snippet of code that I hope will exhibit the problem on your box - if it does then I can take you through some tracing software and we can compare results ... to find where in the MS software it is going wrong.

You can increase tracing in DABDig by setting TraceFlags=8 (etc) - but the issue is something to with VBScript using WMI.

How about reinstalling WMI or VBScript in XP?

DABDig creator

Edited by Paul Webster on Thursday, November 11, 2004 - 3:59:31 PM

Hi,

I have also just ( today 12th November) renewed my sobscription with digiguide and nebula digitv and am getting the same script error panel. Any further thoughts?

regards rosbif

Ps I am a rank beginner regarding scrips and progamming.

Current thought is that it is a corrupted WMI configuration within XP.

I sent Jon a small piece of script that exhibits the same problem.

So - depending on how confident you feel ... you might like to try this to see if it solves your problem (I sent the same to Jon but he has not tried it yet) ... WARNING - UNPROVEN - you might want to wait until Jon has had a go as well (I think he is a bit more of a PC techie).

So ...

If you have a look in
%windir%/system32/wbem you will find some interesting stuff ... including a
"Logs" directory.
wbemess.log is a text file and might also be showing the error that you are seeing in DABDig.
If its database is corrupt then you could try this (make backup first)
1) From "DOS" command line:
   net stop winmgmt
2) delete the %windir%\system32\wbem\repository directory 
3) From "DOS" command line
   net start winmgmt 
This should then recreate the contents of that directory.

DABDig creator

Edited by Paul Webster on Friday, December 03, 2004 - 1:11:30 PM

Here's a quick update.

I haven't made much progress, but I have managed to get the winmgmt system working again using Pauls steps above and a bit of prodding.

I'm still getting a permissions error, it's described very well in this forum post: http://www.mcse.ms/message367757.html but I've so far been unable to fix it (haven't tried the semi re-install yet).

The symptoms are apparently common to a msblaster worm/virus infection, but I can't find any evidence that this is the case on my machine - it's always had up to date antivirus, I don't use that machine for email, and my home network is behind a router.

I may end up reinstalling from scratch...

Jon.

Edited by Jon Sebright on Tuesday, November 16, 2004 - 7:57:44 AM

Edited by Jon Sebright on Tuesday, November 16, 2004 - 7:58:45 AM

SUCCESS!!!

Well, finaly cracked it! - although I don't know how long it will last as I'm too scared to reboot.

Many web searches revealed that this was not an uncommon problem, and that a solution does not work for everyone. I cannot say that this will work for all, nor that it is the only step - it was the final step that eventually worked, everything else failing, but if you've got the permissions problem then it seems to be a likely solution.

I do not know if there are any undesirable side effects to doing this, only that it worked to solve my WMI permissions problem once. If you care about your system or data it's worth taking backups whether you do this or not... Your own risk etc.

So, this is what I did...

Control panel, administrative tools, component services. Follow the Component Services tree through Computers, My Computer, DCOM Config. Find the component called "Microsoft WMI Provider Subsystem Host". Right click it and select properties. Go to the Identity tab. Change the user account to run the application to be "The interactive user" and Apply. That's it.

There were many other steps I did messing about with wbem and winmgmt which may have also made this solution work... I can't say for sure.

Oh yes, DABDig is working now!

Jon.

Well done for the persistance and detective work Jon.

So M. Rosbif - looks like you can go through the same steps.

I think you start with mine above and then if you hit the permissions problem then use Jon's step.

As usual in this sort of situation ... it is at your own peril - but I'll do what I can to help.

Just in case ... might be worth buring a CD of your most useful stuff (unless you already regularly do backups of course )

DABDig creator

Copious apologies for my very tardy reply. Circumstances beyond my control.

I have searched my system 32 files and cannot find any reference to wbem files. I have used 'Agent Ransack' as a support search but again no luck. Your advice would be appreciated. Many thanks for your efforts so far. mike (rosbif) greenwood.

Update

rosbif had another dig around and found the files.

He then went through the steps that I suggested above ... and it now works.

DABDig creator