DPM Error ID: 36 - DPM Cannot access the path, becasue part of the path has been deleted or renamed

I have 6 dpm 2012 sp1 servers backing up a 2012 sp1 8 node hyper-v cluster.

all backups ran perfect all week. We do not run backups on saturday night. Backups ran sun night and 7-8 servers on each DPM server failed to backup with error;

The operation failed for Microsoft Hyper-V \Backup Using Child Partition Snapshot\XXX on SCVMM XXXX Resources.XXXXXX. because the data source is not available. (ID 30169 Details: VssError:The specified object was not found. (0x80042308))

I then go to check the disk allocation - and receive error id 36, DPM cannot access the path, because part of the path has been deleted or renamed?

I checked the disk and not seeing any errors or disk offline.

any ideas what is going on?

THX

ANNCEX

I removed a vm from the protection group, next tried to reapply, but could not even select it to add to protection group. so I checked the failover cluster manager and didnt see any issues. So I live migrated the vm, just to see what whould happen. I was then able to add back into the protection group & consistency check completed. Next test - I selected another of the failed vm's and live migrated it, I was able to complete a consistency check. Now why cant vm's migrate in a csv cluster to different nodes, then complete backups successfully. Cluster has been up for 2 weeks now. Prior to this issues backups ran succesful for the last 7 days.

ANNCEX

Marked as answer by Anncex Monday, February 24, 2014 11:00 PM

------------------------------------

ANNCEX

Marked as answer by Anncex Monday, February 24, 2014 11:00 PM

------------------------------------

I had a similar problem with DPM 2012 R2. I was getting the same error but on one server only. It was a new server that we had built, added to DPM just fine, ended up making some major changes to it, then rebuilt the server and re-added it to DPM and received this error when the review allocation menu during the wizard came up. I rebooted our DPM server, rebooted the VM and the host it was on in the cluster. Tried live migrating it around and still nothing.

For us, the answer was all to simple. I went through added the VM to the protection group again. During the phase where you select what VMs you want to add, there is a little refresh button at the bottom of the available server list. I knew nothing had changed as I could see the server I wanted in the list. I clicked the refresh button and the rest of the wizard completed flawlessly. Sometimes it is the simplest things that can be the solution.

I appreciate you updating your own question with your solution. It gave me a good place to start. I hope if someone else is searching for the same thing, that one of our answers helps them out.

Proposed as answer by Merrild Thursday, July 23, 2015 11:08 AM

------------------------------------

The refresh button solved my issue.

Alastair

------------------------------------

Arrggg - been trying to fix this for hours and refresh button also worked for me!

------------------------------------

You beauty! Refresh button Fixed my issue on DPM v11.0.50.0. I was wasting time on the PowerShell checking for orphaned volumes etc

------------------------------------

One of those gotchas!! Glad it worked Enjoy

ANNCEX

------------------------------------

Robb, you are genius.

I was banging my head for two hours, trying to add my reinstalled server to protection group, before i found your post.

BIG thanks.

------------------------------------

Tive este mesmo problema depois de adicionar um disco novo para a maquina virtual. O DPM Reconheceu o disco, porem não listava as pastas e arquivos dele.

Realmente, o Botão "Refresh" na lista de membros do grupo de proteção, foi o que salvou minha vida.

Obrigado Robb Crabtree pela dica.

------------------------------------

Sorry I don't understand Spanish 🤓 But I'll assume it worked! Enjoy

ANNCEX

------------------------------------

Great solution! The official MS articles that you get when Googling don't suggest this easy fix.

------------------------------------

Thanks Robb, it worked for me as well. I am using SCDPM 2016.

praveen bellary.

------------------------------------

Thanks Robb, this worked like a charm and I was battling for hours on this. :)

------------------------------------

I had a similar problem to this, however, nothing here fixed it. I believe my issue stemmed from the upgrade of our cluster nodes from 2012 R2 to 2016

Here is my scenario:

DPM 2012 R2 4.2.1338.0
4 Hyper-V 2016 Cluster Nodes
1 VM that needed backed up.

Tried Refreshing - No Luck
Tried Live Migrating - No Luck
Removed from Cluster, Re-added to cluster - No Luck
Uninstalled DPM agent and re-installed per the following: - No Luck
https://dmitryivakin.info/microsoft-system-center/dpm/dpm-2012-r2-ur13-can-not-add-clustered-vms-to-protection-group-id-36/

In the comments of that article, someone had removed the VM from the cluster, renamed the VM, then re-added it to the cluster. I did that by adding a - on the end of the VM and was then able to perform backups successfully. So if you are in a scenario where you don't care about the name and just need the VM backed up, you could just rename the VM.

Edited by Bob22212 Thursday, November 1, 2018 1:57 PM

------------------------------------

Thanks for that! One Hyper-V host had died and we managed to copy the VM from the hard disks before replacing with new disks, a re-installation of the OS and then put the VM back on it.

After installing the Agent on the new server installation and attached it to DPM we got this error when re-adding it to a Protection Group - clearly it was using cached information as as soon as we hit the refresh button (with nothing ticked/selected) it then worked!

:)

------------------------------------

Thanx Robb. Refresh button fixed it.

------------------------------------

Yes,

It: "there is a little refresh button at the bottom of the available server list", solved the same problem for me.

Thank you very much.

------------------------------------

Hi,

After 5 years, this solve works always !

------------------------------------

Apple watch after approval message 'something went wrong'

Hello,

After installing watchOS 7 I approve the authenticator pop on my watch I receive the message 'something went wrong'. I can only get the approval to work to do this from the app on my iphone. Anybody else got the same problem? Is it watchos7 related?

Hello Fellow(s),

Have you tried to disable Applock in MS Auth app? After turning that off, I could manage MFA again.

Regards,

Csabi

Proposed as answer by Ilpo Juvander Saturday, September 19, 2020 1:10 PM
Marked as answer by Chiel Dekker Monday, September 21, 2020 7:30 AM

------------------------------------

Hello Same problem after update to watchos7

------------------------------------

I have the same issue. Started happening when I installed the iOS 14 Beta on my iPhone. I hoped it was just a "beta software is not supported" thing, but since the general release of iOS 14 and WatchOS 7, the problem still occurs.

I tried deleting and recreating the accounts that I authenticated via the watch. No luck - still the same error message.

Edited by NSTim Thursday, September 17, 2020 3:04 PM

------------------------------------

have exactly the same as you, started with iOS 14 beta and watchOS 7.0 beta... hopefully the fix will be there soon..;)

------------------------------------

Same thing here, starting today after official release of iOS 14 and watchOS 7. Also after reinstall of watch part of Authenticator, it doesn't sees any account installed on iPhone in phone part of Authenticator.

Edited by panatar Thursday, September 17, 2020 6:17 PM

------------------------------------

same here after iOS14 and watchOS7. Reinstalled app and registration - no good. Approval works on phone just not the watch...

------------------------------------

Same issue. Tried deleting the app on the watch and can now no longer add any accounts to it. Notifications on the watch had been working on the betas.

------------------------------------

Posting here that the same thing is happening to me. Can approve from iPhone or iPad Pro but not watch.

------------------------------------

Same issue. Tried deleting the app on the watch and can now no longer add any accounts to it. Notifications on the watch had been working on the betas.

I removed the app and put it back, but had to delete my personal MS account off the phone and re-add it to get the watch app to add my account back on. Also, notifications work just fine on the watch, but when you tap Approve, it says something went wrong.

------------------------------------

Sama thing, even removed and added account in again, no luck. Broken it is. Works on iPhone, all my accounts are visible on Apple Watch, but cannot approve on any of the accounts.

------------------------------------

Same for me also. Authenticator app hasn't been updated for 2 weeks. Hopefully they push a new version soon.

Edited by JonnySharp Friday, September 18, 2020 8:24 AM

------------------------------------

Also having the same issue with both personal and work accounts. I removed both my personal and work accounts from Authenticator, adding them back, but the "Something Went Wrong" error on Apple Watch persists.

I started having this issue only after updating my iPhone X to iOS 14 and my Apple Watch Series 4 to WatchOS 7. I upgraded both the iPhone and Apple Watch OSes at the same time, so I cannot say if it's one or the other causing the issue.

Currently, I always receive the notification to the watch, but when selecting "Approve" I receive the "Something Went Wrong" error. If I then open the Authenticator app on my iPhone, it will have the notification available, I can select "Approve" there, and be logged in.

So, fortunately I'm not completely locked out, but this is definitely a degradation of features and clearly a bug that needs fixing.

------------------------------------

Glad to see I'm not alone. Thought I was going crazy there for a moment. Watch app doesn't add accounts after installing.

Thanks in advance, Ryan

------------------------------------

Glad it wasn't just me going crazy. Apple released iOS 14 too all of the sudden or MS dropped the ball on getting the app update ready in time.

------------------------------------

Hello Fellow(s),

Have you tried to disable Applock in MS Auth app? After turning that off, I could manage MFA again.

Regards,

Csabi

Proposed as answer by Ilpo Juvander Saturday, September 19, 2020 1:10 PM
Marked as answer by Chiel Dekker Monday, September 21, 2020 7:30 AM

------------------------------------

Excellent! This did the trick!

------------------------------------

Thanks - worked for me as well.

------------------------------------

Thanks Csabi!!

------------------------------------

that did the trick, thanks Csabi!

------------------------------------

Turning off app lock within the Authenticator app on the iPhone fixed it for me

------------------------------------

Thank you, Csabi. This worked.

------------------------------------

my app lock hadn't been on to start with. I have tried to lock and unlock but it did not help. Apple watch side still have the same issue :(

------------------------------------

Disabling Applock worked for me.

------------------------------------

This did not work for me. Still getting the something went wrong error message.

------------------------------------

Disabling App Lock in Authenticator > Menu > Settings > App Lock only fixed the issue for my work account but my other personal accounts still give the "Something went wrong" message when approving requests on my Apple Watch.

Approving requests on the iPhone continues to work however.

------------------------------------

Have you try to resolve it by updating the watch, may be some bugs are there the updation will fix the bug and you watch work properly

------------------------------------

Hi Nufka,

Have you tried to delete all previously set token and re-add them? (I know it's not a solution even if you do not have many account already)

------------------------------------

Hello,

I'm glad (all of you, whom it worked). I have to emphasize that it should be only a temporary solution, App Lock is important!

@Microsoft: please dive into this issue, I assume it is an app issue, where authentication process stuck somehow on Apple Watch with OS7

Cheers,

Csabi

------------------------------------

Hello.

I have the same experience (Disabling App Lock in Authenticator > Menu > Settings > App Lock only fixed the issue for my work account but my other personal accounts still give the "Something went wrong" message when approving requests on my Apple Watch.)

I've spent more than one hour for trying many possibilities for solving this issue. No success. It looks like a bug inside of the app.

Petr

Edited by Petr.RA.CZ Sunday, September 27, 2020 5:58 AM

------------------------------------

Hello Fellow(s),

Have you tried to disable Applock in MS Auth app? After turning that off, I could manage MFA again.

Regards,

Csabi

Worked for me too!

Apple Watch series 3 running WatchOS 7.0.1 and iPhone X running iOS 14.0.1

MSFT Authenticator App for iOS 6.4.26

------------------------------------

There is an issue with approving notifications on watchOS 7, and we're working with Apple to get this fixed. In the meantime, any notifications that require the Microsoft Authenticator watchOS app should be approved on your phone instead.

------------------------------------

Thanks! Works for me.

------------------------------------

Ok, understood. Foor now, disabling applock in the authenticator app works fine until the issue is solved.

------------------------------------

Thanks ... Worked for me too

------------------------------------

Hello.

I have the same experience (Disabling App Lock in Authenticator > Menu > Settings > App Lock only fixed the issue for my work account but my other personal accounts still give the "Something went wrong" message when approving requests on my Apple Watch.)

I've spent more than one hour for trying many possibilities for solving this issue. No success. It looks like a bug inside of the app.

Petr

Opposite for me. Works for my other accounts, just not my work one.

------------------------------------

There is an issue with approving notifications on watchOS 7, and we're working with Apple to get this fixed. In the meantime, any notifications that require the Microsoft Authenticator watchOS app should be approved on your phone instead.

Any updates here? Still broken.

Computer Solutions Group Lead Engineer www.csgsupport.net

------------------------------------

While this is just a workaround we still need a solution. Disabling the app lock will just get us a little bit unsafe.

------------------------------------

Mine was already disabled - and doesn't work.

------------------------------------

Is this ever going to be fixed? This bug makes the watch authenticator app completely useless. Disabling Applock does not fix this problem for me, nor has updating watchOS or the Authenticator app. Any status update would be much appreciated.

------------------------------------

I think I have the solution. You need to turn off Face ID or Passcode lock on the Authenticator app on your iPhone. As soon as I did that I was able to approve on my Apple Watch.

Directions:

1. Open the MS Authenticator app.

2. Click on the hamburger icon on top left and go to Settings.

3. Disable "App Lock" by clicking the toggle to off position.

Edited by 808analyst Friday, November 13, 2020 12:24 AM

------------------------------------

Worked for me as well thank you everyone.

------------------------------------

I have tried this multiple times. It never works. I have uninstalled reinstalled setup accounts for authenticator multiple times. Still cannot approve and get something went wrong message. Totally broken for me.

------------------------------------

That workaround does not work for me either, correct if you read this :

https://docs.microsoft.com/en-us/azure/active-directory/user-help/user-help-auth-app-faq?WT.mc_id=Portal-Microsoft_Azure_Support#apple-watch-watchos-7

Q: Why I am having issues with Apple Watch on watchOS 7?

A: There is an issue with approving notifications on watchOS 7, and we're working with Apple to get this fixed. In the meantime, any notifications that require the Microsoft Authenticator watchOS app should be approved on your phone instead.

Edited by MarTTijn Wednesday, November 18, 2020 10:29 AM no URL added

------------------------------------

Unable to authenticate with Microsoft Authenticator

When I try to authenticate with the app. It gives me error "error communicating with server".

Steps
I entered email on outlook.com
Then in password screen I choose "use Microsoft authenticator app instead"
Then I got notification on my phone to approve sign in by choosing the same number as displayed on screen.
Then I choose the same number on my phone and hit approve.
After that it gives error "error communicating with server".

Another issue is that it ask to enter lockscreen password multiple times even though I enter correct lock screen password or use fingerprint ( My Fingerprint working correctly in other apps and even lock screen password is correct )

Please fix this issue

Edited by John pugilist Saturday, August 18, 2018 10:16 AM Added more text

I get this same error. Totally frustrating! Did you ever find a fix?

------------------------------------

Android App user. This was working.

Now I request approval from my desktop app, then approve on the Authenticator app, then use my Android sign in pattern and I consistency get an error "error communicating with server". This is true for my two personal accounts.

The error would seem to be on the app side as this has occured over a fairly long period of time.

Thanks... Rick

------------------------------------

I have a same problem in not able to sign in my hotmail using the app code. Please Microsoft try to solve the problem ASAP. Thanks.

------------------------------------

I have the same issue since months. Please MS, fix this!

------------------------------------

Okay, I fixed the issue for me. I deleted my Microsoft account in the Authenticator app and added it again, now it works as expected without any issues. I was just too afraid to try this in the past, because I didn't want to lock myself out of my Microsoft account.

Proposed as answer by Han Qiang Saturday, February 9, 2019 12:12 PM

------------------------------------

I've reinstalled the app and still have no luck. I have a live.com account. I've tried removing and adding my account back as well. This is frustrating.

Aaron

------------------------------------

Anyone solved this? I am having the same problem. Funny it only happen to approval with already signed-in (so you choose Approve/Reject). It works well if you have to choose 1 of the 3 numbers.

------------------------------------

Mine hasn't worked for longer than I can recall... I think it may have worked briefly once upon a time... but, never mind that... every time upon entering the 1st # or Code given, as quickly as possible, w/out exception it will say, in nice red letters, "You have entered too many invalid attempts". And that's the end of that... trying again w/ another Code # just gives the same.

I keep trying occasionally, but, never will or never does work (see above).

Would be great to use it, but, alas...

Cheers,
Drew

Drew - IT Pro / MS Partner/Partner Company / Windows Insider / Owner - Computer Issues

------------------------------------

FIX FOUND for Android!

Symptoms: Unable to approve logins using the Authenticator app for Android (possibly iOS) / "error communicating with server" message when you try to approve a request.

I changed my screen lock settings earlier, which apparently requires that you "re-authorize the account" or "re-enable the account" in the Authenticator app (I don't remember exactly which one it was lol).

Go into the app, and there should be an option like "Re-authorize account" or "Re-enable account", I think I got the menu item when i clicked on the account or went to the settings area in the app. (it isn't a complex app, if the option is there it shouldn't take long to find)

Proposed as answer by Manifestarium Sunday, February 10, 2019 4:08 PM
Edited by Manifestarium Sunday, February 10, 2019 4:08 PM

------------------------------------

I confirm that this was solution. And I assume as stated elsewhere that it's because MS updated it's security. Thanks!

------------------------------------

All I ever get if & when trying to use it is this (see below) AND that is, actually, following the FIRST attempt.

Cheers,
Drew

Drew - IT Pro / MS Partner/Partner Company / Windows Insider / Owner - Computer Issues

Edited by Drew1903 Sunday, March 10, 2019 11:02 PM

------------------------------------

Has anyone ever got this to work? I'm just setting up a test Windows 10 VM and I thought, hey - I'm gain, I'll try using my Microsoft authenticator app with my existing Microsoft account: https://i.imgur.com/NmcJWc9.png

I get to this bit where it asks me to press this number on the app: https://i.imgur.com/Srd6Tpv.png

Which I do - I'm then asked to enter my screen unlock code on my Android PI phone. Or use my finger print. Neither method ever works...

------------------------------------

Just tried it, again. This time a code was sent (to it - for signing into this web site) and had to be ok'd in the mobile app. Tried twice, immediately, but, both times said code had expired, already! Geeesh, already!

Why have this thing if it doesn't ever work?? Or could it ever work, MS?

Cheers,
Drew

Drew - IT Pro / MS Partner/Partner Company / Windows Insider / Owner - Computer Issues

------------------------------------

I had the same error

To fix it I just opened the app, went to settings and enabled app lock (on IOS)

Hope this can help somebody

------------------------------------

I changed my authenticator settings to remove app lock. I did not have to reauthenticate, and I was able to use it again to login to onedrive on PC. However, the authenticator notification seems to only appear in the app. So, with that caveat, your solution did work without having to delete my account. Thanks.

------------------------------------

Ms Support forum

Wednesday, January 12, 2022

https://social.technet.microsoft.com/Forums/en-US/82f1d192-d9be-4c7b-90aa-1421b50a9951/unable-to-authenticate-with-microsoft-authenticator?forum=MicrosoftAuthenticatorApp

DPM Error ID: 36 - DPM Cannot access the path, becasue part of the path has been deleted or renamed

Apple watch after approval message 'something went wrong'

Unable to authenticate with Microsoft Authenticator

No comments:

Post a Comment

Setup is Split Across Multiple CDs

About Me