Random WAM error 135011 for small % of users in WVD when logging into Office Apps

%3CLINGO-SUB%20id%3D%22lingo-sub-2594395%22%20slang%3D%22en-US%22%3ERandom%20WAM%20error%20135011%20for%20small%20%25%20of%20users%20in%20WVD%20when%20logging%20into%20Office%20Apps%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2594395%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20a%20very%20small%20%25%20of%20users%20that%20will%20receive%20a%20WAM%20error%26nbsp%3B%3C%2FP%3E%3CH1%20id%3D%22toc-hId-1390939280%22%20id%3D%22toc-hId-1414862229%22%3EError%20code%20135011%3C%2FH1%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESays%20the%20device%20is%20disabled%20within%20the%20WVD%20session.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWord%20%26amp%3B%20Excel%20will%20open%20but%20the%20username%20will%20have%20a%20yellow%20sign%20next%20to%20it%20and%20then%20the%20program%20will%20crash%20stating%20the%20Office%20app%20can't%20be%20used.%20A%20couple%20users%20who%20had%20this%20issue%20suddenly%20had%20it%20go%20away%2C%20others%20it%20is%20lingering.%20The%20image%20has%20proper%20ProPlus%20with%20the%20registry%20entry%20for%20registration.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOutlook%20won't%20open%20at%20all.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E0%20Information%20on%20why%20this%20is%20occurring%20and%20its%20extremely%20frustrating%2C%20I've%20swapped%20the%20users%20between%20E3s%20and%20E5%20licenses%20and%20sometimes%20that%20fixes%20other%20times%20it%20didn't.%20I've%20also%20tried%20the%20%22sign%20user%20our%20of%20everywhere%22%20in%20office%20365%20with%20mixed%20results.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyone%20have%20any%20bright%20ideas%20how%20to%20fix%20this%20without%20having%20to%20waste%20time%20with%20MSFT%20tier%201%20support%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2595546%22%20slang%3D%22en-US%22%3ERe%3A%20Random%20WAM%20error%20135011%20for%20small%20%25%20of%20users%20in%20WVD%20when%20logging%20into%20Office%20Apps%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2595546%22%20slang%3D%22en-US%22%3E%3CP%3EFigured%20this%20out%20-%20there%20was%20a%20wvd%20host%20computer%20object%20in%20AD%20that%20was%20still%20present%20and%20was%20in%20a%20%22disabled%22%20state%20despite%20having%20removed%20that%20host%20with%20Nerdio%20WVD%20Manager.%20Guessing%20due%20to%20some%20changes%20we%20made%20this%20got%20hung%20up%20and%20never%20deleted%20by%20the%20logic%20app%20used%20by%20Neriod%20and%20for%20w%2Fe%20reason%20these%20users%20were%20still%20tied%20to%20this%20stale%20entry.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20reviewed%20the%20sign-in's%20for%20the%20user%20inside%20AAD%20which%20showed%201%20Office%20365%20Suite%20Failure%2C%20and%20then%20checked%20the%20device%20GUID%20via%20the%20devices%20tab%20on%20that%20alert.%20This%20then%20led%20me%20to%20the%20stale%20computer%20entry%20which%20showed%20disabled.%3CBR%20%2F%3E%3CBR%20%2F%3ESolution%20was%20deleting%20the%20computer%20object%20or%20if%20you%20can't%20do%20that%20make%20sure%20its%20enabled%20and%20not%20disabled%20in%20AD%2FAAD%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

I have a very small % of users that will receive a WAM error 

Error code 135011

 

Says the device is disabled within the WVD session.

 

Word & Excel will open but the username will have a yellow sign next to it and then the program will crash stating the Office app can't be used. A couple users who had this issue suddenly had it go away, others it is lingering. The image has proper ProPlus with the registry entry for registration.

 

Outlook won't open at all.

 

0 Information on why this is occurring and its extremely frustrating, I've swapped the users between E3s and E5 licenses and sometimes that fixes other times it didn't. I've also tried the "sign user our of everywhere" in office 365 with mixed results.

 

Anyone have any bright ideas how to fix this without having to waste time with MSFT tier 1 support?

1 Reply

Figured this out - there was a wvd host computer object in AD that was still present and was in a "disabled" state despite having removed that host with Nerdio WVD Manager. Guessing due to some changes we made this got hung up and never deleted by the logic app used by Neriod and for w/e reason these users were still tied to this stale entry.

I reviewed the sign-in's for the user inside AAD which showed 1 Office 365 Suite Failure, and then checked the device GUID via the devices tab on that alert. This then led me to the stale computer entry which showed disabled.

Solution was deleting the computer object or if you can't do that make sure its enabled and not disabled in AD/AAD