Hi Jason,
We received some unsure troubleshooting from Microsoft & the issue is outstanding but here's what we've heard/found.
- Microsoft believes it's a Citrix issue
- Citrix believes it's a Microsoft issue
- Certain 3rd party applications in GP may block the connection when working via Citrix (this is what is believed to be ultimately blocking our connection but not yet confirmed). Here are the apps in our broken environment that we do not have in our working environment which is also 2010.
- Rockton Smartfill
- Cultura Cinch
- GP Power Tools
A few troubleshooting steps that we received along the way were:
1.) Run this process monitor & take a look through the logs for issues (or forward to Microsoft/Partner). -
technet.microsoft.com/.../bb896645.aspx
Here are the provided instructions:
1. Once the file is downloaded, extract the file and double click the ProcMon.exe file to launch the program.
a. In process monitor click ”File>Capture events” to stop the logging.
2. Click “Edit> Clear Display”.
a. In GP get right to the point before the issue occurs.
b. In Process monitor click “File>Capture Events” to start the logging again.
c. In GP recreate the issue.
3. As soon as the error message comes up Click File>capture Events in Process monitor again to cancel the logging.
4. Click “File > Save”.
5. Save the file in CSV format and zip the file. Once this is completed it can be forwarded to me for review.
2.) Grant user security access to reg keys located on the client server(s) @
- HKEY_Local_Machine\System\CurrentControlSet\Services\ASP.NET_2.0.50727\Names
- HKEY_Local_Machine\System\CurrentControlSet\Services\ASP.NET_4.0.0303129\Names
- HKEY_Local_Machine\System\CurrentControlSet\Services\ASP.NET_64_2.0.50727\Names
3.) Try this workaround
1. Log out of the domain Administrator's GP session and drill backs will begin working for all non-Admin users on that machine.
In English, have all users exit any RDP sessions directly on involved SQL & client servers and try the process again. This made no difference for us.
All in all, we're still in the same place that we started. The next steps will be do install another instance of GP without any 3rd parties and try the drill-back. From there, we may be able to identify specifically which 3rd party is causing the issue.
Share
Report
All responses (
Answers (
5,985
