No System Explorers

[Bob]

I think this is an install issue, but not sure.

I am a PC Consultant, and I have been experimenting with
installing the beta at some of my client locations. Usually
it installs and runs fine.

But I am having problems with one and only one particular
client. The programs again seems to install and run (i.e.
scan) fine, but there are no System Explorers displayed
(left side is blank), and I can't seem to set the time
correctly for a scan.

Perhaps some kind of firewall or access problem?

Help to debug appreciated.

Bob

 

[Mikolaj]

I think this is an install issue, but not sure.

I am a PC Consultant, and I have been experimenting with
installing the beta at some of my client locations. Usually
it installs and runs fine.

But I am having problems with one and only one particular
client. The programs again seems to install and run (i.e.
scan) fine, but there are no System Explorers displayed
(left side is blank), and I can't seem to set the time
correctly for a scan.

Perhaps some kind of firewall or access problem?

Help to debug appreciated.

Bob

Try this in command prompt:

regsvr32 msvbvm60.dll

 

[Bill Sanderson]

Mystifying isn't it? Mikolaj has posted the right fix, I believe. This is
a file versioning issue, nothing subtle like ports or firewalls.

 

[Mikolaj]

Mystifying isn't it? Mikolaj has posted the right fix, I believe. This

is a file versioning issue, nothing subtle like ports or firewalls.

Thank you very much for your kindness, but it was your solution, I'm
affraid ;-) :-D

 

[Bill Sanderson]

Well - to be more precise, the original fix that we had, the SP for the VB6
runtime, was contributed by another user here. Then Steve Dodson posted
that revised fix from Microsoft--so this is really Microsoft's fix.

And you're the one doing the work posting it--and that's the important part.
--

 

[Mikolaj]

Well - to be more precise, the original fix that we had, the SP for the

VB6 runtime, was contributed by another user here. Then Steve Dodson
posted that revised fix from Microsoft--so this is really Microsoft's fix.

Yes, of course, you are right - I remember the moment that this solution
came up after the SP6 for VB solution.

And you're the one doing the work posting it--and that's the important
part.

Thank you very much, but I'm still far, far behind you
And that is MVP's "job" to help the others

 

[Pappa Dave 97]

I would like to thank you too, I had the same issue
Dave