Outlook in Office 365

[compcareguy]

I have a client with Office 365 installed. Recently when they turn on their computer and try to open Outlook it gives an error about the database already being open. The only way to clear the error and to be able to access outlook is to reboot the computer.

This also happens when they shut down the outlook app and re-open intermittently. I have not been able to find anything that is 365 specific in order to help this problem. I have used AutoRun in order to see if there was something else opening Outlook but have found nothing. Is anyone familiar with Office 365 that could offer some advice or links about tracking down or fixing this problem?

 

[Metanis]

Perhaps start with

http://www.technibble.com/outlook-not-responding-error/

The fact that this is Office 365 is probably not pertinent. Just troubleshoot it as any routine Outlook issue. Lots of things it could be.

 

[oldtech]

You likely have another program that is accessing outlook ( assuming they are using BCM since you said database) behind the scenes. That could be a line of business app or something like a voip integration package that displayes caller information. I know Shoretel does this with their call director that runs on the desktop.

 

[MobileTechie]

You likely have another program that is accessing outlook ( assuming they are using BCM since you said database) behind the scenes. That could be a line of business app or something like a voip integration package that displayes caller information. I know Shoretel does this with their call director that runs on the desktop.

Yeah sounds like that damned BCM to me. Most people don't even know they've got it yet alone use it but there it sits, causing problems like this.

 

[compcareguy]

Well, after going through everything else I could think of it seems that this morning the problem had intensified and spread to the Excel and Word agents. Since this was 365 it turned out that these things aren't conventional as to the details. At least from what I could find.

I ended up giving cCleaner a try cleaning out the tmp files, I even went for the hale mary with a registry cleaning with cCleaner something I only do on rare can't get it working any other way type situations, in other words not a huge fan of registry cleaners

After cleaning the startup of all non-essential desired programs and services, uninstalling toolbars/BHO's that had found their way on, then ran cCleaner rebooted and (cross fingers) all seems to be working like a charm. My guess is that the 365 Office Agents had experienced some corruption type issue and that issue remained in the tmp so each time it was loading the bad data...I may be wrong but that is the best I can figure. Not experienced with the inner details of what is different between regular Office and Office 365. First time I have had to work on it.

 

[sapikest]

Try tweAking.com tool, and check the proccesses to see what is running

 

[compcareguy]

Try tweAking.com tool, and check the proccesses to see what is running

Haven't used tweaking.com for a long time...I used autorun to see what was loading...I will give tweaking.com a shot when I get a chance...at the moment I was planning on just deleting the currently installed version of Office 365 and replace it with one of the 4 instances remaining in a new enterprise account they just got today that I have the log in information for. I am not even sure when the account that this workstation is on expires or anything...like I said was created long before I got there using a prepaid card and no one has a clue what the log in information for that account is...perhaps the uninstall will fix the problem?