GPA 2.2: I get this error message: "Server rejected connection"

[Neal_Pierman]

(the original post reporting this problem was appended to another thread, but I've moved this to a new thread as it's a new issue with GPA)

[Michael_Scholz]

I am experiencing this problem now. Latest drivers: check. Latest BIOS: check. GPA: 2.2

details:

Server rejected connection


Windows XP Professional, 32-bit DEP disabled
Num Processors: 1
Memory: 2013MB
Driver 0:
Device: Intel G41 Express Chipset
Provider: Intel Corporation
Date: 10-19-2009
Version: 6.14.10.5160
VendorId: 8086
ProductId: 2e32 (Eaglelake)
Stepping: 3
No support for GPA Instrumentation
GPA install directory: C:Program FilesIntelGPA v2.2
GPA version: 2.2.93736

Server rejected connection

[Michael_Scholz]

Immediately after I posted this - it started to work. But my issue is not resolved. It's happening again today, and I don't know why, or what is different between now and then. And when it did work, it was not stable. Example crash report (one of many) included:

Intel GPA Error Report - Please report this error at http://www.intel.com/software/gpa

The target application has exited.


Windows XP Professional, 32-bit DEP disabled
Num Processors: 1
Memory: 2013MB
Driver 0:
Device: Intel G41 Express Chipset
Provider: Intel Corporation
Date: 10-19-2009
Version: 6.14.10.5160
VendorId: 8086
ProductId: 2e32 (Eaglelake)
Stepping: 3
No support for GPA Instrumentation
GPA install directory: C:Program FilesIntelGPA v2.2
GPA version: 2.2.93736



Windows XP Professional, 32-bit DEP disabled
Num Processors: 1
Memory: 2013MB
Driver 0:
Device: Intel G41 Express Chipset
Provider: Intel Corporation
Date: 10-19-2009
Version: 6.14.10.5160
VendorId: 8086
ProductId: 2e32 (Eaglelake)
Stepping: 3
No support for GPA Instrumentation
GPA install directory: C:Program FilesIntelGPA v2.2
GPA version: 2.2.93736

The target application has exited.

[Neal_Pierman]

Hello,

I'm trying to figure out whether you have one or two problems here. I'll assume that both are related, and have to do with starting or maintaining the connection between the target and client systems. In particular, nothing stands out as a "smoking gun" for a simple solution, so we'll need to determine whether the issue is with GPA, your connection, or your application being analyzed.

So a couple of things to look at here (either things that I've seen or heard of, or are mentioned in the GPA Release Notes):

• When running in dual-system mode, are both systems on the same LAN? Are one or both systems connecting via a VPN? One simple thing to try to improve connectivity is to connect an ethernet cable between the two systems (bypassing any routers or switches), and the operating system will automatically setup an internet connection between the two (and it's a pretty fast and reliable connection!).
• Do you have wireless enabled (independent of whether you are using wireless to connect the systems)? If so, please disable wireless entirely, as we've seen connection issues with wireless connections only or even having both wired and wireless connections.
• Have you tried running in single-system mode? If so, is there any difference in the behavior (that is, a change in the frequency of lost connection issues)?

Depending upon your answer to the above, I may need the answers to these questions as well:

• Do you have anti-virus and/or firewall software enabled? If so, does the behavior change when you disable these?
• Have you attempted to capture a frame in a different manner (such as within GPA System Analyzer and/or using the hot key function)? If using a hot key, have you tried using a different combination (as the GPA Monitor's use of a specific hot key combination may interfere with the operation of other applications).
• From what you said, it appears that the problem occurs sometimes, but not others. When it does occur, does it occur at the same time or when doing a specific operation? Have you tried different applications (such as gpasample.exe in the GPA install directory), and do the same issues occur with these?
• Do you know if the application you are testing is making multi-threaded calls to the DirectX graphics API?
• Does the application utilize any copy protection, anti-debugging, or non-standard encryption?
• Does the likelihood of getting/maintaining a connection appear to change when rebooting and/or restarting the GPA Monitor application?

Hopefully your answers to these questions will help us understand the underlying issue and resolve it quickly!

Thanks for using GPA, and for reporting the issues here.

Regards,

Neal

[Michael_Scholz]

so it works today, although broken yesterday, and the machine hasn't been rebooted. Truely an intermittent issue. I expect it will come back next time I really need to use GPA, I'm on pix at the moment.

1. I haven't tried dual-system mode, I installed GPA on another system but haven't gone the step of trying yet.

2. All tests were done on a single system.

3. Not running antivirus. more or less default xp firewall settings, there's no popups and msvcmon works ok.

4. wireless? No, these are desktop pcs.

5. The system monitor's hot key functionality never worked for me. Since the application has a few of its own hooks, those strokes may or may not be bubbling down to your hook; I wasn't worried about it. For pix, cntrl-shift-f5 does work. The other apps won't launch during the problem effect, so no way to try alt capture methods.

6. Inconclusive, although the failure to connect happens before program start, so I don't think it's a test target issue. The failure happens consistently at connection to monitor time.

7. It's a many threaded api, but as far as I've seen all DirectX calls are properly executed from their thread only. Note, it's not the first main thread, though.

8. The application does have a dongle check, but I've got the dongle plugged in, and it hasn't been a problem with regular debugging. I doubt that's a factor. No other copy protection, anti-debugging, or encryption that I'm aware of.

[Neal_Pierman]

Thanks for the quick response...

A couple more things to try...

1. To eliminate the potential that there's a conflict with applications trying to use the same key combination, can you try setting the GPA Monitor hot key to something else and see if this helps or not? Try something not likely to be an issue, such as , for example.
2. If when you attempt to connect and get an error, would you be able to restart the GPA Monitor utility, and see if this "clears" the connection (that is, you are able to successfully connect the next time you run GPA)?
3. Does the problem also occur when running gpasample.exe from the GPA installation directory? If you get the same error, then this helps us eliminate the specific application as being part of the issue.
4. In your DocumentsGPA_2.2 directory there's a file named "ServerLog" -- please include a copy of that file here as well (if it's really long, see if you can make some judicious edits to get it to be a reasonable size).

Thanks!

Neal

[Michael_Scholz]

The thread is misnamed. To review, when attempting to connect to monitor with Intel GPA 2.2.98599, the dialog instapops 'Intel - GPA Error' dialog, text of "Instrumented driver is not installed. Please install the latest driver from http://downloadcenter.intel.com.

Recent I've tried updating GPA, disabling firewall, running gpasample instead of my program, to no avail.
Here's the logs:

Intel GPA Error Report - Please report this error at http://www.intel.com/software/gpa

Cannot initialize data collector.


Windows XP Professional, 32-bit DEP disabled
Num Processors: 2
Memory: 2013MB
Driver 0:
Device: Intel G41 Express Chipset
Provider: Intel Corporation
Date: 10-19-2009
Version: 6.14.10.5160
VendorId: 8086
ProductId: 2e32 (Eaglelake)
Stepping: 3
No support for GPA Instrumentation
GPA install directory: C:Program FilesIntelGPA v2.2
GPA version: 2.2.98599



Windows XP Professional, 32-bit DEP disabled
Num Processors: 2
Memory: 2013MB
Driver 0:
Device: Intel G41 Express Chipset
Provider: Intel Corporation
Date: 10-19-2009
Version: 6.14.10.5160
VendorId: 8086
ProductId: 2e32 (Eaglelake)
Stepping: 3
No support for GPA Instrumentation
GPA install directory: C:Program FilesIntelGPA v2.2
GPA version: 2.2.98599

Cannot initialize data collector.
Instrumented driver is not installed.

[Philipp_G_Intel]

Thanks for information Michael, we has sent it to GPA team and will update you on the progress.

[Neal_Pierman]

Hello again...

So it appears that you now have a completely different error occuring when you've updated the build of GPA that you are using. Is the appearance of this error consistent, and therefore keeps you from using the product at all now?

What's strange is that the error you are now seeing is something that was a driver bug that was supposedly fixed about 6 months or so ago, and to have it come up again is not what I was expecting.

The one thing that I was wondering is whether you could try installing the driver again, but instead of downloading the 6.14.10.5160 version (which you have now), try either the 6.14.10.5189 driver and/or the 6.14.10.5132 version -- and see if this makes a difference.

And last but not least, also go into your BIOS setup and see if there is an option to change the setting of something called MCHBAR.

thanks for your patience on this...

Regards,

Neal

[Michael_Scholz]

I've tried the different drivers, with no improvement. It worked once, as I sent on email, but it's not working today when I need it. No setting for MCHBAR in the bios. Any ideas or progress intel-side?

Intel GPA Error Report - Please report this error at http://www.intel.com/software/gpa

Cannot initialize data collector. Windows XP Professional, 32-bit DEP disabled Num Processors: 2 Memory: 3037MB Driver 0: Device: Intel G41 Express Chipset Provider: Intel Corporation Date: 11-30-2009 Version: 6.14.10.5189 VendorId: 8086 ProductId: 2e32 (Eaglelake) Stepping: 3 No support for GPA Instrumentation GPA install directory: C:\Program Files\Intel\GPA v2.2\ GPA version: 2.2.98599 Windows XP Professional, 32-bit DEP disabled Num Processors: 2 Memory: 3037MB Driver 0: Device: Intel G41 Express Chipset Provider: Intel Corporation Date: 11-30-2009 Version: 6.14.10.5189 VendorId: 8086 ProductId: 2e32 (Eaglelake) Stepping: 3 No support for GPA Instrumentation GPA install directory: C:\Program Files\Intel\GPA v2.2\ GPA version: 2.2.98599

Cannot initialize data collector. Instrumented driver is not installed.

[Neal_Pierman]

Hello,

The biggest issue has been acquiring a similar configuration to what you have to duplicate the problem you are encountering.

However, I have a meeting with the driver team tomorrow morning and I will check what progress they've made, and then let you know where things are at.

Thanks for your patience!

Regards,

Neal

[Neal_Pierman]

Hello,

I did get a chance to talk to the driver team today and they indicated that this error message may be returned if they find a mismatch between expected hardware id's and your specific configuration (they've looked at the driver code itself and checked under what circumstances they would return this error).

Therefore, please open up the "device manager" control panel, then right-click on the graphics display adaptor, select "properties"/"details", then select "hardware id's", and include a copy of the information for us to review:

Also, we may need to remotely connect to your system (either vnc or remote desktop) if the above information is not sufficient to debug the issue(s) that you have encountered.

Regards,

Neal

[Michael_Scholz]

I'll have to learn more about my FIOS router to enable remote desktop, but I can do so if needed.

Here are the bits of info related to your request:

devid1 PCI\VEN_8086&DEV_2E32&SUBSYS_110A1565&REV_03\3&11583659&0&10
devid2 PCI\VEN_8086&DEV_2E33&SUBSYS_110A1565&REV_03\3&11583659&0&11

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{5b45201d-f2f2-4f3b-85bb-30ff1f953599}]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{5b45201d-f2f2-4f3b-85bb-30ff1f953599}\##?#PCI#VEN_8086&DEV_2E32&SUBSYS_110A1565&REV_03#3&11583659&0&10#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}]
"DeviceInstance"="PCI\\VEN_8086&DEV_2E32&SUBSYS_110A1565&REV_03\\3&11583659&0&10"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{5b45201d-f2f2-4f3b-85bb-30ff1f953599}\##?#PCI#VEN_8086&DEV_2E32&SUBSYS_110A1565&REV_03#3&11583659&0&10#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}\#]
"SymbolicLink"="\\\\?\\PCI#VEN_8086&DEV_2E32&SUBSYS_110A1565&REV_03#3&11583659&0&10#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{5b45201d-f2f2-4f3b-85bb-30ff1f953599}\##?#PCI#VEN_8086&DEV_2E32&SUBSYS_110A1565&REV_03#3&11583659&0&10#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}\#\Device Parameters]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{5b45201d-f2f2-4f3b-85bb-30ff1f953599}\##?#PCI#VEN_8086&DEV_2E32&SUBSYS_110A1565&REV_03#3&11583659&0&10#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}\#\Control]
"Linked"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{5b45201d-f2f2-4f3b-85bb-30ff1f953599}\##?#PCI#VEN_8086&DEV_2E32&SUBSYS_110A1565&REV_03#3&11583659&0&10#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}\Control]
"ReferenceCount"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{5b45201d-f2f2-4f3b-85bb-30ff1f953599}\##?#PCI#VEN_8086&DEV_2E33&SUBSYS_110A1565&REV_03#3&11583659&0&11#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}]
"DeviceInstance"="PCI\\VEN_8086&DEV_2E33&SUBSYS_110A1565&REV_03\\3&11583659&0&11"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{5b45201d-f2f2-4f3b-85bb-30ff1f953599}\##?#PCI#VEN_8086&DEV_2E33&SUBSYS_110A1565&REV_03#3&11583659&0&11#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}\#]
"SymbolicLink"="\\\\?\\PCI#VEN_8086&DEV_2E33&SUBSYS_110A1565&REV_03#3&11583659&0&11#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{5b45201d-f2f2-4f3b-85bb-30ff1f953599}\##?#PCI#VEN_8086&DEV_2E33&SUBSYS_110A1565&REV_03#3&11583659&0&11#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}\#\Device Parameters]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{5b45201d-f2f2-4f3b-85bb-30ff1f953599}\##?#PCI#VEN_8086&DEV_2E33&SUBSYS_110A1565&REV_03#3&11583659&0&11#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}\#\Control]
"Linked"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{5b45201d-f2f2-4f3b-85bb-30ff1f953599}\##?#PCI#VEN_8086&DEV_2E33&SUBSYS_110A1565&REV_03#3&11583659&0&11#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}\Control]
"ReferenceCount"=dword:00000001

[Michael_Scholz]

Whoops. Images worked after I posted. I see you want these:

PCI\VEN_8086&DEV_2E32&SUBSYS_110A1565&REV_03
PCI\VEN_8086&DEV_2E32&SUBSYS_110A1565
PCI\VEN_8086&DEV_2E32&CC_030000
PCI\VEN_8086&DEV_2E32&CC_0300

PCI\VEN_8086&DEV_2E33&SUBSYS_110A1565&REV_03
PCI\VEN_8086&DEV_2E33&SUBSYS_110A1565
PCI\VEN_8086&DEV_2E33&CC_038000
PCI\VEN_8086&DEV_2E33&CC_0380

[Neal_Pierman]

Thanks for the prompt reply... I've forwarded the info to the driver team, and hopefully a connection to the system will not be required.

Regards,

Neal

[Neal_Pierman]

I've talked to the driver team, and they would like you to run a small script to test some settings on your system, but I'll need an NDA from you before sending the script to you. I'll follow up with you offline to get this NDA created/signed.

Thanks!

Neal