I seem to have problems using WinRunner through Terminal Server Client. I'm working on Windows2000 with WinRunner 6.02. Sometimes WinRunner doesn't recognize a window anymore (the GUI gives the mic_unknown_class instead of a dialog).
Does anyone already has this kind of problems before?
A couple of things to check...
1) The terminal emulator functions (TE) in WinRunner are available only if you use the Y2K add-in or WinRunner EURO. If you're attempting and TE functions, that would be why.
2) mic_unknown_class usually comes up when WR doesn't recognize and object or window. This often happens when you open WinRunner AFTER an application (or in the case maybe your terminal emulator).
Not sure if I'm anywhere near what you're experiencing, but hope that helps.
Thanks for your interest, but I'm not talking about Terminal Emulator here.
I'm talking about the remote controller "Terminal Services Client" from Microsoft. This is a tool that makes it possible to access a server remotely by sending screensnapshots. I need to test a web-application with a login dialog box. The window is already in the GUI and recognized by WinRunner. Sometimes WinRunner stops recognizing the dialog window. I open the site multiple times during my regression tests and I never know when WinRunner is going to stop recognizing the dialog window.
It is even possible that after a while WinRunner recognizes the window again.