Runtime error 5: Invalid procedure call or argument.

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Hello I have a problem... again... and I need help... again...

I have a batch of PCs that have recently had a ghost installed. They are all showing the Runtime error 5: Invalid procedure call or argument, whenever I open Microsoft Word attachments from emails. This is only with Word attachments; it doesn't matter if they are .doc or .rtf

So far, I have tried replacing all templates in the OFFICE11\STARTUP folder with known working templates. There are no old/odd templates in use on any of the machines. Word started on its own opens and operates fine.

I was going to try Word in safe mode, but that doesn't really help when the issue is opening from attachments... I think...

Once you 'end' the runtime error, it still opens the attachement you were after anyway.

I have tried the Microsoft Knowledgebase and Google, but can't come up with anything useful.

So... over to you guys...

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

The Runtime error 5 is a generic error. Sorry I don't know of a quick fix. Have you tried installing the latest service pack?

-Ken

 

They are all running Office SP2; we would have to do testing before rolling out SP3. The only thing is, we have this PC type across the company; it is only in one isolated office that the issue occurs.

 

No, they can either be users within the domain, or outside the domain.

This issue is affecting at least half a dozen users.

Oddly enough, I think the issue follows attachments after they've also been saved locally. If this is the case, I can't understand why the Runtime Error also wouldn't occur for any documents created locally...

 

Is it anything to do with the AV scanning email attachments?

 

We don't AV scan emails at client level. We have a facility in our DMZ (I think) that checks the emails before they come in.