"Null" Error 1

[ssVBAdev]

I have Windows 2000 installed (OEM) and have tried to install numerous programs (ie Microsoft Office 2000, AutoCAD, Adobe Acrobat Reader etc... etc...). The installations (for the most part) go smoothly; no errors. But, when I open any of the programs (Like excel, word, AutoCAD...) I get the error message:

"Cannot find the file '(Null)' (or one of it's components). Make sure the path and filename are correct and that all required libraries are available."

Now, my initial thought is that it has something to do with the Registry but I'm not sure.

I did have problems installing AutoCAD 2004 which uses the MSI (msiexec.exe). Windows could not 'find' it's own MSI program. The Install CD would not work and The 'run' line would not work. I had to circumvent it by installing AutoCAD from the command prompt.

Any Thoughts on why this 'null' error occurs??

 

[rosieBsDad]

This is a stab in the dark, but suggests to me that you may have lost some system path variables.

Go to Control Panel/System/Advanced and click the Environment Variables button.

Make sure you vae a System Variable called "windir" and thatit points to the correct place (default is C:\WINNT)

Also check the Path variable to make sure it includes \WINNT and \WINNT\SYSTEM32

Good Luck.




RosieBsDad

 

[ssVBAdev]

Good thought but I have indeed checked. In fact, when I was installing AutoCAD, I even tried to add the full path (C:\WINNT\System32\msiexec.exe) to the path variable and Windows still couldn't find it.

 

[rosieBsDad]

Hmmm, strange one. Normally "null" would suggest that a variable is being expected which is not set, hence my first guess.

Do the default W2K apps run? (Calculator, Wordpad etc)

RosieBsDad

 

[ssVBAdev]

Yes. All of those Apps run fine - with one exception. If I try to open the registry editor using the "run" line I get the error:

"Cannot find the file 'regedit' (or one of it's components). Make sure the path and filename are correct and that all required libraries are available."

BUT, the registry editor opens and when I click okay to the message box, I can use the editor like normal. If I type "excel" in the "run" line excel opens fine except for the "null" error.

The only problem right now is that when I open program like Excel, Word, Access, AutoCAD with the Icon I get the "null" error. Notice too, that when you open a program, they automatically open a "blank" or "new" document. But, If I click on a saved document and open the file that way - say a .xls file or .doc file - then I do not get the "null" error. So, at this point it has something to do (presumably) with the "blank" document.
(I know that clicking the file is a resolution to the problem in itself, but the fact that the error shows up seems to me to be a symptom of a larger problem that I need to get to bottom of).

But Yes... this is a strange one indeed!

 

[rosieBsDad]

Sounds pretty screwy to me - almost as if the new programs aren't registered in the registry, even though the file associations are there. Did these programs work previously (i.e. before your dodgy install happened)?

Not my favourite suggestion, but it occassioanlly re-installing your current Service Pack can miraculously fix wierd errors like this.

RosieBsDad

 

[ssVBAdev]

Well, the box is new (january-ish) and came with Windows 2003. Another person in my office installed Office 2000 and told me that there was no problems with the install. So far, AutoCAD 2004 is the only program that I know of that I have installed that uses the MSI. So, in short, no. I was getting the "null" error prior to the "dodgy" install.

I did hear that SP3 has caused others problems with the MSI but I'm not sure how it was affected or what happened.

Because the O/S was an OEM they did not allow for the SP3 to be able to be removed from the add/remove software manager so I could not remove SP3. So, I did download a new version of SP3 hoping that the problems were fixed but to no avail.

 

[rosieBsDad]

Oh dear. With all due respect, do you trust your colleague's statement? Maybe the problem was actaully there beforehand but just gone unnoticed?

I hate to say it, but it's beggining to look like a re-install....hope you've got a good set of media from the OEM.

Bit stumped on this one I'm afraid, sorry I can't help any further at this stage, would be interested to hear the outcome - please keep me "posted"

RosieBsDad

 

[ssVBAdev]

Yea, If I do get a resolution I'll be sure to post it!!

BUT - after saying that - I'm not sure I want to go as far as a re-install. Sure it's a pest of a problem but I'm not sure it's worth the headache that re-install problems may cause. My next step is to contact my vendor and let them know about the problem to see if they have run into it before.

As for the install... yes, I have my doubts.

Again, If I find something I'll be sure to post it. thank you for your time

 

[mapleleaf]

ssVBAdev,

Before you reinstall, try one other thing. Go to System>Advanced>EV and edit the path setting. Since you had a "screwey" install it may be damaged.

What I would check for is correct expansion, missing ";" or directories "pointing nowhere"

If it helps here is mine

%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;d:\Program Files\Support Tools\;D:\Program Files\ObjREXX;D:\Program Files\ObjREXX\OODIALOG

Ian

 

[ssVBAdev]

I did check it out right now to be sure but I was telling RosieBsDad earlier that I had looked into it. Sure enough, everything looks fine. When I did the install, I even tried putting the true path to the MSI in the path variable (C:\WINNT\System32\msiexec.exe) - rather than the %system%... and Windows still could not find the MSI.

P.S. (quickly off topic for a second) Your handle "mapleleaf" doesn't refer to TML of the NHL does it?...

 

[mapleleaf]

Unfortunately not. When I signed up I was working at Maple Leaf Foods in TO. Now, of course, I could rant about the "Leafs" blowing it yet again !!, but ...

Your problem is certainly a puzzler. Does anything pop up in the event viewer ??

The other thing you may want to try, before you reinstall (sigh !!), is to open a cmd prompt. Change to \ and type path. It should look right. Check to see if you have an autoexec.bat file thats > 0. If you do, it may contain a path statment that windows is appending. Try typing regedit and see if it runs.

If it does, then you may have a virus hooked into .exe in CLASSES_Root. A quick test would be to rename regedit.exe to regedit.com and try it in the run box

I'm between contracts, so I'm home all day if the above doesn't work

Ian

 

[ssVBAdev]

Nothing shows in the event viewer when I open a program such as Excel. Although, I'm sure the errors from the install are in there. There are some warnings and errors.

Running path in the command prompt shows the same info as the Path Variable but the %systemroot% is replaced with C:\WINNT.

Autoexec.bat in the C: drive is 0KB. Windows 2000 doesn't use the Autoexec.bat though does it?

Typing regedit from the DOS command prompt runs just fine, as it should - no errors. BUT, running regedit from the windows command line ("Run&quot gives me the error. This is how I was able to install AuotCAD in the end. I ran the MSI through the DOS command prompt, with all the required arguments and AutoCAD installed fine - no errors.
Therefore: I can access Windows components from the DOS prompt but not through the Windows GUI.

 

[edemiere]

Personally, this sounds to me like one of those issues that would take ten times the amount of time to figure out over just reinstalling the OS and being done with it.

At least that is what I would do before I wasted too much time trying to figure out such an obscure problem.

Sorry I cannot offer anything more concrete.

Good luck!

 

[mapleleaf]

edemire,

That's true, but lets say it's a Server and not a workstation.

ssVBAdev,

Take a look at CLASSES_Root\.exe It should point to exefile

\exefile\DefaultIcon should be a Reg_SZ containing %1

\exefile\shell\open\command
\exefile\shell\runas\command

should both be a Reg_SZ containing "%1" %*

Ian

 

[mapleleaf]

ssVBAdev,

To answer your other question. Win2K will "parse" a non-zero autoexec.bat file if

CU\Software\Microsoft\Windows NT\CurrentVersion\WinLogon\ParseAutoexec is set to 1

It's for 16-bit compatability, but can cause "fun" if there is a bad PATH statement

Ian

 

[ssVBAdev]

mapleleaf: (I'm still thinking TML if that's alright with you ). I'm a fan)
Yep. All that is correct. I'll be leaving soon though. Workdays almost done!

edemire:
Good point but I'm not interested in going through the pains of reinstalling the O/S. Could cause too much down time right now. Although it's a pretty weird bug I've got here, I can live with it - If I need to.

 

[ssVBAdev]

Seems we crossed paths... I don't need to worry about that, there's nothing in the autoexec and most of what I do (as far as I know) is 32 bit.

 

[mapleleaf]

ssVBAdev,

Pity it wasn't that. I've seen exefile highjacked by a virus before, so it was worth a try.

It's not just the OS, it's all the apps along with their settings.

Run a full scan overnight and see if it picks up anything.

I'll check tomorrow,

Ian

 

[ssVBAdev]

A "Full Scan"? I'm guessing you mean a virus scan. Well, anyway, I missed that post last night. I'm running a virus scan on my computer right now. I'm sure it's not a virus though. One little key piece of info that I have been leaving out is that this is happening to 3 other machines that we bought at the same time from the same company. I had intended on going back to my dealer and saying "Hey! You sold me computers that don't work right!!" But, I was hesitant to try as:
1) I'm thinking that they may try to wash there hands of any problems and claim it was something that I did "aftermarket"...
2) Even if they do want to help, they'll probably want to take my boxes for a few weeks (Not good; That would mean down time for our entire engineering dept!)... and
3) I thought I'd try to see If the problem can be fixed first.
I'm starting to think this is way too far above my head and that I shoud just live with it or go to my dealer.