We are having an internal web application developed using C#.net, MVC. Each time 100 members access the app. while using, automatically logging out in any of the systems and with out any error page/message.
It is not occurring in a specific time/ using service. After that anybody try to login into the app, getting error message like "user name/password wrong." till application pool restarts.
The issue is occurring only with in two/three days after moving the code from local to server. After three/four days, application is working fine.
I am struggling to know the issue from code side or application pool issue?
Related
Suddenly my Azure App service(website) stop working(slow response from server side), When I try to open it in new tab or Reload it & only works when I freshly reload it & cache cleared.
App service working fine outside of India , Arr affinity also disabled. not able to figure out where is issue ? at code level or server or Azure platform
This error related to application and you can check error why these happening. using Application Insights and Azure App Service diagnostics.
You can check actual error using Application Insights.
Go to application Insights -> Click on failed request.
Click on Exception types.
And check by Diagnose and solve problems . Investigate how your app is performing, diagnose issues, and discover how to improve your application.
Go to App Service -> Diagnose and solve problems.
And other issue related to this problem.
Network issue, not response for request
db queries taking long time to response.
Application not handling error properly
This error is related to the application and you can check error why these happening. using Application Insights and Azure App Service diagnostics.
You can check actual errors using Application Insights.
Go to application Insights -> Click on failed request.
Click on Exception types.
And check by diagnosing and solving problems. Investigate how your app is performing, diagnose issues, and discover how to improve your application.
Go to App Service -> Diagnose and solve problems.
And other issues related to this problem.
DB queries take a long time to respond.
Application not handling error properly
Network issue, not response for the request
I have no idea how to troubleshoot this problem to findout what is going wrong.
When my deployed app is required to send an email it loads for a while then gives a 500 error. It sends the email fine in development and if I run the app in production on my local machine it also sends the emails fine so I cant reproduce it on my local machine and look at the logs. If I just deployed an update or fix then it will send the emails fine in the deployed version sometimes, but for the few times it works it stops working shortly after.
I'm using google cloud platform to host the app but can find a way to see what is causing the emails to not be sent and give me the 500 error. the GCP logs are useless and just say there was a 500 error at x time with no indication in what caused it.
How can I troubleshoot this problem or maybe what could be causing this?
Somehow narrowed it down to be a firewall problem from my google cloud instance. By default they block port 465 (the port I was using to send emails).
I have developed a web app using Angularjs. This app is intended to be used by company employees that have an iPad.
The application works great on Chrome, but Safari is causing problems. iOS Safari usually fails to execute first http request after wake up. If a user tries to navigate within the app after a wake up, the http request fails, the application shows the error to the user, then the user needs to refresh the page one or more times to get it working again.
Is there something I can do to workaround this problem other than recommend users to use Chrome instead of Safari?
EDIT: thanks to a friend that has a Mac I got the exact error message:
Failed to load resource: The network connection was lost
I support a legacy WinForms C# application that connects to 2 QuickBooks files. It has worked very well for years, both with QuickBooks 2008 and QuickBooks 2011.
A few days ago, the client upgraded to QuickBooks 2014. The application has not sucessfully connected to the QuickBooks files since. When I run the application manually it throws a .NET error saying System.Runtime.InteropServices.COMException (0x80040408): Could not start Quickbooks.
I decided to test to make sure that the SDK I am using, version 8.0, could in fact connect to QB 2014. So, I ran the SDKTestPlus3 application. When I tried to connect to the company file, it tells me that the application is not authorized to connect to that company file. So, I opened the company file in QB and went into Single User mode, and tried again - expecting to get the pop-up asking me to grant that application the right to connect. Instead, when I tried to connect with the file open in QB in Single User mode, SDKTestPlus3 gave an error saying "A QuickBooks company data file is already open and it is different from the one requested or there are multiple company files open."
Can anyone point me in the right direction here. Is the QBFC8 compatible with QB 2014, and if so is there something I need to do to get this application that has been working with QB 2011 for so long to continue working with QB 2014?
TIA!
Additional Information
I have now noticed that the errors in connecting to QhickBooks seem to be intermittent. The WinForms application gets run by a windows scheduled task every morning at 1:00 AM. Since the upgrade to 2014 on Monday, it has failed Tuesday, Wednesday and Thursday mornings. In looking at today's log files - this morning it successfully connected and processed records in QB. Now, when I try to run it manually, instead of the (0x80040408): Could not start Quickbooks COM error I instead got COM error (0x8004041C): An internal QuickBooks error occured while trying to access the QuickBooks company data file.
Has anyone else experienced these types of problems or have any idea what may be causing them? I need this application to work consistantly as it has in the past!!
Make sure the option to Keep QuickBooks running is unchecked.
Close all QB files that are open and make sure there are no other QBW32.exe files running in the task manager. If there are, kill them.
Try connecting again.
QuickBooks can be picky about who is doing what. Even better, though I'm sure there's some set of logical conditions that make it 100% replicable, it complains about user access seemingly randomly.
Make sure your legacy WinForms application and QuickBooks itself were installed and are running under the same user account.
Another option is altering the UAC settings.
technet on UAC: https://technet.microsoft.com/en-us/library/cc709691%28v=ws.10%29.aspx
intuit on UAC and your presenting error code: http://support.quickbooks.intuit.com/support/articles/SLN40414
Ignore that bit ^^^.
There's an error in QuickBooks Pro 2014. I've encountered it running in unattended mode with your connections and sessions going back and forth between company files.
After a few back and forths, something happens in their code and when you .EndSession/.CloseConnection the QuickBooks exe doesn't shut down. Then when you try to open your next connection, the exception bubbles up and you get the InterOp exception.
What I ended up having to do was after closing the connection, waiting like half a second and then, if QB32 is running, killing it. It's a crummy fix, but I didn't have a choice, and it works.
// closeConnection is from Intuit's SessionManager.cs that gets installed with the SDK
private void closeConnection(bool logError)
{
try
{
endSession(true);
if (_bConnOpen)
{
_sessionMgr.CloseConnection();
System.Threading.Thread.Sleep(waitTime);
KillQB32W();
_queryResponse = null;
_bConnOpen = false;
}
}
catch (Exception e)
{
if (logError)
logger.logCritical("SessionManager.CloseConnection", e.Message);
throw;
}
}
private void KillQB32W()
{
System.Diagnostics.Process[] oProcess = System.Diagnostics.Process.GetProcessesByName("QBW32");
foreach (System.Diagnostics.Process q in oProcess)
{
if (!q.HasExited)
{
q.Kill();
System.Diagnostics.Debug.WriteLine("Killer");
}
}
}
I have a simple Windows Phone App (7.1) that uses the LiveSDK and simply asks the user to sign in, grant access, and then is supposed to get their name and display it on the screen. Once I sign in, I get the following error:
A first chance exception of type 'System.NotSupportedException' occurred in System.Windows.dll
I have the correct Client ID, and have registered this as a Mobile app.
Anyone know what's happening here?
Re: the Redirect URL, i just left it blank since this is just a mobile app- and didn't specify one while setting up the Client ID.
Thanks!
You know I just ran into this same issue and it was confusing me for a bit. Then two things hit me.
It's a first chance exception
It's caught and handled by the Live SDK
I was too busy researching the error to try to actually continue through it :) Anyway it works fine if you let it continue.