Free Download Manager Stuck On Requesting Info

[Ezilda Newnam]

Butthere is some more reasons, why you stuck on "Retrieving information". First check your proxy and firewall settings. In my situation, we need to unblock something(it is in my work, so I don't know,what exactly) and after that I saw the updates.

I've noticed this problem once I changed versions of Visual Studio. For whatever reason, the Nuget extension breaks during the installation process even though it seems to be installed in Visual Studio. You basically need to reinstall Nuget, and I had to follow the instructions on this link to get things working again:

I came across this problem and it would hang for about an hour at times. How I get round it is go to download a package in the Manage Nuget packager and then right click on your project and click clean. The download pops up within 2 -20 seconds.

My Concur travel request timeline is stuck at participant review on approval flow. I am and end user, but neither myself or my administrator can see why the approval flow is stuck and there is no person identified to move the approval flow forward. It states "Participant review" but myself, as the participant, I do not see any action that I can take.

The Concur ORAU system has been experiencing numerous glitches. I started a travel request on Monday that circled through two approval cycles unnecessarily and once approved yesterday I clicked the "book travel" button within the fully approved travel request but after numerous glitches during booking, once the travel was finally confirmed/ reserved and I received the confirmation email, Concur created a second travel request with a new ID that contained "self booked" expenses from the booking that I created through the fully approved request. The fully approved request is still listed in my requests and still states " Ready to book".

This is emergency situation, I have 1 day to either finished the approval on the un-approved submitted and booked request that is not moving forward with its approval flow, or I need to be informed of a way to troubleshoot a way around this glitch and have the fully approved request that is not linking to accept "book travel" from the accepted request actually follow through and stay attached to the specific travel booking.

This issue was resolved. It appeared as though there was either a glitch in the system during my first booking attempt through the fully approved travel request or that something occurred during processing that created a duplicate travel request. This is not verified, this is only my best guess. The low flight availability pushed me back into the booking process and my request to change primary email moved me out of the booking process and into user settings. This disruption in the booking could have been outside the standard flow. Again, I'm uncertain here. I did not know that the travel had been duplicated and the system was not allowing me to book travel through the approved request because the system thought that I was already travelling at that same time. Once we understood what occurred in the system and discussed the issue with my company, they instructed me to go into the duplicate request and cancel to then proceed again through the original approved request. The second attempt was successful.

Are you able to do a travel booking first, then have that turned into a Travel Request? I've seen some companies set up this way. The users do the booking and once finished, the system auto-creates the travel request for the user.

I have a user that was using a Teams Free account. He went ahead sometime last year and "upgraded" to a paid subscription and some kind of organization account. He does not recall any information on the credentials and it is causing us a lot of grief. I would like to get into an admin portal and reset the password and hopefully change the admin email address/login, but I'm stuck in a loop.

When I try the "Work" account, I have to use a password reset which then kicks back the message: "Only your admin can reset your password. To assist you, we've sent an email to your admin requesting a password reset."

Nevermind, ignore my reply, I was thinking that personal account was a normal user on this tenant. You can't even get into any account so it's going to be close to impossible to get into if some form of backup access MFA etc. wasn't setup.

I uploaded my license to license pool to download it on another laptop. It uploaded fine but after the upload was complete I accidentally clicked on download and the license manager got stuck downloading it. It has been almost 40min and it still is saying: ''Please wait...... loading license information (1/4)'' (Yes I have internet connection.)

So I had to take the laptop which had the license originally. Currently I am on a train and here is no option to charge the laptop. I am worried that the license information could get damaged if the computer shuts down.

I had the same issue when upgraded my license keys on a window Dell laptop , experienced the wait message for long extended time, I managed to resolve it by plugging both old and new key at two different ports on my laptop, when you run the license managers ( can be found in GRAPHISOFT folder ) , your system will recongnise the two keys in the dialogue box popped up , then the transition will excute the new key replacement from the old key with the new one.

I was having a similar issue with Ansible ping on Vagrant, it just suddenly stuck for no reason and has previously worked absolutely fine. Unlike any other issue like ssh or connective issue, it just forever die with no timeout.

If this works, you can pretty much rule out any setup or connectivity issue, as it proves that you could resolve target hostname, open a connection, authenticate, and execute an ansible module with the remote python interpreter.

I can remember this happening on older ansible versions, where a command would wait for an interactive input that would never come, such as a sudo password (when you forgot a -K switch), or acceptation of a new ssh host fingerprint (for a new target host).

Modern versions of ansible handle both these cases gracefully and raise an error immediately for normal usecases, so unless you're doing things such as calling ssh or sudo yourself, you shouldn't have this kind of issue. And even if you did, it would be after fact gathering.

By default, ansible will try and be smart regarding its ssh connection use. For a given host, instead of creating a new connection for each and every task in the play, it will open it once, and keep it open for the whole playbook (and even across playbooks).

This last example is a terrible situation : you can ssh to the target machine with a default ssh config, but as long as your previous connection is still considered active, ansible won't even try establishing a new one.

The setup module (when run automatically at the beginning of an ansible-playbook run, or when run manually as ansible -m setup ) can often hang when gathering hardware facts (e.g. if getting disk information from hosts with high i/o, bad mount entries, etc.).

Folks are very unlikely to run into the scenario that caused this issue for me but just in case... My playbook would run fine once but on subsequent runs it would get stuck at Gathering facts and then timeout. I eventually figured out that one of my tasks was configuring /opt/rh/devtoolset-8/enable to run via an /etc/profile.d link. Well, well, well all of a sudden sudo now refers to /opt/rh/devtoolset-8/root/usr/bin/sudo and it does not recognize the parameters that Ansible tries to use.

Maybe the Fingerprint of your target system has changed, for example when you reinstall the server OS. You have to delete the entries in known_hosts, ansible will not notify that a non-trusted entry is the issue, it just gets stuck exactly as you describe.

In my case ansible stopped working in the middle of a task. The reason was because my ssh-agent stopped working (ssh-add -l was not returning anything). I restarted everything and it worked again. So check if your ssh-agent is working properly (ssh-add -l should not get stuck).

FQDN and hostname mismatch can also cause ansible hangout.I have used FQDN with domain differs from hostname domain.After making both equal, ansible works perfectly.Possiblly ansible compares FQDN and hostname before executing tasks on remote host.Hope it helps!

Sudo's password is the problem. Make sure that (1) you can issue 'sudo anything' on newly opened terminal (where password in not cached) without providing one (2) that puppet hasn't reversed your earlier manual 'sudoers' changes.

I had this problem on a new macOS install. I'd just installed /Applications/Xcode.app/ from XIP but hadn't accepted the license yet. (I think I had accepted the Xcode Command Line Tools license, but running xcode-select -p showed /Applications/Xcode.app/Contents/Developer so not sure if that's relevant).

3a8082e126