(I have solved this. Posting it in case someone else is having this issue.)
I have an application that integrates with Quickbooks using the QBFC13 library. It all works great when running the application from Visual Studio. However, after publishing and installing as a ClickOnce application, the app crashes when calling the SessionManager.OpenConnection method.
The following is the EventViewer entry:
Faulting application name: ******.exe, version: 1.0.0.0, time stamp: 0x5c9bc8e2
Faulting module name: ucrtbase.dll, version: 10.0.17763.348, time stamp: 0x93e4fbe5
Exception code: 0xc0000409
Fault offset: 0x000a3652
Faulting process id: 0x47d4
Faulting application start time: 0x01d4e4dd895421ae
Faulting application path: C:\temp\test****.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report Id: a081e5b3-502b-4591-9fc7-429d5658dba4
Faulting package full name:
Faulting package-relative application ID:
Turn off ClickOnce signing. Double click Properties. Then go to Signing tab and uncheck "Sign the ClickOnce Manifest".
I haven't figured out why this is a problem, but after switching it off and publishing again, the problem disappeared.
Related
This error starts when I change the time zone of the Wordpress from where the data is pulled via gatsby-source-wordpress plugin. Before I changed the time zone everything was working fine.
The complete error:
C:\Users\XXXX\Documents\XXXX\XXX\2021\www\XXX-www\node_modules\yoga-layout-prebuilt\yoga-layout\build\Release\nbind.js:53
throw ex;
^
Error: listen EADDRINUSE: address already in use 127.0.0.1:51116
at Server.setupListenHandle [as _listen2] (net.js:1318:16)
at listenInCluster (net.js:1366:12)
at GetAddrInfoReqWrap.doListen (net.js:1503:7)
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:69:8)
Emitted 'error' event on Server instance at:
at emitErrorNT (net.js:1345:8)
at processTicksAndRejections (internal/process/task_queues.js:80:21) {
code: 'EADDRINUSE',
errno: -4091,
syscall: 'listen',
address: '127.0.0.1',
port: 51116
}
The development server is deployed, but right after that the app starts to update posts, create categories and other Wordpress data stuff:
info gatsby-source-wordpress update mediaItem getz-150lb (#425)⠀
⠀
info gatsby-source-wordpress create mediaItem tolva-getz-450lb (#445)⠀
⠀
info gatsby-source-wordpress create mediaItem bomba-transfer-co2 (#423)⠀
⠀
info gatsby-source-wordpress create tag getz (#417)
To finally crash throwing the mentioned error.
Gatsby info:
System:
OS: Windows 10 10.0.19042
CPU: (4) x64 Intel(R) Core(TM) i5-4200U CPU # 1.60GHz
Binaries:
Node: 14.15.5 - C:\Program Files\nodejs\node.EXE
npm: 7.5.3 - C:\Program Files\nodejs\npm.CMD
Browsers:
Chrome: 90.0.4430.212
Edge: Spartan (44.19041.964.0), Chromium (90.0.818.66)
npmPackages:
gatsby: ^3.4.1 => 3.6.0
gatsby-plugin-google-analytics: ^3.5.0 => 3.6.0
gatsby-plugin-image: ^1.5.0 => 1.6.0
gatsby-plugin-manifest: ^3.5.0 => 3.6.0
gatsby-plugin-react-helmet: ^4.5.0 => 4.6.0
gatsby-plugin-sharp: ^3.5.0 => 3.6.0
gatsby-plugin-sitemap: ^4.1.0 => 4.2.0
gatsby-source-filesystem: ^3.5.0 => 3.6.0
gatsby-source-wordpress: ^5.5.0 => 5.6.0
gatsby-transformer-sharp: ^3.5.0 => 3.6.0
npmGlobalPackages:
gatsby-cli: 3.5.0
Any ideas in how to fix this?
Regards!
According to this GitHub thread the issue is related more to Node dependencies rather than Gatsby.
Try lowering your Node version to 10, remove your node_modules as well as your package-lock.json, and install the dependencies again as the thread suggests.
Try this release gatsby-source-wordpress#5.7.0-alpha-wordpress.0+fe81b6e978 .It will fix the issue, it worked for me and suggested here on github github issue
Stumbled upon this page today when we were having the same issue... at first I completely skimmed over the "WordPress timezone" aspect, but then realized that we had just made the same change on our WordPress.
In my case, I had one post that I had published shortly before the timezone setting change, and that post currently exists with created/modified timestamps in the future. I set that post to "draft" and now gatsby develop is running.
I am deploying a django project to GAE. When I deploy locally everything runs as smooth as silk, however when I try to deploy from Jenkins it gets hung on the following line:
12:42 PM Getting current resource limits.
Full Deploy Log
12:42 PM Application: <gaeproject>; version: dev (was: 1)
12:42 PM Host: appengine.google.com
12:42 PM Starting update of app: <gaeproject>, version: dev
12:42 PM Getting current resource limits.
Deploy Command
python $GAE_PATH/appcfg.py -A $GAE_INSTANCE -V $GAE_VERSION update .
Has anyone else encountered this issue before? What might be causing this hang?
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]
"dontdisplaylastusername"=dword:00000001
I was trying to build a custom V2 Credential Provider and basing it off of Microsoft's code sample. The custom credential provider works as expected in most scensrios. However, if I enable the following setting dontdisplaylastusername, either through policy or by setting this registry setting and try to go to the login screen, the cursor just spins and the screen just flashes and I am never able to get the login screen to come up. Without any custom v2 credential providers installed, I am able to get to the Other User screen correctly.
How can I fix this? I tried adding a username field to my custom version since Microsoft's version did not have one but that did not change anything and still crashed.
Any ideas?
This is the github repo I was using for the sample
Here is an example of the fault that is logged for the sample credential provider.
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: LogonUI.exe
P2: 10.0.10586.0
P3: 5632d88c
P4: SampleV2CredentialProvider.dll
P5: 0.0.0.0
P6: 56cc64dd
P7: c0000005
P8: 0000000000003086
P9:
P10:
Attached files:
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_LogonUI.exe_5e45fd9b49f0ea6611374ae56677dfa1cb3a1fe_9798b224_0a4ffaf8
Analysis symbol:
Rechecking for solution: 0
Report Id: 5efbdb96-de9f-4254-b259-1beea7137fc7
Report Status: 96
Faulting application name: LogonUI.exe, version: 10.0.10586.0, time stamp: 0x5632d88c
Faulting module name: SampleV2CredentialProvider.dll, version: 0.0.0.0, time stamp: 0x56cc64dd
Exception code: 0xc0000005
Fault offset: 0x0000000000003086
Faulting process id: 0x3a8
Faulting application start time: 0x01d1910e42a0efb5
Faulting application path: C:\Windows\system32\LogonUI.exe
Faulting module path: C:\Windows\system32\SampleV2CredentialProvider.dll
Report Id: 038f9265-0f6f-45fa-bc3e-6c7de490ca34
Faulting package full name:
Faulting package-relative application ID:
I have written a small uploader to upload files using AWS S3 .NET SDK. It works fine on my computer. When I tried it on the two of the client computers, it throws exceptions.My dev machine and the client machine are running Windows 7. I tried couple of other computers, the program works fine. It is a very simple program, reads a file and calls the SDK API to upload it. The exception I am getting are:
Faulting application name: AWSUploader.exe, version: 1.0.0.0, time stamp: 0x56df54b2
Faulting module name: KERNELBASE.dll, version: 6.1.7601.23313, time stamp: 0x56842940
Exception code: 0xe0434352
Fault offset: 0x0000c44d
Faulting process id: 0x1594
Faulting application start time: 0x01d1798c224555b4
Faulting application path: C:\Users\ama06v\Desktop\Debug\Debug\AWSUploader.exe
Faulting module path: C:\WINDOWS\syswow64\KERNELBASE.dll
Report Id: 602f959e-e57f-11e5-a925-70f39532fcec
Application: AWSUploader.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: Amazon.Runtime.AmazonServiceException
Stack:
at Amazon.Runtime.Internal.ErrorCallbackHandler.InvokeSync(Amazon.Runtime.IExecutionContext)
at Amazon.Runtime.Internal.PipelineHandler.InvokeSync(Amazon.Runtime.IExecutionContext)
at Amazon.Runtime.Internal.MetricsHandler.InvokeSync(Amazon.Runtime.IExecutionContext)
at Amazon.Runtime.Internal.RuntimePipeline.InvokeSync(Amazon.Runtime.IExecutionContext)
at Amazon.Runtime.AmazonServiceClient.Invoke[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.__Canon, Amazon.Runtime.Internal.Transform.IMarshaller`2<Amazon.Runtime.Internal.IRequest,Amazon.Runtime.AmazonWebServiceRequest>, Amazon.Runtime.Internal.Transform.ResponseUnmarshaller)
at Amazon.S3.AmazonS3Client.InitiateMultipartUpload(Amazon.S3.Model.InitiateMultipartUploadRequest)
at s3.amazon.com.docsamples.UploadFileMPULowLevelAPI.Main(System.String[])
I have opened a ticket with AWS, they are looking into it, so far no answer form them.
I am using the latest AWS SDK from NuGet 3.2.2
Thanks for any help.
After researching a lot, found out that the exception I was getting is an uncaught exception. This exception has nothing to do with the KERNELBASE.dll, this is not the culprit, although it looks like. So I added a handler for unhandled exception not knowing where the exception was happening like this:
AppDomain currentDomain = AppDomain.CurrentDomain;
currentDomain.UnhandledException += new UnhandledExceptionEventHandler(MyHandler);
Handler
static void MyHandler(object sender, UnhandledExceptionEventArgs args)
{
Exception e = (Exception)args.ExceptionObject;
Console.WriteLine(e);
Console.ReadLine();
}
That handler produced the following exception (truncated):
MyHandler caught : A WebException with status ProtocolError was thrown.
Amazon.Runtime.AmazonServiceException: A WebException with status Protocol Error was thrown. ---> System.Net.WebException: The remote server returned an error: (407) Proxy Authentication Required.
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
at System.Net.HttpWebRequest.GetRequestStream()
at Amazon.Runtime.Internal.HttpRequest.GetRequestContent()
......
......
Basically the hospital system had a proxy server that was blocking our request to AWS!! Needed to login to the Proxy server as the defualt logged in user. For that you add the following line to the app.config.
<system.net>
<defaultProxy useDefaultCredentials=”true”> </defaultProxy>
</system.net>
I hope this helps somebody.
I am running OTRS on Windows on localhost as a test system.Whenever I create a ticket from customer webfront I am getting this error.
Error: Need ArticleTypeID!
Comment:
Traceback:
ERROR: OTRS-CGI-10 Perl: 5.12.3 OS: MSWin32 Time: Sun Jan 20 13:13:30 2013
Message: Need ArticleTypeID!
RemoteAddress: 127.0.0.1
RequestURI: /otrs/customer.pl
I think you somehow changed this value: Ticket::Frontend::CustomerTicketMessage###ArticleType to something that does not exist in the database.
Navigate to Admin > SysConfig > Ticket > Frontend::Customer::Ticket::ViewNew and reset the value using the circular arrow.