Dang. Might not be a bad idea in light of active directory; I'm the only one not joined to it for some reason because it's taken a while for people to send me files. Anyway ... I've looked around on the internet and I seem to find a rather lot of people having similar issues; all related to Office 2016 and this particular DLL. Is that an Office or Windows related file? I've not seen it show up in any other error messages. And it seems with Windows 10 in general reimages happen more frequently. Starting to Wonder whether Microsoft did that on purpose to force everybody to keep their systems clean? Is it just me who keeps noticing this?
From: [email protected] [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Friday, June 02, 2017 10:24 AM To: [email protected] Subject: [NTSysADM] RE: Nasty Outlook 2016 and Windows 10 issue If ShellCommon is faulting, that's an even better reason to image the machine. You didn't mention that before. How long does it take you to image a machine? I would hope not more than 30 minutes... From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Katherine M. Moss Sent: Friday, June 2, 2017 9:47 AM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] RE: Nasty Outlook 2016 and Windows 10 issue In light of the advice you guys provided yesterday, I deleted everything out of appdata\Roaming\Outlook, both the xml files and the srs files. I'm still getting this weird profile thing where when it creates a profile, it is autopopulating those fields from my office 365 account (where did it get them from on a new office install?) and then hanging once again when asking for the credentials for the Exchange account. Not to mention, ShellCommon.dll keeps crashing; I actually paid attention to that now; sounds like a DLL issue rather than a specific office issue at this point. Reimaging the machine seems a bit overkill for just an issue with Office 2016. Or not doing it manually, at least. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Thursday, June 01, 2017 9:38 AM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] RE: Nasty Outlook 2016 and Windows 10 issue They should be recreated for the proper contents of the new profile. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Katherine M. Moss Sent: Thursday, June 1, 2017 9:25 AM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] RE: Nasty Outlook 2016 and Windows 10 issue If I move them, though, will they be re-created upon the creation of the new profile? And could those have anything to do with why Outlook is crashing for this account? In that case it's just one computer. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Thursday, June 01, 2017 9:20 AM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] RE: Nasty Outlook 2016 and Windows 10 issue In appdata for Outlook are a few XML files where OST and PST files are stored. Before you create a new profile, you should save-off those XML files (put them in a different folder). They are used by Outlook 2016 to build the profile instead of the PRF files that prior versions of Outlook used. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Katherine M. Moss Sent: Thursday, June 1, 2017 8:56 AM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] Nasty Outlook 2016 and Windows 10 issue Hi all, This might end up on the Exchange list, but until then, it looks like a different issue. I have recently reinstalled Office 2016 in light of a crashing Outlook when I went to set up this email address inside. Upon reinstall, I created a new profile, (the "connect Outlook to Office 365" dialogue needs to go the hell away, if you ask me), selected connect to a different account, and then all of the fields are autopopulated with values from my other email account which is indeed Office 365. If this is a brand new office install and my computer is set up with a local account, from where is Outlook even pulling values from my Microsoft account anyway? Not sure whether the two issues are related, but after correcting the autopopulated fields to match the values for this account (on premise Exchange server 2016), I'm having an annoying thing happen where the credentials prompt just hangs for ever and ever. Hence I'm having to use the Windows 10 mail application until I can resolve the issue. It's only on one computer where it happens; this one is fine, and my other laptop is fine. It's only my newer primary laptop where this is happening. Someone else I know is having the same issue, and autodiscover is set up correctly. Any other advice?
