How Do I Fix An Exe Application Error

[Marthe Bernskoetter]

HmmnI use Vivaldi, which is chrome based - don't get any issues with normal sign-ons. (I don't use the Google option). If you're wedded to Chrome, maybe export your bookmarks (just in case) and uninstall / reinstall Chrome?

Same with me since a couple of days. I have a free account for over 10 years now on only two devices: my mobile phone and the webversion. The mobile phone version works ok but the webversion comes up with the 404 error message. Could it be due to some sort of limit?

You don't say what browser you are using. One thing to try is to remove all the EN data including "app" from the browser. In Chrome you do this by right clicking the icon to the left of the url and choose "site settings"

Usually an Application Error message like this pops up if there is trouble with Concur's servers, but after checking open.concur.com, there doesn't look like there have been any performance issues nor outages for Expense in the past few days, so this may just be a browser hiccup.

If you are still getting the application error when moving expenses to reports, I strongly suggest that you open a ticket via the Support Portal so one of our Mobile Analyst can look further into the error logs to see where the issue is coming from.

I get this popup when running SourceTree 3.3.8. It seems to go away after I push something and login using SourceTree, but eventually comes back after a time. This is reproducible with 3.3.8 and 3.3.4. Any ideas would be appreciated.

At the same time all my checked out repositories were showing a red exclamation mark on the "Remote" icon. Clicking on Remote was trowing an error from winscp "Putty.exe not found".

So I installed putty but without success. The exclamation mark was still there and clicking on the icon was now trowing 'Server refused to start a shell/command'.

Next thing I tried was to do a new Clone and that was working. So I compared the "Remote Account" settings under Settings >> Remotes >> origin >> Edit and it seems that for my previously cloned repositories this settings were not correct anymore after the upgrade. Changing them solved the issue with the Remote. Clicking on Remote was sending me now to the right repository location in a browser.

Thanks, I deleted my saved password under Tools >> Options >> Authentication, and then the next time I did an action that required authentication, it re-saved my password. The saved password was a little odd looking in that it said "Rest-Saved Passwords" in the dialog, which was different from a co-worker's so it made sense that this might be the culprit. Afterwards, the title changed to"Git Save Passwords". After this, then the problem went away. Thanks!

Opened each repo, clicked Settings, double clicked the URL for the repo (to edit the entry), they were all set to "Generic Host" instead of my specific saved Bitbucket and Github save logins. Switched them to that, and they went away.

I pressed the + button to add a repository tab, and clicked "Remote" to see my remote repositories, and only there did it warn me about a problem, showing a red circle with an X in it on my Bitbucket account. No warnings in my account settings. I tried editing and remaking that account several times, using HTTPS and OAUTH, which succeed, but it returns to having the red mark on it in the "Remote" list after a few seconds. The AskPass.exe error seems to have disappeared. I can pull and push just fine using the account. Not sure what to make of this. It'll probably come back.

It is ridiculous that none of the big players in this (SourceTree, Git, etc.) have any working tips to solve this. It has been going on for years. Why on Earth is anything calling AskPass.exe if it's so obsolete that the file is missing?

Yep, it came back a few days later. I don't even have the broken account or any repositories from it in SourceTree anymore. I guess it's one of the other ones that's broken, but I've already removed them all and readded them several times with different setups, but it keeps coming back.

The recurring popup issue you are experiencing with SourceTree 3.3.8 and 3.3.4 is likely a bug or a configuration problem. To address this, you can try a few troubleshooting steps. First, ensure that you have the latest version of SourceTree installed, as newer versions often contain bug fixes. as you can see Formats of applications You can also try resetting or clearing the application cache and restarting SourceTree. If the issue persists, it is recommended to reach out to Atlassian's support team or consult their community forums for further assistance and potential solutions specific to this recurring popup problem.

I have a AP9630 that is no longer reporting back information properly. We did a switch replacement to the site but after the network came back online the card will no longer connect properly. The UPS unit was not powered down and all it did was move network ports. No firmware upgrade was done on this card in the past two years or during the switch replacement.

We are able to ping the card and get a web page to resolve for it but it states:

"The Application was not able to load"

"You are attempting to access a Schnieder Device. There was a problem loading the application. Please login to the device via telnet for more details"

1) Press and hold the NMC's pinhole reset button for 20 to 30 seconds, ensuring the NMC's status LED is flashing green during this time. When it changes to amber or orange, release the reset button to let the format function complete and for the NMC to complete its reboot process.

I'm trying to launch a Perspective app on an ipad and am getting an application error. This is occurring for both my app and the Perspective Demo. I didn't find another topic on this and wondered what it could be.

A possible first step will be to run the app in the designer and see if there are any error messages showing up in the logs. Secondly, is the app being opened in browser or perspective launcher? Lastly, are there any details of the error reported by perspective? If yes, then please paste them here.

I use a PC with Windows 7, and I'm using Adobe Reader version 15. Yesterday I was prompted to install an Adobe Reader update, which I did. Today, when I tried to open and print a PDF file, I got a message that said: "AcroRd32.exe -- Application Error. The instruction at 0x518f525c referenced memory at 0x00000000. The memory could not be read. Click on OK to terminate the program." I then tried to open other PDF files that I'd successfully opened as recently as last week, and I'm getting the same message for all of them, except that the instruction number (e.g., 0x518f525c) is different each time. After reading earlier posts on this forum, I tried uninstalling and reinstalling Adobe Reader, but the same problem is still occurring. The version of Adobe Reader that is installed is 15.023.20053. I also tried disabling Protected Mode in Adobe Reader, but after I do that and try to reopen Adobe Reader, I get a message saying that the program has stopped running. Please help!

I can't explain why this worked, but after reading a similar thread about issues that users have been having with Acrobat Reader since the most recent update, I tried the following, and it seemed to solve the problem for me:

I ran the Windows compatibility checker on the exe file and it set compatibiltty to Windows 8 and the problem has gone away. Weird! Possibly a conflict between Acrobat reader and win 10 updates? It has been fine for years.

We are facing the same issues today at work, so far 2 users are having this issue when scanning or viewing scanned documents in SAP. I want to find the prior full version installer so I can go back to the old version for these users but it seems impossible to find old installers! Not sure what we can do to fix this, very frustrated!

Thank you. I work at a helpdesk and one of my users has been experiencing this issue all morning, but only when trying to print from within an application which interfaces with Adobe. I first updated, which did not work, so I uninstalled and reinstalled. This worked for a short period, then the issue returned. I then did a system restore, which also worked for a limited time. Your solution has resolved the error for a third time today. Let's hope it's the magic fix.

The fix did not work for me. I ticked the Windows 7 box and tried unsuccessfully to open a PDF. I then un-ticked the Windows 7 box but again received the "Memory could not be read" message". Thanks for your help anyway.

@hilaryb....Is your problem that you are unable to open a pdf at all? I would check DEFAULT PROGRAMS, and ensure .pdf file types are set to open with your preferred application. The AcroRd32.exe error i received only occurred when attempting to print the pdf from within another application. Btw, no further issues have arisen since i applied the compatibility fix, confirmed just an hour ago by my EU.

I have never seen this error before, and I am running a freshly reinstalled Win10. Thanks for the direction though I went the other way. I ran the compatibility trouble shooter and took it's suggestion. I'll run in Win 8 mode now until/if i have further issues to see if the error happens again. Restarting and opening files seem good.

Interestingly if I open as run as administrator the program opens , I can set adobe as default pdf app and make changes to enhanced security. But these are not saved. When I open normally the pgm crashes once again.

I had posted earlier today for the same thing in another forum and went through the same steps, had the same situations, different message headers and codes. One thing I tried before today was the compatibility part, but Windows 7 didn't even show up in the list, only Vista SP1. But, after doing the cleaner and reinstall, and going by your suggestion, Windows 7 was in the list. So, something happened, and I still believe that there is a lingering issue that we will continue to run in to, until they completely repair the update issue.

3a8082e126