Outlook 2010 reopen and connection problem
Hi!
I have been facing an annoying problem on a fresh new machine installation with Windows 7 Home Premium 64-bit and Outlook 2010.
Outlook 2010 with IMAP port 143 and just simple settings will get stuck with send/receive after one-two s/r attempts and can got functioning again only by a machine restart, and, the problem is there again just after few moments! There is probably appearing some corruption on the net connection modules/settings ...
Another syndrome on this is appearing, if Outlook 2010 is closed and reopened, it will not got opened properly, but stuck on "Loading Profile". Sometimes the previous Outlook.exe is still active on the processes and a new one opened aside, so, there is two of them, and, even more, if tried to open several times, but sometimes just the newly opened process only. Anyway, Outlook 2010 will not got opened, probably about for the same net connection problem as described above.
OK, I have found some corrective hints, profile recreation, add-in disablings etc. other tricks and tried them, already a few times, but nothing seems to help ...
An old neighbour XP-machine on the same 4-port network switch with Outlook Express 6 and same IMAP port 143 simple settings do work all fine! So, there may not be much reason to blame the ISP/mail-provider ... Neither to blame the firewall or other programs/services, as no type of fresh/clean/safe starts do not make any difference.
And yes, one more note, the account settings test hasn't worked at all, neither the first time when establishing this account nor on any test after any correction trial!
One guess, could there be some bug on the Outlook 2010 32-bit version, used on a 64-bit Windows 7 Home Premium, causing some corruption on the net connection after one-two mail send/receive attempts? And, where/how to obtain an Outlook 2010 64-bit version?
Please, give any hints to this desperate ocean-deep research on these MS products ...
I have been facing an annoying problem on a fresh new machine installation with Windows 7 Home Premium 64-bit and Outlook 2010.
Outlook 2010 with IMAP port 143 and just simple settings will get stuck with send/receive after one-two s/r attempts and can got functioning again only by a machine restart, and, the problem is there again just after few moments! There is probably appearing some corruption on the net connection modules/settings ...
Another syndrome on this is appearing, if Outlook 2010 is closed and reopened, it will not got opened properly, but stuck on "Loading Profile". Sometimes the previous Outlook.exe is still active on the processes and a new one opened aside, so, there is two of them, and, even more, if tried to open several times, but sometimes just the newly opened process only. Anyway, Outlook 2010 will not got opened, probably about for the same net connection problem as described above.
OK, I have found some corrective hints, profile recreation, add-in disablings etc. other tricks and tried them, already a few times, but nothing seems to help ...
An old neighbour XP-machine on the same 4-port network switch with Outlook Express 6 and same IMAP port 143 simple settings do work all fine! So, there may not be much reason to blame the ISP/mail-provider ... Neither to blame the firewall or other programs/services, as no type of fresh/clean/safe starts do not make any difference.
And yes, one more note, the account settings test hasn't worked at all, neither the first time when establishing this account nor on any test after any correction trial!
One guess, could there be some bug on the Outlook 2010 32-bit version, used on a 64-bit Windows 7 Home Premium, causing some corruption on the net connection after one-two mail send/receive attempts? And, where/how to obtain an Outlook 2010 64-bit version?
Please, give any hints to this desperate ocean-deep research on these MS products ...
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The error value ‘0x80070005’ means ‘Access Denied’.
This means that an attempt has been made to update part of the registry that you do not have permissions to update. There are many parts of the registry that can be read but not updated (except by ‘system’ or the local administrator).
Possibly Remedies:
Check that you have local administration rights.
If you are a local administrator (i.e. a member of the ‘Administrators’ group on the workstation) then most likely someone or some application has modified (intentionally or unintentionally) the permissions on one or more registry keys and that this is preventing access
(Alternately, it may be that the key that is failing is one that normally only ‘system’ can update.) To identify which registry key is causing the problem use Regmon (a freeware tool published by System Internals). Use Regmon to capture all registry access when regsvr32 is run. If an ‘OpenKey’ request fails with ‘Access Denied’ (which is listed by Regmon as ‘ACCDENIED’) then run regedt32 and check the permissions on that registry key. If necessary change the permissions on the key to grant local Administrators ‘Full Control’. They try registering the COM object again. The only times I have encountered this problem it affected more than one key, so be prepared to repeat this process.
to get the tools you can go to the following site:
http://www.cryer.co.uk/glossary/r/regmon.htm
http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
This means that an attempt has been made to update part of the registry that you do not have permissions to update. There are many parts of the registry that can be read but not updated (except by ‘system’ or the local administrator).
Possibly Remedies:
Check that you have local administration rights.
If you are a local administrator (i.e. a member of the ‘Administrators’ group on the workstation) then most likely someone or some application has modified (intentionally or unintentionally) the permissions on one or more registry keys and that this is preventing access
(Alternately, it may be that the key that is failing is one that normally only ‘system’ can update.) To identify which registry key is causing the problem use Regmon (a freeware tool published by System Internals). Use Regmon to capture all registry access when regsvr32 is run. If an ‘OpenKey’ request fails with ‘Access Denied’ (which is listed by Regmon as ‘ACCDENIED’) then run regedt32 and check the permissions on that registry key. If necessary change the permissions on the key to grant local Administrators ‘Full Control’. They try registering the COM object again. The only times I have encountered this problem it affected more than one key, so be prepared to repeat this process.
to get the tools you can go to the following site:
http://www.cryer.co.uk/glossary/r/regmon.htm
http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
ASKER
OK, sorry, had to open the command window as Admin ...
Will come back in an hour or so, after having possibility/permission to reboot the machine.
Will come back in an hour or so, after having possibility/permission to reboot the machine.
ok cool let me know of the outcome
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Check to see if there is a newer driver for your nic
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
OK, I did try the FW and AV disablings already before lainNIX's reply, but for some reason didn't get the problem cured those times, but after his reply still re-checking the hint.
glad you got it sorted in the end. i mention AV simply because i had been caught with that before, McAfee Enterprise has a nasty habit of blocking port 25 by default, if you don't sort your policies......kind of hard to use Exchange without it!!
ASKER
OK, I did try the FW and AV disablings already before lainNIX's reply, but for some reason didn't get the problem cured those times, but after his reply still re-checking the hint.
ASKER