I am new to citrix env.
When i run a PB application on Citrix environment, for a particular screen PB appl gets crashed without any error for the particulat screen. If I check the same in PB spource it is working fine. I dont know why it is happening.
Can you help me?
The multi-monitor hooks are the most common cause of unexpected behaviour on Citrix servers. So try adding an exception into the registry for your application to disable Citrix multi-monitor hooking to see if that helps. The following article describes how to do this:
http://support.citrix.com/article/CTX129712
Edit: for further ideas.
If disabling the MM hooks doesn't help, the only other thing I can think of is to check what DLLs are loaded in the process when it crashes. Check the stack dump you get from your crash and look at all the loaded DLLs, e.g. using Windbg to inspect your dump you can use the following commands:
http://windbg.info/doc/1-common-cmds.html#10_modules
Look for any Citrix DLLs loaded in the process space. You can then look for those files in the file system and temporarily rename them to hide them (so they won't get loaded into your process). Note: most Citrix DLLs live in C:\Program Files (x86)\Citrix\system32.
If that doesn't help all I can suggest is putting debugging tools on a Citrix server and debugging the app.
Related
I've taken a GPUView trace on one machine running Windows 10 but want to analyze the trace on a different machine running Windows 7. When I try to open the trace file, merged.etl, using GPUView I see the message:
This etl file has data that was captured on a version of the OS that is different from the current OS. The data may not be displayed correctly or expose other side effects in GPUView.
Would you like to continue loading this file anyway?
If I choose to open the trace anyway GPUView opens but there is nothing to view.
I know I should be able to view traces this way but I don't know the magic sauce to make it work. Does anyone know it?
As a last ditch effort, after finding nothing for this error online, I tried pointing GPUView to a folder containing symbols from the OS the trace was captured but this doesn't have any effect.
Thank you,
Lawrence F.
I discovered this was happening due to using different GPUView versions on the two machines in question. I thought I had used the same version but it turns out I had serveral. I removed all the old version and installed the Windows 10 SDK on each machine (includes GPUView). This allowed me to view the trace on the Windows 7 host
Recently forced upgraded to windows 10 by microsoft. Windows Start and cortana froze. Searched google and from powershell ran
Get-AppXPackage -AllUsers | Foreach
{Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
Now lot of my windows application have disappeared. They show up with #{AppPackageName} in taskmanager or when searched using cortana for example #{Microsoft.ZuneMusic_2019.6.15131.0_neutral_~_8wekyb3d8bbwe}. I can not remove these app using any command like
Tried to install store app manually and get error Merge Failure : error 0x80070003 : Cannot register the Microsoft.WindowsStore_2015.21.25.0_x64__8wekyb3d8bbwe package because there was a merge failure with the following file: C:\Program Files\WindowsApps\Microsoft.WindowsStore_2015.21.25.0_neutral_split.scale-100_8wekyb3d8bbwe\resources.pri
Full log below:
Now I understand that store app is not getting add because add process is causing error or merge failure with another package (?). The problem is get/Add-AppxPackage are resolving dependency of application with package-version: Microsoft.WindowsCalculator_10.1510.13020.0_neutral_split.scale-100_8wekyb3d8bbwe
AND/OR
Microsoft.WindowsCalculator_10.1510.13020.0_neutral_split.language-hi_8wekyb3d8bbwe
My laptop c:\program files\windowsapp only has Microsoft.WindowsCalculator_10.1510.9020.0_neutral_split.scale-100_8wekyb3d8bbwe (not diff in version 13020 and 9020). Note: The version no on app is 13020 but dependent package on drive is 9020.
Second package is missing from drive (Microsoft.WindowsCalculator_10.1510.13020.0_neutral_split.language-hi_8wekyb3d8bbwe).
How to get my calculator and windows store application back.
<1>Create a new user account and Log into the new account
<2>You can also try
Running the System File Checker by running
sfc /scannow
Download files from Windows Update to replace the corrupt ones by running
DISM /Online /Cleanup-Image /RestoreHealth
You may try the following, at your own risk.
I had the same issue after trying to reinstall the apps via that powershell thingy. Fixed it and returned the apps to their out-of-box state by first wiping everything from C:\Program Files\WindowsApps and C:\Users*\AppData\Local\Packages and then reinstalling Windows over itself from the tech bench ISO (from under Windows and keeping "traditional" apps and files in place, of course). I had to use the ISO because the media creation tool wasn't cooperative at all, throwing some error at me. Just in case, the aforesaid wiping didn't cripple the vitals like the immersive control panel or something else, just the typical no start menu/dead modern apps/no right click on the taskbar items.
By the way, the whole problem started after the 1511 update. Modern apps would refuse to remember their settings, and windows shell experience host would freeze for no reason, taking the start menu and things like volume control with it. I've had this Windows installation for a couple of years now, and the system has gone pretty smoothly through the 8.0-8.1-10 update process over that time, but that 1511 screwed something big time.
I just started using the included Development Kit that came with the CRM SDK. I created a simple plugin using the Development Kit and now I cannot find a way to debug the plugin. Before i started to use the Development Kit i was able to debug the plugins i created.
I attached the debugger to the w3wp.exe process but the debugger doesnt break on the breakpoint at all.
Moreover my assembly is registered on Database and with Isolation set to None
Any help would be greatly appreciated. Thank you
There is another way to debug (instructions toward the end), by copying the PDB to the CRM /bin and attaching to the asynchronous (or sandbox) worker process. I'm not sure which way is easier...I will have to try Piyush's way sometime, but I do not use the RegistrationTool anymore thanks to the toolkit:
Debugging works well once you follow the setup instructions, though
copying the PDB file remains a manual step. Also note, the sandbox
process (Microsoft.Crm.Sandbox.WorkerProcess) is not started until
after a plug-in is run, so you will have to invoke it (or another one)
at least once before you will be able to debug.
Some time back I wrote an Article to debug plugins in CRM 2011, this might help you out.
Debug Plugins - CRM Parking Lot
I found out what the problem was. Turns out you have to re-deploy the plugin after setting the Assembly with Isolation set to None. Then like Chris Snyder said you still have to copy the PDB file from the debug folder to the bin/assembly folder on the CRM server. Seems like that step is still manual. Will see if I can either find a way to do it automatically or just create a simble batch file to do it.
Thank you all for your help.
I know VS2012 has the ability to start the Windows Simulator right out of the editor.
What I want/need is to be able to 'tell the simulator' to start a specific app. So let's say I have a previously compiled (Metro) app, it could be C# or HTML, and I want to tell the Simulator to Start and run my specific app. Is that possible?
Let's say I'm also in a Windows 7 box, and I want to try it out. I know I can't do that on the Win7 box so I thought I would connect to a Windows8 VM via Remote Destop and either start the simulator there to see how my app works, or as mentioned before, start the simulator with my app.
So is that all possible? How would I do it? Does anybody can think of a better idea to achieve that? Say powershell to send my app to the Win8 machine?
You can find the Simulator executable at ...
C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Simulator\11.0
Looking at Windows.Simulator.exe with ILSpy, however, it appears that the only startup command it looks for is /Minimized. If you check out OnStartup, it contains the code ...
if (App.ParseStartAsMinimized(e.Args))
{
window.WindowState = WindowState.Minimized;
}
That's the only one I could find. I also didn't find a place where it tried to access its configuration file. It does reference System.Configuration, however, so maybe some additional detective work is warranted.
After setting up WinQual and WER for the first time, I intentionally inserted a crash in a release build expecting\hoping to get the WER dialogue but instead still get the dialogue containing "runtime error! The application has requested the runtime to terminate in an unusual way...".
Everything seems to be working correctly regarding the setup of WinQual (along with all the supporting symbol server, source server,WinQual account, submitted mapping files and verified their presence my WinQual account). Now I want to verify that dump files are created, submitted to WinQual and I can retrieve them for debugging.
I verified that my PC's (XP Pro SP3) error reporting is enabled (system properties-error reporting). I figured the hard part would be setting up everything above not getting the program to actually show the WER dialogue. Is there some modification to the exe or the PC needed?
It's good to know I may not be (completely) crazy. You're right that external issues were causing problems for the WER dialogue.
I changed the crash to the code above, just in case my version was too brutal, and ran the application on three machines and it appears that the presence of Visual Studio and/or just-in-time debugging, on XP and Win7, was affecting the WER dialogue. For anyone interested this is what I saw:
XP with Visual Studio. Asked to choose a debugger and if I chose No, the program exited without the WER dialogue.
XP without Visual Studio. Displayed WER dialogue and sent the error report (yeah).
Win7 with Visual Studio. Did not crash at all.
Win7 without Visual Studio. I have not tested yet but suspect it will behave correctly.
So as you implied, a combination of the crashing code and unrepresentative testing environment were thwarting my test.
Thanks so much!
If you are using a WinForms application there is a catch handler in it's event loop that pops up a dialog and prevents Windows Error Reporting (WER) from kicking in.
This call prevents this from happening.
(http://social.msdn.microsoft.com/forums/en-US/netfxbcl/thread/176b7f8c-3efb-4e6f-8deb-c685c62629db/)
The magic line to fix:
Application.SetUnhandledExceptionMode(UnhandledExceptionMode.ThrowException);
There shouldn't be anything you need to do in the application to get it working. I suspect you've somehow managed to crash in some strange way that is not working too well with WER. Try adding a crash once the application has initialised, rather than during application startup (if that is what you're doing). I usually do something like this:
int* p=0;
*p=1;
Another possibility is that your machine isn't going to give you the same results as an end user because of the Just In Time debugger of Visual Studio, so try it on a typical end-user machine. A further possibility is that your machine is XP and WER support was at an early stage in XP and is better in Vista and Win7, so try crashing the app on a newer machine.