Hello all,
Some months ago I had a Windows NT workstation with Outlook 2002 appear with a script error when loading the Outlook Today page:
An error has occurred in the script on this page.
Line: 298
Char: 1
Error: Class not registered
Code: 0
URL: Outlook Today
Do you want to keep running scripts on this page?
I followed the MS Knowledgebase article at:
which discusses replacing DLLs, without success. The strange thing is that the error was appearing only on 1 user account. Not all of them - if it was a DLL problem I would be inclined to think that it would be happening to all users. Eventually I resolved this by setting the properties of the Outlook Today screen to not show the Outlook Today HTML page, but just to show a blank screen.
This was the only instance I had had of this problem until yesterday when a Terminal Server (Windows Server 2003) user account running Outlook 2003 had the same problem. Again, this was only happening to the one account. I again resolved it by removing the default Outlook Today HTML page from the properties of the Outlook Today screen.
This solution is not ideal as a number of our users like the facilities available on the Outlook Today page. I was wondering if anyone has experienced this before and can maybe shed some light on the cause of this problem?
Some months ago I had a Windows NT workstation with Outlook 2002 appear with a script error when loading the Outlook Today page:
An error has occurred in the script on this page.
Line: 298
Char: 1
Error: Class not registered
Code: 0
URL: Outlook Today
Do you want to keep running scripts on this page?
I followed the MS Knowledgebase article at:
which discusses replacing DLLs, without success. The strange thing is that the error was appearing only on 1 user account. Not all of them - if it was a DLL problem I would be inclined to think that it would be happening to all users. Eventually I resolved this by setting the properties of the Outlook Today screen to not show the Outlook Today HTML page, but just to show a blank screen.
This was the only instance I had had of this problem until yesterday when a Terminal Server (Windows Server 2003) user account running Outlook 2003 had the same problem. Again, this was only happening to the one account. I again resolved it by removing the default Outlook Today HTML page from the properties of the Outlook Today screen.
This solution is not ideal as a number of our users like the facilities available on the Outlook Today page. I was wondering if anyone has experienced this before and can maybe shed some light on the cause of this problem?