In Dynamics CRM 2016 On premise, whenever I try to close a Task on a specific entity I get an error.
The "close task" is a standard Microsoft button.
The error in the top reads "An error occured. Return to the startpage and try again". Not very usefull. It happens every time.
Debugging have not been helpfull since it does not catch on anywhere.
No Javascript functions are being called on that button and there are no business rules sat up for that page. There are no plugins attached either.
Any ideas what could be causing this error? Or at least how I can dig deeper. I have very little to go on.
Thanks
Related
I'm having a problem with my product.
Does anyone know the cause?
And please tell me the solution to this problem.
Execution environment
Outlook2019 build Ver 2203(15028.20204)
※Works correctly in other execution environments.
It always occurs when you follow the steps below.
1)Launch Outlook 2019.
2)Compose an email.
3)Click the "send" button.
4)An error occurs.
I tried debugging.
I Confirmed that there was a problem with the "localStorage.getItem()"API part in the source code.
I'm expecting the value to be returned, but I've confirmed that it's returned as "null".
This issue only occurs in dialogs opened with "displayDialogAsync"
What may be the cause?
[Office365 release notes]
https://learn.microsoft.com/en-us/OfficeUpdates/update-history-office-2019#retail-versions-of-office-2016-c2r-and-office-2019
[display dialog async API]
https://learn.microsoft.com/en-us/office/dev/add-ins/develop/dialog-api-in-office-add-ins
[localStorage API]
https://developer.mozilla.org/ja/docs/Web/API/Window/localStorage
I am making a windows phone 8 application and in the designer view in both blend and VS I get "Unable to determine application identity call" error as a dialog box.
From what I read on stack this is propably because of the Isolated Storage is getting run and the designer can't handle it.
I am wondering is there away I can get some line numbers or something where the errors are happening instead of having to manually go through the code?
By the time you see this message box it is already too late, the exception was caught and handled. You have to catch it when the exception is raised. Which is not so easy to do at design time.
One technique that's worth a shot is to use a debugger to debug Visual Studio itself. Start it again and use Tools + Attach to Process. Locate the first devenv.exe in the list of processes and select it. Set the Attach to: setting to "Managed (v4.5, v4.0)" and click OK. Let it trundle to find the PDBs (takes a while). Debug + Exceptions, tick the Thrown checkbox for CLR exceptions.
Switch back to the original instance of VS and do whatever you did before to trigger the error. The 2nd instance will break in when the exception is thrown. Which some luck you'll see your code on the Call Stack window. If the debugger doesn't break then repeat the exercise but attach to XDesProc.exe, the XAML designer. Good luck with it.
Isn't this
Unable to determine application identity of the caller?
or
Getting Unable to determine application identity of the caller Error
are the same topic????
Don't know, just asking...
Sorry for any inconvenience..
Just answered in my basic question.
I'm afraid, i don't know how to get exact string number, just keep in mind that Designer cant have an access to the IsolatedStorage and check all places where you're working with IsolatedStorage. Basically, what you need to do is to add to all constructors a lines
if (ViewModelBase.IsInDesignModeStatic)
return;
If you're working with MVVM Light, or
if (System.ComponentModel.DesignerProperties.IsInDesignTool)
return;
which is pretty the same but without MVVM Light.
Also, i edited my answer there.
I'm developing workflows on SharePoint 2010 using Visual Studio.
I need to catch event, when user cancel running workflow from UI.
User clicks on "Terminate this workflow now" link and I should add some logs to history of current workflow instance.
I added cancellationHandlerActivity for my SequentialWorkflowActivity, but cancellationHandlerActivity is not executed.
In MSDN I find explanation for cancellationHandlerActivity (http://msdn.microsoft.com/en-us/library/aa349442(v=vs.85).aspx) - The CancellationHandlerActivity activity contains cleanup logic for a composite activity that is canceled before all the composite activity's child activities are finished executing.
So I thought, that cancellationHandlerActivity is what I need, but on practice - I'm wrong :(
Please, give me some advice, how i can solve my problem!
I tried to find solution on the Internet, but couldn't :(
I found solution!
You can create your custom WrkStatPage and add your custom action on cancel event.
(More information about this way)
Also in Element.xml for your workflow add property
StatusUrl="_layouts/MyCustomWrkStat.aspx"
I cannot get my Outlook addin to work in release mode for OL2007 (debug works great). I created a ClickOnce installer, signed it with a custom certificate and built the installer.
Then after installation when I start Outlook 2007, it does not load and gives no notification at all. I look into the addin section where I find my addin among "inactive addins". I look to the COM addins and find it unchecked (checking it doesn't help) with the notification "Not loaded" (NOTHING ELSE).
Things I tried already:
try/catch block around my startup routine plus message output: nothing is shown
new custom signing certificate: useless
APPDATA\MS\Outlook\extend.dat deleted: to no avail
regedit setting "LoadBehaviour" 3: It is always like that, I don't have to change it
VSTO_SUPPRESSDISPLAYALERTS = 0: to no avail, nothing is shown
VSTO_LOGALERTS = 1: same here, nothing is logged
Fusion Logging: nothing is posted into the output directory
I get NO info at all what causes my addin not to load. It is driving me crazy. Can anyone point me to a solution or at least something I can still try to solve this problem?
The problem obviously occurred due to a difference between GUID and setup product key. Changing the setup product key to match the GUID enabled the addin to complain about errors again, so I could continue with debugging.
Very weird that in this case no error whatsoever was thrown.
On Windows XP when a process crashes, we get a dialog box with a link:
"To view technical information about the error report, click here."
The "click here" link brings up a whole lot of information in a window, but no obvious way to save it to a file. Is there a way? It would be very nice to be able to send that data to several different external vendors we're working with.
The only other option I see in the dialog box is to send it to Microsoft, but this crash is likely not Microsoft's fault and there is no reason to send it to them.
If you are a company, you can register with Microsoft to be able to download WER reports.
As of when you see this dialog box, you should still be able to manually attach a debugger (e.g. Visual Studio) to the crashing process and take a look at any available exception records. Alternatively, I believe you should be able to register Visual Studio to handle these crashes instead of the normal error reporting mechanism. This article seems to have more information about that option:
http://msdn.microsoft.com/en-us/library/5hs4b7a6.aspx
Hope this helps...
Maybe a bit late for '08 question, but anyway, you may use Error Report Grabber software for this task