Hi, lbarnhart.
Thank you for the update.
I'm glad to hear that the upgrade worked and that you and your Superintendent are able to successfully use the apps.
Also, thank you for the feedback on your user experience with the software update. I will be sure to share that information with the team for future improvements.
Thanks again! If you have any additional support needs, please let us know.
XAS Moderator
We fixed the problem with software upgrades. We upgraded the two copiers to 100.002.068.26100 and made sure the apps where version 3.0. The upgrade did take a good twenty minutes so that is something to think about when you do a software upgrade.
Hello, lbarnhart.
Apologies for the delayed response.
This may have something to do with folder permissions or folder/file names.
If the Superintendent logs in to Office 365 using the web portal, can he access the folder that the app is failing to scan to?
A couple additional questions to help us troubleshoot:
Using the app at the device, can he scan to other folders?
What is the Folder name that he is trying to scan to and is failing? Does it contain any special characters?
What is the folder path for the folder that he is trying to scan to? This might look something like this: https://yoursharepointservername.com/teams/YourCollectionSite/SitePages/Home.aspx?RootFolder=%2Fteam...
I hope that this is just a permissions issue, but if not please share the answers to the questions above and will will look into this for you.
Thank you and again so sorry for the delay.
XAS Moderator
Our organization has been using the Xerox C8045 and the weblet Connect to Office 365 without any problems. Recently our superintendent is able to log into his account, but when he selects the folder he wants to scan a document to, the weblet acts like it is refershing and then displays the message cannot connect to this service please check Internet connection. I tried my account yesterday and today and I don't have any issues selecting folders. Any ideas on what direction to look at. Our local vendor said it is a Microsoft issue. I looked at that, but haven't found any useful information.