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.

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

Power Query Load to Data Model -- Constantly Stuck/Hanging

Hello,

I am currently running into a troubling situation across with Power Query and Power Pivot across multiple computers.

Both computers are Windows 10 Pro 1903

Both versions of Office are Microsoft Office Professional Plus 2016 and up to date.

I cannot under any circumstances load a Power Query based query/table into the Data Model. Whether it's 26 rows in a totally simple by-hand table (see below) or a complex query that's had a lot of transformation and many tens/hundreds of thousands of rows, the same thing happens:

EDIT:

I cannot submit an image file/link given my account is not verified. I am not sure how to show what is happening given that.

It just hangs and hangs and hangs and never loads to Data Model. The number of rows always loads instantly, but then it hangs after that.

Things I can do to get the Data Model to work:

I can create a table in Excel and load directly to Data Model (From Table option in Power Pivot Ribbon). That's fine and instantaneous.
I can load the Power Query query to a table in the worksheet and then load that query indirectly to Data Model by using the From Table option like I would a regular Excel Table in the first option.

What I can't do:

I can't right-click the query (or choose upon initial creation) the option to "Load to Data Model" regardless of whether it's a Connection Only or Load to Worksheet. All Excel does is hang and nothing ever shows up in the Power Pivot window after many minutes of waiting.

I can't load bigger tables to worksheet as an intermediate step so this work-around is not stable or usable.

Over the last 24 hours I've tried:

Repairing Office (Full Repair that takes a long time and re-downloads Office essentially)
Uninstalling/Reinstalling .Net
Repairing .Net Installation with the Microsoft Tool
Changing my Power Query options/configuration (Background Data, etc) per other sites/forums where I've seen similar (but not the exact same) issues.
Searched for hours on forums and found nothing that troubleshoots this issue.

This is a new problem given I was just using Power Query and Power Pivot last week with no issues. It's happening across multiple machines. It's happening with generic, tiny tables like the one in the gif above (with no other data in the workbook) and bigger, more complex queries that cascade off of each other, have transformations, etc. Same results no matter what.

If anyone has any idea what I might do to fix this, I'd be very grateful. This is impacting my ability to do client work given it's not working on either of my computers.

Thanks so much!

Edited by Wizard-121 Thursday, November 21, 2019 3:09 PM

Thank you all for reporting the issue and for all the details you have provided.
As you may have already noticed, we finally found the root cause of it and according to our testing it has been fixed.
Please restart Excel before trying it again.
If you aren't using one of the latest versions already, you may have to update your installation first.

Yehezkel,

Excel team

Edited by Yehezkel BernatMicrosoft employee Sunday, February 2, 2020 6:14 PM
Marked as answer by Imke FeldmannMVP Monday, February 24, 2020 9:57 PM

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

I just went back to an older workbook from a few weeks ago that has ten queries and two scrubbed queries loaded into the data model that has never given me problems.

I tried to add an additional query to the data model and the same behavior that I described above happens.

In short, I have no ability whatsoever to combine Power Query and the Data Model/Power Pivot currently.

I have no idea what to do to fix this.

[EDIT] One more update:

I opened my original file on a client machine remotely. Office 365 ProPlus. Zero problems. Everything works fast, effortlessly, and easily. No issues with the data model, PQ >> PP interface, hanging, etc.

I have a feeling there's something wrong with Office 2016 Professional Plus standalone.

Edited by Wizard-121 Thursday, November 21, 2019 9:28 PM

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

Hi there, I've got exactly the same issue, but I've seen it in Windows 10 and in Windows server 2012 R2 64 but always with Excel 2016 professional plus.

I am an instructor in Excel and I was teaching a course on Power Query and Power Pivot 3 weeks ago and this issue happened to all the students that happened to have Excel 2016 professional plus with the latest update installed (October). It's the first time in 3 years teaching with the same material.

After many tests I have come to the conclusion that PCs with Excel 2016 professional plus 32 or 64 bits with the version 1910 compilation 12130.20410 or 12130.20390 are affected with this issue.

There is no way to load data from any query (CSV, excel, access,..) to the data model. Importing directly from Power Pivot works fine so I guess the addin is ok. And also, when loading to table, the process stops and finally finishes by cancelling the load and then refreshing. Doing the same procedure when loading to the data model just ends in an error.

I've tried playing with the windows defender new options, with different data sources, but nothing. In my laptop with 365 pro plus it just works like charm.

It is a very unnerving situation that I hope gets addressed soon.

I'll post any updates I may find on this subject so it can be helpful to others.

Cheers

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

Hi DU,

Thanks so much for validating this issue. At least I know I am not crazy or doing something weird or wrong. My only solution was to use a different machine that has a different version of Excel on it. Both Excel 365 and Excel 2019 worked for my situation and loaded the data seamlessly and quickly. The Excel 2016 machines had no ability to do what I needed them to as of my writing (I haven't tried again since then).

I am surprised more people haven't reported a similar issue. That's part of what made me think it was something local to my machine/version/add-ins. When the second machine showed the same issue, I figured it was the software, but I haven't seen anyone else complaining about it and I'm quite sure that there are many many thousands of people using Power Query/Power Pivot with Excel 2016 Professional Plus.

Hopefully it gets resolved shortly.

Edited by Wizard-121 Thursday, November 28, 2019 2:21 PM

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

hello

posting the query would be appreciated.. .:)

do you use some external tables to do filering in the query?

I had a similar problem and it turned out that it was some kind of a bug, but there was a work around.

Please check my post and check if the work around suggested there is working for you

https://social.technet.microsoft.com/Forums/en-US/4b5eb556-2d27-4c98-983e-d1cef591d8cb/problem-loading-data-directly-to-data-model?forum=powerquery

good luck

Jimmy

Query it

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

Any query would fail I'm afraid. Check this video so you can see what kind query is not loading. The simplest one won't load into the data model.

https://www.screencast.com/t/0gr2QTq36

I think it has something to do with october 8th update and just for Excel 2016 users.

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

oooh... this seems to be a bug indeed.

Because I'm curious... try to add a Table.Buffer after the IN-statement...

something like

in   Table.Buffer(ChangedType)

Jimmy

Query it

Edited by jimmy80211 Friday, November 29, 2019 10:41 AM

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

In addition to DU - as of today - 2 other users running Excel 2016 face the same issue and nobody was able to assist (MS Community thread). After having seen this thread I suggested them to report here as well suspecting something specific to this version

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

hello

posting the query would be appreciated.. .:)

do you use some external tables to do filering in the query?

I had a similar problem and it turned out that it was some kind of a bug, but there was a work around.

Please check my post and check if the work around suggested there is working for you

https://social.technet.microsoft.com/Forums/en-US/4b5eb556-2d27-4c98-983e-d1cef591d8cb/problem-loading-data-directly-to-data-model?forum=powerquery

good luck

Jimmy

Query it

Hi Jimmy,

As DU said, this fails for all queries. I have tried multiple workbooks that have never had any issues -- some freshly made, some old and elaborate, some that were super basic.

My original post tried to upload a gif that showed this issue for the most basic of query loads (an Excel Table of 1/2/3; A/B/C) but I wasn't allowed to embed any photos or links given I was new here.

Here's what I am talking about. This is by far the most basic Power Query to Data Model/Power Pivot table one can add and it still hangs.

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

I am having the exact same problem. Any CSV file folder will fail. I have the exact same version of Excel - Professional Plus 2016 with Version 1910 (12130.20410) update. I guess I got stuck because my Excel is set to auto update.

It is driving me nuts for the past 1 week. It bombed on me as I was doing a demo and prodly wanted to show how more than a million rows can be loaded with PowerPivot and PQ Get & Transform Data.

Please, please help us with a solution Microsoft.

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

hello

posting the query would be appreciated.. .:)

do you use some external tables to do filering in the query?

I had a similar problem and it turned out that it was some kind of a bug, but there was a work around.

Please check my post and check if the work around suggested there is working for you

https://social.technet.microsoft.com/Forums/en-US/4b5eb556-2d27-4c98-983e-d1cef591d8cb/problem-loading-data-directly-to-data-model?forum=powerquery

good luck

Jimmy

Query it

Hi Jimmy,

As DU said, this fails for all queries. I have tried multiple workbooks that have never had any issues -- some freshly made, some old and elaborate, some that were super basic.

My original post tried to upload a gif that showed this issue for the most basic of query loads (an Excel Table of 1/2/3; A/B/C) but I wasn't allowed to embed any photos or links given I was new here.

Here's what I am talking about. This is by far the most basic Power Query to Data Model/Power Pivot table one can add and it still hangs.

I´m literally having this exact same error. Anybody got updates for a possible solution?

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

oooh... this seems to be a bug indeed.

Because I'm curious... try to add a Table.Buffer after the IN-statement...

something like
in   Table.Buffer(ChangedType)
Jimmy

Query it

Hi Jimmy,

Tried your solution running MS Office Professional Plus 2016 (v1911 - 32bit), unfortunately no succes. Thanks for the suggestion though, its a frustrating error.

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

Thanks Jimmy, I tried the Table.Buffer line but still no luck.

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

I'm having the same issue, Excel 2016 Pro Plus (C2R) version 1911.

While we're waiting for a fix from Microsoft, I think I found a workaround. I happened to have a machine on which Excel hadn't been updated to 1910/1911. It was still 1909, and Power Query worked in that version.

So I copied the bin folder of P.Q. that's in:
"C:\Program Files (x86)\Microsoft Office\root\Office16\ADDINS\Microsoft Power Query for Excel Integrated"

And I copied it onto my machine which had Excel v.1911, and it seems to work.

As additional details, I'm thinking the culprit was Version 1910 (Build 12130.20344), released on November 12, 2019. (https://docs.microsoft.com/en-us/officeupdates/update-history-office-2019). They fixed a CVE:

Information disclosure vulnerability exists in Microsoft Office software when the software fails to properly handle objects in memory. An attacker who successfully exploited this vulnerability could obtain information to further compromise the user's system. To exploit the vulnerability, an attacker would have to log on to an affected system and run a specially crafted application. The security update addresses the vulnerability by correcting how Microsoft Office handles objects in memory.

Edited by dubeg Monday, December 9, 2019 11:43 PM

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

Eureka, it fixed the problem! at least until the fix is published by MS thanks

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

Great news Dubeg & Duyarra.

Is it possible to upload the Bin folder of 1909 build here or somewhere else as a zip?

Thanks,

Vin

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

Hi,

Can you please provide us with your Excel's Product ID and Session ID from a session it reproduces in so we can investigate further?

Information can be found in "Excel -> Account -> About Excel"

Thank you,
Ron.

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

Hi Ron,

I upgraded my Excel on my main machine so I could do work, therefore the issue is no longer there. I'll track down the other machine if no one else responds and get you the pertinent information. I have not even tested anything on that faulty machine in many weeks now so, for all I know, the issue could be gone/updated.

I'll take a look sometime and respond here if you don't get what you need to help you diagnose the issue.

--

As an aside, I not only started this thread, but also separately turned on notifications/subscribed and continually check the Alert Me box on any reply and I have yet to receive even one notification when this thread has any responses. The only way I know someone has commented here is if I come to this page randomly and check. I had submitted an email address when I first posted, but when I go into my profile, I don't even see an email field, let alone mine listed.

Edited by Wizard-121 Wednesday, December 11, 2019 6:45 PM

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

Hi Ron, here it is:

Product ID: 00351-35026-43710-AA642

Session ID: AC157DF7-49A1-49B5-B733-A52E808F99C4

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

Hi Vinay,

Here's a link: https://1drv.ms/u/s!Ap-sAwOg4WG8gslZGdkU5JSXRzCw1g?e=c9YZBJ

When you decompress it, don't duplicate the root folder, eg. \bin\bin\. Otherwise Excel will give you an error.

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

Thanks a lot dubeg. Much appreciated!!! You are SUPER AWESOME!

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

@dubeg

Thanks for sharing the IDs!

Unfortunately, I couldn't pinpoint the issue for now.

Any chance you have a workbook that reproduces this issue and you can share with us?

If not, maybe there are specific steps that easily reproduce the issue?

Also, is the query loaded to a query table?

Thanks again!

Edited by Yehezkel BernatMicrosoft employee Thursday, December 12, 2019 3:37 PM

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

Hello Yehezkel.

Here's a simple repro:

- Create a simple list of values such as A, B, C, in any sheet.
- Create a table out of these values, and select it.
- Data > (Get & Transform) From Table.
- Close & Load > Close & Load To...
- Check [Only Create Connection], and check [Add this data to the Data Model]. Click [Load].

Notice that the row count displayed is correct, but the query never terminates.

Edited by dubeg Thursday, December 12, 2019 9:18 PM

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

Hello,

I'm having the exact same problem with Excel 2016 Pro Plus.

'Connection only' and 'load to data model' does not yield any results. Adding the connection only does work but as soon as I add 'load to data model' the query does not load any data.

Loading to table does work. Adding the data from table to the data model also works. Adding data from Power Pivot also works. But Get&Transform (a.k.a. Power QUery) is bugged atm.

And since my data has more than 1 million rows, I can not bypass the problem by loading into table.

Any (Good) News regarding this bug?

Shlomi

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

I upgraded my Excel on my main machine so I could do work, therefore the issue is no longer there.

Sorry Ron, for clarification, when you say upgrade you mean you are no longer using Excel2016 (where the issue is solely happening) but you're now using Excel2019 or 365. Is that correct?

It is the same case here (365). Many of my customers have, and still have , this issue with their machines running Excel 2016 professional, but many of us have decided to shovel in the extra cash to upgrade an continue working.

What worries me is, that this same problem might happen to us (365 users) in the next iteration, and I'm finding that it is taking painfully too long for the problem to be correctly addressed.

Again, thanks to dubeg tha found a workaround that I posted to my customers while recommending to turn off automatic updates for now.

Tx everybody for contributing to this thread,

Edited by duyarra Sunday, December 15, 2019 8:03 PM

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

Hello Ron,

Product ID: 00332-90002-44767-AA235
Session ID: 8C9C7E74-B06C-4940-8D07-50263AAF32C9

I'm having the exact same problem with Excel 2016 Pro Plus

'Connection only' and 'load to data model' does not yield any results. Adding the connection only does work but as soon as I add 'load to data model' the query does not load any data.

Loading to table does work. Adding the data from table to the data model also works. Adding data from Power Pivot also works. But Get&Transform (a.k.a. Power QUery) is bugged atm.

And since my data has more than 1 million rows, I can not bypass the problem by loading into table.

I've already run the fix office and even re-instlled the office, but it didn't fix it.

Is there any updated regarding this bug?

Thanks,

Shlomi (Israel)

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

I upgraded my Excel on my main machine so I could do work, therefore the issue is no longer there.

Sorry Ron, for clarification, when you say upgrade you mean you are no longer using Excel2016 (where the issue is solely happening) but you're now using Excel2019 or 365. Is that correct?

It is the same case here (365). Many of my customers have, and still have , this issue with their machines running Excel 2016 professional, but many of us have decided to shovel in the extra cash to upgrade an continue working.

What worries me is, that this same problem might happen to us (365 users) in the next iteration, and I'm finding that it is taking painfully too long for the problem to be correctly addressed.

Again, thanks to dubeg tha found a workaround that I posted to my customers while recommending to turn off automatic updates for now.

Tx everybody for contributing to this thread,

DU

I am not Ron, I am the original poster of the issue. Ron is one of the people who's helping to troubleshoot the issue with Microsoft.

To answer your question, I have no idea if this problem is isolated to a specific update of Excel 2016 Professional Plus or may end up affecting other versions later. I only know that I've seen two long threads about this issue and every poster has the same edition of Excel. In every other Excel version/edition, I have tried, I have not seen the issue.

I was happy to post here to try to troubleshoot the issue and for the good of other community members, but a mission-critical piece of software not working for over three weeks meant I had to quickly move on to continue onward given no one who I consult for cares why my Excel doesn't work.

I do hope the issue gets resolved for the good of the community and all users. It's clear it's not isolated and has at least a few dozen people who've either contributed to one of these two threads or clicked "I have the same problem."

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

Thanks for your answer Wizard-121, at least we got the workaround. Let's cross our fingers this problem will be sorted out soon.

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

(Sorry for the delay in my answer. For some reason I haven't got notifications for the new replies.)

Thanks everyone for clarifying the bug scope!

Unfortunately, I still can't reproduce it locally even when using the same Excel version mentioned here (12130.20410) and the steps described above. I continue investigating it in more ways.

Meanwhile, it may helps a lot to debug it if you could please send feedback from inside Excel in a session that reproduced the issue, preferably with a descriptive title mentioning Power Query and data model. (Here is how to do it: https://support.office.com/en-us/article/how-do-i-give-feedback-on-microsoft-office-2b102d44-b43f-4dd2-9ff4-23cf144cfb11#platform=Windows.) For extra helping, posting here the OCV link (you get later by email, if you provided your email in the feedback) will make it even easier and faster to connect them to this issue.

It'd be great if you could please add more info about the issue:

Is Excel still responsive?
Is the data model functioning?

Thanks again!

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

Hi Yehezkel,
I just did what you suggested. I'll post the OCV link if/when I get it.

My Excel version is now 12228.20100.
PowerQuery is now 2.75.5649.941.

Is it worth mentioning that it's the 32-bit version of Excel/PowerQuery?
Are you trying to reproduce the issue with the 32-bit version?

Is Excel still reponsive?
Yes, it is.

Is the data model functioning?
I'm not sure how to test that. Could you provide instructions?

Here's a screenshot of what I'm seeing after cancelling & re-trying (Refresh) the never-ending query:
https://1drv.ms/u/s!Ap-sAwOg4WG8gsla16cmuvLbRi6Imw

In that state, I can't retry/refresh again.

Edited by dubeg Thursday, December 19, 2019 9:38 PM

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

(Sorry for the delay in my answer. For some reason I haven't got notifications for the new replies.)

Thanks everyone for clarifying the bug scope!

Unfortunately, I still can't reproduce it locally even when using the same Excel version mentioned here (12130.20410) and the steps described above. I continue investigating it in more ways.

Meanwhile, it may helps a lot to debug it if you could please send feedback from inside Excel in a session that reproduced the issue, preferably with a descriptive title mentioning Power Query and data model. (Here is how to do it: https://support.office.com/en-us/article/how-do-i-give-feedback-on-microsoft-office-2b102d44-b43f-4dd2-9ff4-23cf144cfb11#platform=Windows.) For extra helping, posting here the OCV link (you get later by email, if you provided your email in the feedback) will make it even easier and faster to connect them to this issue.

It'd be great if you could please add more info about the issue:

Is Excel still responsive?
Is the data model functioning?

Thanks again!

Is there a place to post the issue about the Technet forums not sending notifications? I have not received a single one on this thread and it appears no one else is either. It's not easy to navigate issues and troubleshoot when there's no notification and one has to randomly check to see if someone has responded every so oten. I'd like to offer that to someone on the Technet side so they can address it.

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

I finally logged on to the machine I have that still has Office 2016 on it. Here are the specs:

Microsoft Excel 2016 (16.0.12228.20322) 64-bit
Product ID: 00339-10000-00000-AA361
Session ID: 3C8C46B3-2F85-4CD8-825B-EF1E7BA8AF3D

Recently upgraded to Windows 1909 and re-tested this issue. No change (I wouldn't expect there would be). Office is fully updated as well.

To answer the questions about is Excel responsive:

Excel is fully functional
Power Query is fully functional
Power Query Load to Table works
Power Query Load to Connection works
Power Query Load to Data Model hangs and never updates (opening the Data model Window is empty unless there's something in there that didn't originate from Power Query)
Excel looks like the screenshot I posted a few weeks ago and that I'm reposting here:

Even when this "hanging" happens, I can do whatever else I need to do as far as Excel and Power Query go. Ultimately, just to get the annoyance out of the way, I typically cancel the loading and the subsequent "Did not Load" error results.

This behavior on Excel 2016 across multiple machines has maintained itself over all these weeks even across updates of various kinds. This only happens in Excel 2016. I've now worked with Excel 2019 (on a machine that had this issue) and Excel 365 (on a totally different machine) and neither have had this problem -- either with files that had this issue in 2016 or with brand new files. Every way I've tried on Excel 2016 (new files, old files that used to work, etc) has reproduced this issue 100% of the time.

Edited by Wizard-121 Saturday, December 21, 2019 6:22 PM

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

@dubeg

> Is the data model functioning?

> I'm not sure how to test that. Could you provide instructions?

Insert > PivotTable > Use this workbook's Data Model

If you can create the Pivot Table and see your data there, the Data Model is working and maybe this is just a cosmetic (even if annoying) issue.

Many thanks to everyone who filled feedback on this issue. We are looking into them right now.

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

Exactly Same problem here with

Microsoft Excel 2016 (16.0.12228.20322) 64-bit in a Windows Server 2016

And

Microsoft Excel 2016 (16.0.12228.20322) 32-bit in a Windows 10

The only workaround was to over write the DLL's as @Dubeg proposed

I only have patched the windows 10 Machine, please tell me what to do with the windows server to provide you feedback so you can try to solve this issue.

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

For anyone not getting notifications, I posted a separate thread and was offered a solution by a Microsoft MVP:

https://social.msdn.microsoft.com/Forums/en-US/a32f2cdf-8603-47ab-a640-4679e634c2b8/technet-notifications-broken?forum=reportabug

Edited by Wizard-121 Monday, December 23, 2019 1:01 AM

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

I had the same issue with the Excel 2016 version 1911 as everyone else here. This is definitely a bug, but it will take some time to fix on MS side and we needed an immediate workaround. I tried "transplantation" of the DLLs mentioned here, but it failed and corrupted installation of the Office so I reinstalled the Office and then used standard downgrade procedure. I followed the instructions on the link below and used the config XML below. The Excel was successfully downgraded to 1908 where is this bug not present.

support.microsoft.com/en-us/help/2770432/how-to-revert-to-an-earlier-version-of-office-2013-or-office-2016-clic

<Configuration>
<Updates Enabled="TRUE" TargetVersion="16.0.11929.20254" />
</Configuration>

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

@Yehezkel

It doesn't seem to be comestic only, the option is greyed out :l

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

It's now December 27th. I haven't seen any update to this from Microsoft and when I tried reverting my Office back to the earlier version I got an error code 30029-27. Is there any hope for a working update to Excel for this issue? I also tried the other work around of copying the bin folder from the link but all that did was make the New Query, From Database, From SQL Server not do anything. It just comes back to the main screen and the dialog box to enter the server name never appears.

Edited by RB Robert Brooks Saturday, December 28, 2019 2:36 PM

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

Chiming in here, exact same issue on my side, I cant load queries to the data model. Excel 2016, 64 bit, Office 2016 Pro Plus Retail on Windows 10 64 bit.

On the 1911 build 12228.20364 C2R

Quite worrying that its been over a month and there's no fix out for this..

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

Chiming in here, exact same issue on my side, I cant load queries to the data model. Excel 2016, 64 bit, Office 2016 Pro Plus Retail on Windows 10 64 bit.

On the 1911 build 12228.20364 C2R

Quite worrying that its been over a month and there's no fix out for this..

I am actually quite surprised. This is like if a main/frequently used formula wasn't working. It's such core functionality for some that to not see really anything from Microsoft about ability to reproduce, ETA, etc, is very disheartening (and I'm very pro-Microsoft, mostly).

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

Is someone still looking into this? I don't want this to be forgotten. As the previous poster pointed out, this is not some small function that hardly anyone uses. This prohibits being able to bring SQL data into Excel.

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

It still is unresolved. So far I have my updates settings to "don't update" so I can use dubeg's workaround and keep using Excel with big datasets and data models in power pivot.

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

Still no update. I'm going to start reporting it frequently on the feedback button so they wake up. It can't be hard to reproduce?

Strangely my work laptop, which runs a volume license and that I update excel manually with the updates from the Microsoft website, even though on the December patch, is not affected.

Anyone know where else we can report this so it receives more attention?

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

I wanted to report the same issue as the one described by Wizard 121 (initial post).

Below my system configuration:

MS Win 10 Pro, Version 10.0.18363 Build 18363

Excel:

MS Pro Plus 2016 (16.0.12228.20100) 32-bit

Product ID: 00338-97684-28485-AA947

Session ID: D35DF5B8-3C5C-4824-827F-74C949130143

Power Query Version: 2.75.5649.941 32-bit

I hope Microsoft teams are still investigating, as this issue is blocking for people using the functionality of loading data to the data model. Could you please confirm?

The behaviour is the same as already reported from other users.

@MS Team: Please reply and advise.

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

This is still an issue. I'm getting ready to begin a new position and had planned on using Excel as an initial bridge to begin data analysis and then possibly transition to Power BI. If Microsoft is not going to find a resolution to this issue I may have to suggest an alternative BI solution. There has been no communication from Microsoft as to a possible fix or even that they are continuing to look into this. It's beyond annoying that it has been almost 2 months and no feedback is being provided.

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

Me too I have this problem!!!

Ivo

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

I also have the problem. Office version: MS Pro Plus 2016 (16.0.12228.20100) 32-bit.

I am looking forward to having a fix.

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

Hello @YehezkelBernat,

Were you able to reproduce the error?

Can we help you with anything i order to get this fixed as quick as possible?

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

I too have this issue :

Session ID: F91F40C2-C8D2-4D23-9649-83DCADBA3F11
Product ID: 00339-10000-00000-AA937

Unfortunately the bin fix doesn't work for me :(.

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

Apparently we are not going to get any replies from Microsoft. Has anyone had any experiences with other BI software such as Tabular or Qlikview? I'm running out of time and I need to be able to offer alternatives to Excel and Power BI.

Thanks

Edited by RB Robert Brooks Monday, January 6, 2020 5:54 PM

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

UPDATE: Apparently the reason we are not getting any response from Microsoft is that the November updated caused bigger problems than just the one we reported here. Google "Forbes warning issued for millions of microsoft 10 users".

Here's some info from the article:

"Picked up by the ever-reliable Windows latest, Microsoft's Windows 10 November update is causing significant problems by breaking core elements of File Explorer. These include file search, file transfers and being, as one user described, "generally all around terrible". Windows Latest notes these bugs are "widely reported".

For its part, Microsoft has committed to investigate the issue, though Microsoft senior program manager Brandon LeBlanc has riled some affected users after tweeting "We will look into this but since it's not a pressing issue, we may not get traction until after the holidays."

"It's a very pressing issue, affecting everyone," replied one disgruntled user.

In the meantime, we can add these File Explorer issues to an inglorious list which - since September - includes BSOD crash reports, boot failures, broken printing, Search and Start Menu bugs, USB and audio problems, screen discoloration, spiked CPU usage and broken Internet connectivity.

Microsoft has promised to make fundamental changes to Windows 10 updates but, for an operating system approaching one billion users worldwide, the fruits from this need to arrive sooner rather than later. "

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

Does anybody know if we can report this issue at another level/ blog/ site/...then this place, where we would receive an answer from a MS Team with a "real" follow up on the issue?

It seems that there is not much attention from MS here.

Thank you for all additional information that would help us to move forward with this problem.

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

For those where my /bin/ upload isn't working for whatever reason, rolling back to a previous version seems like a better alternative.

You can use the method suggested by SpamXBin (support.microsoft.com/en-us/help/2770432/how-to-revert-to-an-earlier-version-of-office-2013-or-office-2016-clic) (does it required C2R?).

Or, if you have a click-to-run installation of Office (as opposed to what you have when installing Office with .msi package), you can also use this tool, which should already be on your system:

"C:\Program Files\Common Files\microsoft shared\ClickToRun\OfficeC2RClient.exe"

Rolling back to a previous version:

OfficeC2RClient.exe /update user updatetoversion=16.0.12026.20320

Version History for Office 2016/2019 C2R:

- Version 1911 (12228.20364) Dec 10
- Version 1910 (12130.20410) Nov 22
- Version 1910 (12130.20390) Nov 18
- Version 1910 (12130.20344) Nov 12
- Version 1909 (12026.20320) Oct 8
- Version 1908 (11929.20300) Sept 10

Use whichever number between parentheses, and prefix it with "16.0.", e.g. "16.0.12228.20364". I went back to the version from Oct 8, in which the issue isn't present.

For references:

- http://web.archive.org/web/20190419144959/https://blogs.technet.microsoft.com/odsupport/2014/03/03/the-new-update-now-feature-for-office-2013-click-to-run-for-office365-and-its-associated-command-line-and-switches/
- https://docs.microsoft.com/en-us/officeupdates/update-history-office-2019

EDIT:
Don't forget to disable Office updates until a fixed version is released.

Edited by dubeg Tuesday, January 7, 2020 4:21 PM
Proposed as answer by Diuuugh Thursday, January 16, 2020 8:25 AM

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

Try this workaround:

Step 1 - Create your query. In "Load To", select "Only Create Connection". Do NOT check "Add this data to the Data Model".

This will create a connection only query.

Step 2 - Insert a new pivot table on a blank tab of your worksheet. Select "Use an external data source" and select the connection only query you created in step 1. Check "Add this data to the Data Model".

This will create a second query which places the results of your connection only query in the Data Model.

After the new query has loaded, you can optionally delete the tab containing the pivot table. This doesn't seem to affect either the Data Model or the new query.

I've tried this in several scenarios and so far, this work-around has worked for me.

Proposed as answer by JoanaPat Thursday, January 9, 2020 6:26 PM

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

Hey, THANKS for posting this!

It does work, but in order to not have oddly named tables, you have to go back and delete the Original Query name and rename the (2) Query to just the table name and then right click and select refresh for that Query. You have to do that for every table you bring into the Data Model using this process and delete the workbook tab. Then, when you open the Data Model it does have the correct names of the tables you added. It's a pain in the butt to have to do it this way but at least it gets the data into the Data Model.

One other thing, when you rename the Query, it tells you the relationships are going to be deleted. It doesn't appear using this method that the table relationships came over anyway but I didn't honestly look at the diagram view before I deleted the original Query and renamed the 2nd Query that gets created when you use Step 2.

I am going to try building a few visualizations and see if anything is affected.

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

Thank you, this workaround is working for me.

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

Hi,

Thank you so much, this workaround is working!!!!

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

I also wanted to report the same problem as described in Wizard 121 (initial post).

Below my system configuration:

MS Win 10 Pro

Exceel:

MS Professional 2016 (16.0.12228.20100) 64-bit build version 1912 12325.20288)

Product ID: 00351-70004-06254-AA667

Session ID: 042BF9B0-59B8-48B4-8AB4-430C3800D3E4

Power Query version: 2.76.5678.581 64-bit

The behavior is the same as previously reported by other users, i.e. data prepared in PQ is not loaded into the prepared model, nor can new objects from PQ be added to the PowerPivot data model in MS Excel.

Please let me know if the Microsoft team is still analyzing the problem, because it is a priority for implemented business processes (analysis and control).

The @MS team: Please answer and advise.

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

I just tweeted to @OfficeSupport and @msexcel I hope it brings more attention to the issue.

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

Thank you, still waiting for a clean fix from MS Teams.

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

Thanks this worked for me as well.

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

Many thanks,

it worked.

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

Excel 2016 V 1912 Build 12325.20298

I had the same problem loading from SQL which I do frequently. In this case 3000 rows.

Simple workaround is to load the query, and while it is running incessantly, go to table properties and click refresh. For me it completes the project. Does not work if loading to the Data Model, since refresh is grayed out, but adding to the data model after the fact is simple.

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

Just FYI, Office Update Version 1912 (Build 12325.20298) did not fix this problem. Still hangs and you have to use the workaround to be able to load data to the data model.

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

Is Microsoft going to fix this issue? Are you just ignoring it, does anyone read these comments or are we wasting our time?

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

This workaround is good at the moment for small model projects. However, for large and more complicated there are chaps when there is a need for additional transformations in PQ and reloading into previously loaded data where we have already defined measures, relations and others.

Maybe people like Ken Puls, Miguel Escobar, Marco Russo, Alberto Ferrari etc. would help us in Microsoft's interest in the reported problem for obvious reasons?

Thanks for the solution and your time!

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

Two months later and a core function of their Excel Program is not functioning. Do they not support Excel 2016 anymore? Are they forcing more constant updates/renewals of their software? Are they finally addressing severe security issues with their software and it is leading their code to malfunction? Let me know if you get answers.

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

This is the only contact I've received. It was sent on Jan 16, but I didn't see it right away. I replied on Jan 23 and have not heard back. I did the first thing they asked and of course, got the continuous circle that never completes. I couldn't find legacy wizards anywhere.

"Thank you for sending Microsoft feedback. Your input is valuable to us and helps improve our products.

In order to investigate your feedback, we would like to get some additional information from you. Please reply back to this email with the results of the following tests:

Create a blank query (found under "From Other Sources"), add the text "=1" as a query and load to data model (connection only). Does it work?
i.e. when opening "Manage Data Model" window, does it display "1"?
Create a connection using one of the legacy wizards (here is how to find them) and load to data model (connection only). Does it appear in "Manage Data Model" windows?

For your reference, you submitted the following feedback on January 2, 2020:

This is to supply feedback as requested by Yehezkel Bernat in Question in Power BI > Power Query about Power Query Load to Data Model hanging up in the social technet forum.

If you have any questions, please reply back to this email.

Thank you,
The Microsoft Team

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

Hi,

worked also for me, thanks.

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

Same issue with Excel Professional 2016:

Version 1942 B 12325.20344

MSO 16.0.12325.20280

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

As long as this issue is not addressed, I will keep replying so this stays near the top of the forum.

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

Finally, it works!

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

Thank you! It is fixed!

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

Thank you! It is fixed!

Can someone share version and build numbers where this is fixed? Thanks

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

My Office updated tonight Version 1912 (Build 12325.20344) and I can once again choose Add to Data Model from the Close & Load To option in Power Query.

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

My Office updated tonight Version 1912 (Build 12325.20344) and I can once again choose Add to Data Model from the Close & Load To option in Power Query.

Thanks Robert. I wasn't affected by the issue (I run Office 365) but have a couple of friends who will like the news

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

Hi Lz.

Seems to be solved in version 2001 b12430.20184

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

Seems to be solved in version 2001 b12430.20184 FYI nothing about that in the Release notes (could be a silent fix...)

Hi JP

I thought about you when I saw Robert's reply and I was hoping you would come here because things were not and are still not clear to me: on the MS forum you said you were running v1912 build 12325.20344 and experiencing the issue. Now, Robert says v1912 build 12325.20344 (so the exact same version & build) fixes the problem on his side ???

@Robert,

For the sake of clarity could you double-check the version+build you currently run

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

Version 1912 (Build 12325.20344). I'm certain.

From earlier in this discussion my Version and build was: Office Update Version 1912 (Build 12325.20298)

Edited by RB Robert Brooks Sunday, February 2, 2020 2:35 AM

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

Hi Lz.

I'm pretty sure about the version that I mentioned before. Robert has a Pro Plus while I have a Pro version. It looks as the version and build numbers depend also on the product.

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

Hi Robert & JP (edit your post pic. => email address)

THANK YOU very much guys, things are a bit more clear. As JP pointed this could be Pro vs Pro Plus. Haven't had a chance yet look at the various versions on the release notes page yet...

Anyway, I don't think I'm the person who will and should definitively clarify which Home, Pro, Pro Plus… version and build number that addresses the issue. On that thread Ehren said Updates about this issue will be posted there (meaning this thread)
Versions+Builds you guys refer to are from Jan 30th so it's reasonable to think they simply haven't had the time to post the information yet

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

Yehezkel,

Excel team

Edited by Yehezkel BernatMicrosoft employee Sunday, February 2, 2020 6:14 PM
Marked as answer by Imke FeldmannMVP Monday, February 24, 2020 9:57 PM

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

I've just updated Excel and now it works, it loads the data to the data model without any hiccups.

Excel version of 2016 professional plus now shows "version2001 compilation 12340.20184

Thank you Excel team

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

Many thanks. Very frustrating bug (I wouldn't call it that even given it is so pervasive) given it's such core functionality so the wait felt very long, but all is well that ends well. Hopefully we don't see such a wait again.

Thanks to Duyarra, Yehezkel, and Lz._ for navigating both forums.

In other news, nothing I have done to try to get notifications working here has worked since my first post, even with the help of the Microsoft MVP in previous posts I outlined here.

As such, I likely will not use technet again and go to Microsoft Answers or somewhere else. I didn't know this thread had so much activity, until I got a series of alerts on the Answers thread that's the sister to this one.

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

I restored the original version.At least your approach has worked so far.

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

Why is Microsoft Mashup Evaluation Container consuming so much RAM

Hi -

I am working with multiple large csv source files in power query. All of my queries are disabled by default during development and I load them to the data model when testing, and then unload them. My workbook is about 40KB in size.

But when I open the workbook and I click on "Enable Content" for External Data Connections (queries still disabled) I will see 4 or sometimes 6 Microsoft Mashup Evaluation Container tasks (Microsoft.Mashup.Container.NetFX40.exe) in the Task Manager, each consuming 200-250MB.

Can you please tell me what these tasks are for? Why are they started with this workbook?

Thank you,

Rory

Hello Rory,

Sorry for the large RAM consumption the Mashup Containers are causing. These are in fact evaluating the preview cache eagerly in the background so by the time you click on one of the queries the preview loads immediately.

We understood that the side effect of this is sometimes undesirable. Hence we are looking at ways to address this problem.

Regards,

Peter Q. http://blogs.msdn.com/peter_qian

Marked as answer by R Noone Friday, October 17, 2014 11:12 AM

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

Hello Rory,

We understood that the side effect of this is sometimes undesirable. Hence we are looking at ways to address this problem.

Regards,

Peter Q. http://blogs.msdn.com/peter_qian

Marked as answer by R Noone Friday, October 17, 2014 11:12 AM

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

I'm having the same problem with a CSV source. I have a lot of Power Query steps, but each step is simple.

There are only a couple hundred rows in the CSV file, but I get three separate Microsoft.Mashup.Container.NetFX40.exe files running that together take up 75% of my CPU as soon as I open the Excel file.

They never free up the CPU. I even let it run overnight, but they continue to use 75% the next morning.

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

Yes, I've been having the same issue. It would be great to just have an option somewhere to disable the automatic calculations of these previews.

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

I have the solution, or a parcial solution, I tried with Power Query 2.23 and I had the same problem you have, but if you disconect your computer from internet, the cpu gets the nomal level, 3% or 4% max.

I update to Power Query 2.24 and I get something new, if I wait like 1 minute doing nothing, the cpu gets to 75% and then slows until 20 % and then you can work perfect.

They are close but not enought. Let's wait

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

Thanks for the report Raimundo!

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

I'm experiencing the same issue with either .csv files or excel files. Is there any workaround to this?

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

I see it was being looked into 3 years ago now. I'm new to Power Query in 2017 and I'm
seeing

3 x Microsoft.Mashup.Container.NetFX40.exe

each consuming 23% of my CPU load even though all the PQs and connections are within the same workbook which itself has only 500 records.

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

Same thing - AMD FX-4350 CPU is overheating because this Mashup thing is trying to do something in the background, and this has been noted since 2014?!? How long is Microsoft going to think caching is the answer to everything? It's "fake" performance, folks, has been since Access 1.0.

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

Hi there,

It appears I'm not the only suffering with this problem. I have three large Data set which I have many Excel Power Queries working off from. I'm hitting 2.7GB of RAM, now The outputs are simple Excel tables.

Is there a solution, or better ways to mash up the data to use less RAM etc.?

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

This problem is about to render Power Bi unusable...... This thing is running up 5-6 instances with each being 200mb. I have disabled the auto background refresh in the data source settings. The reports only need to refresh 1 time a day. Why should they occupy this much RAM 24/7? Really hoping there is a better solution.

Edited by Eric - EnvisionHealth Monday, August 7, 2017 2:49 AM

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

I haven't noticed these Mashup's until lately. Are they a direct result only from setting up a Power BI Subscription or something PowerBI related? I have been using PowerQuery a lot more that past few months and only noticed these Mashups this week and I setup my first subscription on BI to generate last Friday.

I agree with all of you, they are eating up 50-200k a process and running at least 4+ at a time. Really needs a fix fast.

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

I submitted this as an issue to Power BI some weeks ago and got the same "we know it's an issue and we're looking into it." Agree with the poster who says this issue is about to render Power BI useless. It's ridiculous how much load these processes take. I didn't know you needed a server to use Power BI...

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

Hello Peter

I am working with a few fairly large, but not ridiculously large, csv files and Power BI has now become all but unusable. A fairly straightforward load now takes 30 minutes, and this happens every time I change a single line in any query.

Do you, or anybody, perhaps know whether there is a way to make this workable again?

Thanks

Wilhelm

Wilhelm van der Merwe | Sydney, Australia

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

Good Day All,

I am facing same issue in Excel 2019 (64 Bit), while using Power Query. I work on i7 processor with 16 GB RAM, still as soon as I open the excel file CPU consumption hits 90-100% only on 64 bit. Is there any way to fix this or this is a bug which Microsoft needs to fix.

Thanks

Nasir

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

Its August 2020 and is still happening (Office 365, Win 10 Enterprise v1709, 64 bit)

Is there a solution that I am missing?

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

There is a solution available, you can choose to disable background refresh.

Here's a blog that discusses the settings:

https://www.excelinppc.com/recommended-power-query-settings/

This paragraph:

The important option in CURRENT WORKBOOK Data Load is "Background Data". You can tick or untick "Allow data preview to download in the background". When ticked, this feature allows to cache ALL the queries within the file in the background.

Regards,

Peter Q. http://blogs.msdn.com/peter_qian

Proposed as answer by Meester2089 Thursday, November 5, 2020 6:10 AM

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

Thanks very much for this solution!!

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

"The task sequence has been suspended. LiteTouch is trying to install applications. This cannot be performed in Windows PE."

MDT 2012 Server is up and running. I mistakenly deleted a Task Sequence step called "Install Application" that I thought was not needed (I know I should have disabled it and tested).

I have a problem now, when I went to image a computer I did not get application list (This used to work before I deleted the above TS step) with items to check and uncheck for installation. "Install Application" TS was readded but now when I try to image I get this error:

"The task sequence has been suspended. LiteTouch is trying to install applications. This cannot be performed in Windows PE."

I've tried moving it to different positions on the list (Higher and lower) to no avail, I always get the same error. Please advise.

-Thanks in advance!

Edited by MDT Padawan Tuesday, October 2, 2012 9:34 PM

I had to clear the partition. This resolved the issue.

Marked as answer by MDT Padawan Tuesday, October 2, 2012 9:51 PM

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

I had to clear the partition. This resolved the issue.

Marked as answer by MDT Padawan Tuesday, October 2, 2012 9:51 PM

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

What do you mean by "clear the partition?" I'm having the same problem.

Clear the partition on the workstations or on the MDT server?

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

On the computer you are deploying to "the client", boot into WindowsPE just like you are going to image and before you authenticate or get any dialogue boxes, press F8 in WindowsPE to get command prompt and type the following:

diskpart
list disk
select disk 0
list part
select part 1
clean
create part primary
assign
active
exit

Please mark this as the answer if it works.

Proposed as answer by fubeca6 Wednesday, February 20, 2013 11:55 PM

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

I'm doing this on 20 computers, is there anyway you think I can put this in the task sequence? Why is this error happening? I'm not installing anything through winPE other than the OS.

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

My best advise to you is to try it on 1 computer first. Then if it works you can work on a way to do it on all of the other computers. In my situation everything was working for me before this error. I made a change and then this problem occurred. I removed the Install Application task sequence step, I did not keep trying to deploy on different computers, just the 1 I was testing with. If this is happening on a computer that you did not have a failed deployment with, this may not be the solution to your problem.

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

On the computer you are deploying to "the client", boot into WindowsPE just like you are going to image and before you authenticate or get any dialogue boxes, press F8 in WindowsPE to get command prompt and type the following:

diskpart

list disk

select disk 0

list part

select part 1

clean

create part primary

assign

active

exit

Please mark this as the answer if it works.

Great!! worked for me...

thanks a lot :D cheers

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

That worked for me ..thanks

Proposed as answer by Genoxidec Monday, August 12, 2019 7:51 AM

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

On the computer you are deploying to "the client", boot into WindowsPE just like you are going to image and before you authenticate or get any dialogue boxes, press F8 in WindowsPE to get command prompt and type the following:

diskpart

list disk

select disk 0

list part

select part 1

clean

create part primary

assign

active

exit

Please mark this as the answer if it works.

You are awesome this worked for me I didn't see how I was going to get my new computer to reimage again Thank you sooooooooooooo much!!!

Proposed as answer by Anonymous Noob Sunday, December 17, 2017 6:16 AM

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

I used gPart to purge the partition on the drive, which resolved the issue. Thanks for the tip everyone!

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

Awesome! This worked like a charm. . . . Thanks

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

This worked for me as well. Thank you!

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

Thx, saved my Life xD

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

Awesome..... this worked for me... thanks a lot dude..! :) :)

Regards Rushikesh..

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

In my case I only did part 1-6 (and 9) as my MDT image will carve up the partitions itself as it does with new/wiped disks.

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

Hmmm, this sound good, but when i press F8, i get the list with all the opportunity with F:1,2,3,6,7,9,10 and 12, but no F8.

Is there another way to solve this issue?

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

Found the Solution:

Solution;

Open Bios F10, go to security, in Utilities to Hard Drive Tool, Utilities Secure Erase

After that you should be able to rebuild the pc.

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

FYI: The simple reason is that once the hard drive is partitioned and formatted MDT will create a MININT folder with the scripts and task sequence info. Let say something goes wrong during deployment and you decide to start a new deployment. When you boot back to your MDT boot image it will attempt to read what is in MININT and continue from there.

All you really need to do is delete the MININT folder and restart. Wiping the disk isn't needed but you're welcome to do that if you want to.

If this post is helpful please vote it as Helpful or click Mark for answer.

Proposed as answer by january19 Monday, December 19, 2016 1:09 PM

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

Worked for me! Cheers

Christopher Valentine

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

Perfect! Worked great, thank you.

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

:D <g class="gr_ gr_9 gr-alert gr_spell gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="9" id="9">excelent</g>, this comment helps was very very useful for me, I only add that I need to enter in the <g class="gr_ gr_487 gr-alert gr_spell gr_run_anim ContextualSpelling" data-gr-id="487" id="487">advance</g> options for <g class="gr_ gr_90 gr-alert gr_spell gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="90" id="90">litetouch</g> and select the option "save mode".

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

I have never been able to delete the MININT folder because in most cases I cannot boot to the system to do so. My situation is mostly a device that will pick up where MDT left off, but it tries to install software while in WinPE. That's not allowed, so it loops, endlessly, to the same point, installing in WinPE. Booting back to MDT but getting to DOS and running the format is the only way for me. I just wish MDT would erase the MININT after EVERY attempt - I know it failed, I just want to start over fresh, but it hangs onto every previous failure. Would be nice to see that gone.

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

Using MDT you could easily build yourself a generic WinPE boot image and boot to that. Or don't skip the welcome screen, then from the welcome screen press F8 and delete the MININT folder from the command prompt.

It's better that MININT isn't deleted automatically during an early failure in case that's the only place in which to grab logs.

If this post is helpful please vote it as Helpful or click Mark for answer.

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

Thank you so much for the info. It worked for me. Initially I had a struggle to find out where I need to press F8. Finally by reading the post closely I realized that we just need keep pressing F8 after selecting the MDT Media( with Key board support) and there we go.. command prompt poped up after few min..

Make sure you select the DISK 0 during the diskpart i.e. which could be the Hard disk... not the USB drive and follow the steps. This diskpart clean up should be deleting the MININT folder which has the app install logs where they left off.

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

Thanks for the deep info on this.

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

I know this Post is a very old one, but some might to have this issue anyway.

For me it would worked too, but it was due to failed autologon with local Administrator. The machine tries to log on and run the script litetouch.wsf.

So i had the Folders _SMSTaskSequence and MININT still there, also the DeploymentShare.

All i needed to do ist starting manually the script C:\MININT\Scripts\Litetouch.wsf by an elevated commandline. The deployment will resume, install application, cleanup, etc.

Also you will see in Deployment Workbench, machine is now deployed 100%.

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

Worked for me. Thanks!

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

For me, it got stuck at "Litetouch is trying to install Windows Updates", but same fix. Thank you!!! Seems this disk wipe fixes a lot of MDT errors I've had so far.

Edited by acatic Wednesday, March 7, 2018 4:55 PM add'l info

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

I had to clear the partition. This resolved the issue.

Thank you!

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

Thank You!

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

FYI you can cut it down to just:

diskpart
select disk 0
clean

You don't need to bother recreating a partition or formatting as MDT will do all that for you.

Daniel Vega

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

On the computer you are deploying to "the client", boot into WindowsPE just like you are going to image and before you authenticate or get any dialogue boxes, press F8 in WindowsPE to get command prompt and type the following:

diskpart

list disk

select disk 0

list part

select part 1

clean

create part primary

assign

active

exit

Please mark this as the answer if it works.

This worked for me in 2019! Thanks!

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

Worked for me. Attempted to lay down an image from usb but it froze when installing a certain application. It appeared the image took and the computer was working fine but I noticed the app I needed was not there. From there the computer would no longer read my usb and gave me the above error. This fixed it and I was able to begin reimaging from scratch.

Edited by Michelle wardlow Monday, July 1, 2019 1:16 PM

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

On the computer you are deploying to "the client", boot into WindowsPE just like you are going to image and before you authenticate or get any dialogue boxes, press F8 in WindowsPE to get command prompt and type the following:

diskpart

list disk

select disk 0

list part

select part 1

clean

create part primary

assign

active

exit

Please mark this as the answer if it works.

I LOVE YOU MAN!

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

FYI you can cut it down to just:

diskpart
select disk 0
clean

You don't need to bother recreating a partition or formatting as MDT will do all that for you.

Daniel Vega

I agree.

Also if you need the EFI partitions is better leave the system make it for you for UEFI installations.

with the first 3 steps is sufficient.

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

perfect, it works for me

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

Worked great for me. Thanks!

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

Ms Support forum

Wednesday, January 12, 2022

https://social.technet.microsoft.com/Forums/en-US/a9522a63-6fcf-48f2-9455-e42354a32d01/quotthe-task-sequence-has-been-suspended-litetouch-is-trying-to-install-applications-this-cannot?forum=mdt

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

Power Query Load to Data Model -- Constantly Stuck/Hanging

Why is Microsoft Mashup Evaluation Container consuming so much RAM

"The task sequence has been suspended. LiteTouch is trying to install applications. This cannot be performed in Windows PE."

No comments:

Post a Comment

Setup is Split Across Multiple CDs

About Me