In my legacy VB6 application,
When I try to move a column in a list the application locks up with a message that the application has stopped working, Windows is collecting more information about the problem.
The details collected indicate
Files that help describe the problem:
C:\Users\Kirsten\AppData\Local\Temp\WER3A65.tmp.WERInternalMetadata.xml
C:\Users\Kirsten\AppData\Local\Temp\WER6971.tmp.appcompat.txt
C:\Users\Kirsten\AppData\Local\Temp\WER69D0.tmp.mdmp
The problem signature in the first file shows
<ProblemSignatures>
<EventType>APPCRASH</EventType>
<Parameter0>jtJobTalk.exe</Parameter0>
<Parameter1>1.0.0.0</Parameter1>
<Parameter2>58216da3</Parameter2>
<Parameter3>mscomctl.ocx</Parameter3>
<Parameter4>6.1.97.82</Parameter4>
<Parameter5>403ad117</Parameter5>
<Parameter6>c0000094</Parameter6>
<Parameter7>0000e4c5</Parameter7>
</ProblemSignatures>
Install the controls from
https://www.microsoft.com/en-us/download/details.aspx?id=10019
to solve this problem.
Related
I created a new application with react native windows, and it works well the first (few) times I run it, however, when closing the application I always end up with the following warning:
Attempt by security transparent method 'System.Reactive.Concurrency.CoreDispatcherScheduler..ctor(Windows.UI.Core.CoreDispatcher)' to access security-critical type 'Windows.UI.Core.CoreDispatcher' failed.
I've tried this on more than one computer and all of them get the same error but I can't find a way to fix this, meaning I cant proceed with my Native project in fear that it will malfunction every day.
How do I fix this, to stop this from happening again, or is it a bug?
I'm a novice in React Native myself, but here are a few suggestions:
1) There's an issue logged in GitHub on this exact problem: https://github.com/Microsoft/react-native-windows/issues/1954
2) I personally find that I get this with command-line execution (react-native run-windows) but I don't think(?) that I've seen it when running from inside Visual Studio. Try that approach to running instead.
3) As described at GitHub - I've found that deleting windows\Debug folder before running tends to resolve the issue.
i am stuck with a problem regarding Crystal Report 13. I am working on Visual Studio 2013 developing Web Application.
Previously i've developed reports and those were working fine but after some time on web page crystal report viewer stop rendering. I tried to resolve the issue by suggestions on different forums where i need to add reference of Crystal Report 13 files in my Web.Config. After all changes the problem was not resolved. Than people suggested me to re-install redistribution package of crystal report 13, i've done the same thing now there is a new problem which is quite different. Whenever i am trying to open page it shows following error:
Server Error in '/Abcd' Application.
The document has not been opened.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Runtime.InteropServices.COMException: The document has not been opened.
I've tried many forums and different suggestions but all seems useless, i've check the appropriate rights even try after giving full rights but still at same position.
I've found the alternative solution, before i was using 13.0.21 redistribution package which was using registry dlls version 13.0.2000.0, i was facing two problems using that particular version.
1. Unable to edit rpt file, whenever i tried to open it an error appear on screen that The operations is failed or unable to complete operation (something like that i don't know exactly what the error is but the summary is this)
2. When i try to open Crystal report viewer during execution, i've come up with error which i posted earlier.
What i have done for the resolution, that i've download Crystal report developer version 13.0.21 and install it with "Run as Administrator" because i creates some entries in your registry of windows, keep in your mind to close VS during installation. After successful installation both problems are solved but u need to change the dlls version in your code from 13.0.2000.0 to 13.0.3500.0
I have an App that uses Admod and Firebase from Google. Since I am using Swift they want me to use frameworks when loading them from CocoaPods. When I try to archive/validate the App I get the error:
No suitable application records were found. Verify your bundle identifier 'org.cocoapods.GoogleToolboxForMac'
What is the correct way to provision an app that uses someone else's frameworks so it can be uploaded to iTunes Connect? I tried to find something in Apple's documentation but I haven't found anything.
UPDate:
I previously had answered my own question, since I had thought I had found a solution. My reply was:
Problem Solved. Turns out I was using an App-ID that I am having Apple look into as being corrupt. I had already created a new App-ID to prove the one I want to use is not working and retried with that and it Validates. This required a lot of help from the Google Ads Mobile SDK team. Thanks.
So the correct answer is: Now Incorrect
You should not get this error unless you are using a Bundle-ID that is not already registered on iTunes Connect, but, you should never be able to create an archive that does not have a Bundle-ID that is not already registered on iTunes Connect. So this is caused by an abnormal situation.
This is no longer true
I used my new working project and got 4 whole builds out of it and into iTunes Connect. In the process I was trying to clean up the mess caused by trying to solve this problem, like loosing my git history. I tried to modify my old App to get it to work and without modifying my new working project, But my new project started failing with the above error. I even used my time machine and went back to the directory as it was when I made the last build, but no help. So, any answers?
Further Update:
I pulled all the code related to Google Firebase and Admob out of the code and removed the cocoaPods and Archived/Validated and now I get the error:
You must supply a CFBundleIdentifer for this request.
Which is the error message I was getting with my other App-ID that tracked that App-ID in iTunesConnect. This time it does not track the App-ID so it must be something in my project. Will report what I find.
UpDate:
I think Apple has been modifying their code for validation at the same time I was trying different things. At one point it told me I was using CFBundleSignature instead of CFBundlePackageType set to APP and I fixed this and got the code to validate. Understand I am copying complete projects and renaming everything to debug this problem, so this must have come from the original program. I ended up with a project that was renamed from my original but archived/validated but when I went to compile for Test I got errors that I debugged until I got lots of Mach-O link errors. I decided to complete the loop and go back to my original code and try using the new Bundle-ID which points to the new App-ID, the one that works, and add all the knowledge I have learned. But when I get it done I have an project that can test but does not validate. The only difference is this project has the old identifier which has the same name as the suffix of the App-ID that has a bug.
Am I missing something?
Final UpDate?
On a whim I renamed the Scheme file to be the same as my Suffix to the Bundle-ID and I got my original Project to Validate! I have worked on this for over a month and you might not believe the astonishment I feel in this.
Back to Unit Test!
I have come to the conclusion that the Identity of the App, the name at the far top of the right side Utilities window, has something to do with the way iTunes Connect validates the App. This is the name in the left hand column of the Organizer window. It is like it overrides the suffix of the Bundle-ID and since I can't use that Identifier because the associated App-ID is corrupt. Or the name of the Scheme.
First off, ScintillaNET v2.6 was installed as a control and I have been able to use it and compile, so I assume the installation is ok:
This app is targeting the full .NET 4.0 framework, not the client profile)
Environment variable
ScintillaNT folder content
The error message:
The code triggering the error:
The error happens on the second line when I "step-in" the load method. Looks completely unrelated, but highly reproducible: the error always happens at that exact step.
The problem turned out to be a corrupted XML file. I still don't know why the crash page was all about ScintillaNET, but it appears this had nothing to do with Scintilla.
I am not deleting this question because I could not find any indication that this could happen (errors in different parts of the code triggering a Scintilla error page) and it would have saved me a lot of time trying to track back the "scintilla" problem.
I have just added ILCrashReporter-NG to my application to log application crashes. Unfortunately it seems to have broken my Sparkle updates (Sparkle gives an error when the appcast has downloaded and the Install button is clicked). I have added the ILCrashReporter launchReporterForCompany: report addr: method to applicationDidFinishLaunching. Does anyone have any experience of implementing these two frameworks together and if so, is this a problem that you encountered.
I use the two together without any problems. What's the error that you get? Did you change anything else besides adding Sparkle?
The only time I've had the update fail, as you describe, was after changing my bundle id so that the bundle id in the update and the application didn't match.