Outlook 2010 not creating Stream_AutoComplete file

[doubleohalex]

Hey Everyone,

Ran into a strange issue today. I have a client running Outlook 2010, we are currently in the process of setting them up with a new Outlook Profile. Within Outlook AutoComplete seems to work as expected...however no Stream_AutoComplete .dat file is being created in the RoamCache folder by the new profile. The original "Outlook" profile did create the autocomplete file, however this was all setup before we took them over as a client. I have no knowledge of what has gone on with the machine from initial installation until now. We are currently doing an unplanned migration from GoDaddy Hosted Exchange to Office 365.

Here are the steps I've tried so far:

• Cleared the autocomplete cache
• Created multiple new profiles with the same results
• Renamed the RoamCache folder and let Outlook recreate it. All other stream files are created, just not the autocomplete file
• Disabled and re-enabled the autocomplete functionality from Outlook settings
• Ran Outlook in safe mode

Short of reinstalling Outlook, I am out of ideas. In the new profile, a new autocomplete cache is built. As in, I can send a couple of emails and the addresses will be present within Outlooks autocomplete. However, this is all happening with no Stream_Autocomplete file. It seems to be a fairly common issue based on what I've researched..however I have yet to find anyone with a resolution.

I'm wondering if anyone on here has encountered this before?

 

[YeOldeStonecat]

Toggle Outlook cached mode to non cached..blow away old OST, then put back to cached mode. See if it resycs locally. With Exchange, Outlook 2010 and higher now store the main nickname cache up in the mailbox on Exchange.

 

[doubleohalex]

Toggle Outlook cached mode to non cached..blow away old OST, then put back to cached mode. See if it resycs locally. With Exchange, Outlook 2010 and higher now store the main nickname cache up in the mailbox on Exchange.

Thanks. Tried this after I posted, also replicated new profiles. No luck. I thought with Outlook 2010 it stored the autocomplete local in the stream*.dat files as well up in the data store...hrm. Strange enough, this issue is persistent on 2 machines at this client and the other 2 machines worked just fine. Same specs, same O365 account...same everything.

 

[YeOldeStonecat]

I believe it is supposed to "sync" to the local, cached stream file. And, like the OST, that local stream file is supposed to sync with primary copy on the mailbox. So if you have several computers sharing the same mailbox...in theory, that autocomplete is supposed to be the same across all computers..and in constant sync.

...on theory....

...heh. I've also run across it not migrating well, and it's become too buggy and time consuming to bother with.

Since Outlook and Exchange 2010...I don't migrate the autocomplete cache anymore....it's gotten too time consuming. Used to be easy peasy with the old .NK2. Only a few end users moan about it..and quickly forget it as their new cache file quickly grows from scratch, they get over it.

 

[doubleohalex]

I believe it is supposed to "sync" to the local, cached stream file. And, like the OST, that local stream file is supposed to sync with primary copy on the mailbox. So if you have several computers sharing the same mailbox...in theory, that autocomplete is supposed to be the same across all computers..and in constant sync.

...on theory....

...heh. I've also run across it not migrating well, and it's become too buggy and time consuming to bother with.

Since Outlook and Exchange 2010...I don't migrate the autocomplete cache anymore....it's gotten too time consuming. Used to be easy peasy with the old .NK2. Only a few end users moan about it..and quickly forget it as their new cache file quickly grows from scratch, they get over it.

That is basically where I'm at. I hardly ever migrate it over, only when requested. Of course it went fine on the first 2 computers and the 2 users with the issue "need" it. Everyone is on a separate mailbox as well. It seems to be a common issue and Microsoft went "eh, we fixed it in Office 2013".

The only reason I even stressed was because it's a new client. GoDaddy switched them to Office 365 in the middle of our onboarding process with no warning (no warning to us at least). Oh well lol

 

[Majestic]

In order for this to work the autocomplete file needs to be the same name as the new .ost file on exchange so verify that. That said, you can also try using Nk2edit from Nirsoft.net, http://www.nirsoft.net/utils/outlook_nk2_edit.html. Reexport the autocomplete file to a new nk2 file, put it in the roaming cache directory then from the run prompt type "outlook /importnk2". That should sync up online.

Regards,

Majestic

Hey Everyone,

Ran into a strange issue today. I have a client running Outlook 2010, we are currently in the process of setting them up with a new Outlook Profile. Within Outlook AutoComplete seems to work as expected...however no Stream_AutoComplete .dat file is being created in the RoamCache folder by the new profile. The original "Outlook" profile did create the autocomplete file, however this was all setup before we took them over as a client. I have no knowledge of what has gone on with the machine from initial installation until now. We are currently doing an unplanned migration from GoDaddy Hosted Exchange to Office 365.

Here are the steps I've tried so far:

• Cleared the autocomplete cache
• Created multiple new profiles with the same results
• Renamed the RoamCache folder and let Outlook recreate it. All other stream files are created, just not the autocomplete file
• Disabled and re-enabled the autocomplete functionality from Outlook settings
• Ran Outlook in safe mode

Short of reinstalling Outlook, I am out of ideas. In the new profile, a new autocomplete cache is built. As in, I can send a couple of emails and the addresses will be present within Outlooks autocomplete. However, this is all happening with no Stream_Autocomplete file. It seems to be a fairly common issue based on what I've researched..however I have yet to find anyone with a resolution.

I'm wondering if anyone on here has encountered this before?

 

[doubleohalex]

In order for this to work the autocomplete file needs to be the same name as the new .ost file on exchange so verify that. That said, you can also try using Nk2edit from Nirsoft.net, http://www.nirsoft.net/utils/outlook_nk2_edit.html. Reexport the autocomplete file to a new nk2 file, put it in the roaming cache directory then from the run prompt type "outlook /importnk2". That should sync up online.

Regards,

Majestic

Thanks. This was essentially done using the suggested contacts feature in Outlook 2010 to rebuild autocomplete in Exchange. It doesn't solve the original issue though, Outlook is not creating a local autocomplete file for this particular machine. It does so just fine for every other machine at this site...all using O365 and Outlook 2010. After speaking with Microsoft, they basically said its a bug with Office 365 and Outlook 2010. Its apparently fixed in Outlook 2013.