File could not be found documents.doc

-
I first saw this when opening a word document from outlook as an attachment, I may be mistaken though this could happen in more scenarios.

Most of you will be glad to hear, the fix is simple!

Go to Start > Run, type "Winword /r"

Comments

Post a Comment

Popular posts from this blog

Huel discount code 2020 - £10 Off First Order Discount Code

-
Image
The Future Of Food Get £10 off of your first order of Huel with a minimum spend of £45, the equivalent of 28 meals.

Huel gives you everything your body needs, its made in the UK and if you order today, it'll be delivered free tomorrow.
Huel is a nutritionally complete powdered food ​that contains all the proteins, carbs, and fats you need plus at least 100% of the European Union's "Daily Recommended Amounts" of all 26 essential vitamins and minerals​. So you know you won’t be deficient in any essential nutrients.



Claim £10 off here: URL: https://huel.mention-me.com/m/ol/jj9uo-0d445f52d9


Read more

This product type does not match the list of supported product types

-
I got this message installing a HP CM1312 on an SBS server, how on earth it is justifiable that an SBS server doesnt meet requirements is beyond me, obviously this being a network shared printer this was no solution so I had to install it.

Even going to the HP website you get the same installer package so you can't use the add printer wizard... a few hours with HP later and finally we cracked it.

So to get past this error simply hold down CTRL + SHIFT when pressing Cancel on the installer, this will then keep the installer running passed the error and works a treat.

Enjoy!

Did I solve your problem? Buy me a virtual beer by clicking on a Google ad :). Thanks!
Read more

LSASS.EXE - System Error / Rebuilding Active Directory Indices. When booting windows server 2003

-
LSASS.EXE - System Error, security accounts manager initialization failed because of the following error: Directory Services cannot start. Error status 0xc00002e1.

I know everyone's scenario's when seeing this message are pretty varied but I found a nice way to fix this within an hour providing you have a similar setup.

In my particular case I had two servers an SBS 2000 (oh dear I hear you cry) and a Standard Server 2003 running SP1. The 2K3 machine was rebooted and upon reboot we were presented with the above error.

So to fix try the following:

1. Reboot the 2K3 server into "Directory Services Restore Mode" then logon to the machine locally, in my case I didnt know the restore password (results of taking on machines from other support companies.)

-If this is the case go onto the second server, right click "my computer" and select manage, within the new window, right click the "Computer Management" header and then click connect to another compu…
Read more