[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:
Related
(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.
Has anyone facing this issue with docker pull. we recently upgraded docker to 18.03.1-ce from then we are seeing the issue. Although we are not exactly sure if this is related to docker, but just want to know if anyone faced this problem.
We have done some troubleshooting using tcp dump the DNS queries being made were under the permissible limit of 1024 packet. which is a limit on EC2, We also tried working around the issue by modifying the /etc/resolv.conf file to use a higher retry \ timeout value, but that didn't seem to help.
we did a packet capture line by line and found something. we found some responses to be negative. If you use Wireshark, you can use 'udp.stream eq 12' as a filter to view one of the negative answers. we can see the resolver sending an answer "No such name". All these requests that get a negative response use the following name in the request:
354XXXXX.dkr.ecr.us-east-1.amazonaws.com.ec2.internal
Would anyone of you happen to know why ec2.internal is being adding to the end of the DNS? If run a dig against this name it fails. So it appears that a wrong name is being sent to the server which responds with 'no such host'. Is docker is sending a wrong dns name for resolution.
We see this issue happening intermittently. looking forward for help. Thanks in advance.
Expected behaviour
5.0.25_61: Pulling from rrg
Digest: sha256:50bbce4af6749e9a976f0533c3b50a0badb54855b73d8a3743473f1487fd223e
Status: Downloaded newer image forXXXXXXXX.dkr.ecr.us-east-1.amazonaws.com/rrg:5.0.25_61
Actual behaviour
docker-compose up -d rrg-node-1
Creating rrg-node-1
ERROR: for rrg-node-1 Cannot create container for service rrg-node-1: Error response from daemon: Get https:/XXXXXXXX.dkr.ecr.us-east-1.amazonaws.com/v2/: dial tcp: lookup XXXXXXXX.dkr.ecr.us-east-1.amazonaws.com on 10.5.0.2:53: no such host
Steps to reproduce the issue
docker pull XXXXXXXX.dkr.ecr.us-east-1.amazonaws.com/rrg:5.0.25_61
Output of docker version:
(Docker version 18.03.1-ce, build 3dfb8343b139d6342acfd9975d7f1068b5b1c3d3)
Output of docker info:
([ec2-user#ip-10-5-3-45 ~]$ docker info
Containers: 37
Running: 36
Paused: 0
Stopped: 1
Images: 60
Server Version: swarm/1.2.5
Role: replica
Primary: 10.5.4.172:3375
Strategy: spread
Filters: health, port, containerslots, dependency, affinity, constraint
Nodes: 12
Plugins:
Volume:
Network:
Log:
Swarm:
NodeID:
Is Manager: false
Node Address:
Kernel Version: 4.14.51-60.38.amzn1.x86_64
Operating System: linux
Architecture: amd64
CPUs: 22
Total Memory: 80.85GiB
Name: mgr1
Docker Root Dir:
Debug Mode (client): false
Debug Mode (server): false
Experimental: false
Live Restore Enabled: false
WARNING: No kernel memory limit support)
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.
In all their tutorial Getting started with LoopBack they start the app with $ slc start. I follow the tutorial step by step but my app doesn't start with $ slc start. I mean, the server localhost:3000 isn't started with the command. However, it starts with $ slc run. Why it happens? Why $ slc start doesn't work but they use it all over?
Here is an output when I run $ slc start which doesn't work. The "page is not available":
C:\Users\user\sbox\strongloop\hello>slc start .
App `.` started under local process manager.
View the status: slc ctl status
View the logs: slc ctl log-dump
More options: slc ctl -h
And when I check the status, it says that it is stopped for some reason:
C:\Users\user\sbox\strongloop\hello>slc ctl status
manager:
pid: 4764
port: 8701
base: C:\Users\user\.strong-pm
current:
status: stopped
link: C:\Users\user\sbox\strongloop\hello
current: hello
branch: local-directory
worker count: 0
And here is the output of $ slc run . that works, that starts the server:
C:\Users\user\sbox\strongloop\hi>slc run .
INFO strong-agent API key not found, StrongOps dashboard reporting disabled.
Generate configuration with:
npm install -g strongloop
slc strongops
See http://docs.strongloop.com/strong-agent for more information.
supervisor running without clustering (unsupervised)
Browse your REST API at http://localhost:3000/explorer
Web server listening at: http://localhost:3000/
Models created:
[ { name: 'Bel Cafe', city: 'Vancouver', id: 1 },
{ name: 'Three Bees Coffee House', city: 'San Mateo', id: 2 },
{ name: 'Caffe Artigiano', city: 'Vancouver', id: 3 } ]
slc start is used to start apps under process manager. We recommend using node . to start applications (slc run is an alias for node . anyways). I've asked our docs guy to update all references accordingly.
We actually changed the LoopBack docs to start apps with node . everywhere instead of slc start. Using node . is more appropriate for development on a local system because it gives you immediate feedback, error traces, etc. Apparently we made this change right after the OP.
Using slc start is useful to configure clustering and run the app under control of Str
Rand
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.