After a phone call all I was getting was a meaningless copy-paste email.Īfter countless number of emails and phone calls a TeamViewer finally came back to me. No escalation as far as I could see, no communication, no updates about progress.
Not sure whether I was simply unlucky, or something has changed in TeamViewer support procedures, but this time support was horrific. I obviously opened another support ticker. After a few months exactly the same issue re-appeared (quite possibly after one of the Windows Update cycles). Eventually they released an updated version which was supposed to fix the problem. Then one of TeamViewer developers contacted me and worked together trying to find a solution. During this time I had two support tickets opened with TeamViewer technical support.įirst one was dealt with very professionally - the issue was quickly escalated to Level-3 support. The problem has been dragging on for nearly a year. Only common thing was that all machines were running Windows XP SP3 in a AD domain environment. It's probably worth mentioning that this problem was not caused by a particular network or setup - I had affected users in two completely unrelated companies, and I also had one affected machine on my own test network.
The only solution was to remove TeamViewer and install old good VNC. I didn't manage to find any patterns or any other clues which would help to fix the problem. It was an intermittent issue - only about 20% of machines were affected (although I suspect not all users reported the problem), those affected were crashing at completely random intervals, making troubleshooting very difficult. It took me a little while to link the issue with TeamViewer, but after some testing it became clear that explorer.exe crash is caused by TeamViewer. 5512, faulting module shdocvw.dll, version. The only error recorded by Event Logs was:įaulting application explorer.exe, version.
0 kommentar(er)
