UtterAccess.com
X   Site Message
(Message will auto close in 2 seconds)

Welcome to UtterAccess! Please ( Login   or   Register )

Custom Search
 
   Reply to this topicStart new topic
> Users Having To Sign Out Then Back In, Any Versions    
 
   
accessDatabase
post Mar 1 2017, 09:16 AM
Post#1



Posts: 40
Joined: 17-December 15



Hi, I have an Access 2013 front-end pointing at Office 365 Sharepoint backend. The users are on Access 2016.

Recently quite a few of my users were getting the spinning blue circle when they opened the front-end. To fix it they had to log out of their Office365 account in their local MS Access and then log back in. This then allowed them to re-connect to the SharePoint backend and the database opened normally. Is this something that SharePoint requires from time to time or does it require a fresh log-in after a certain number of days of inactivity?

Any information or advice welcome!

Thanks!
Go to the top of the page
 
ranman256
post Mar 4 2017, 07:05 AM
Post#2



Posts: 729
Joined: 25-April 14



As it should be. You shouldn't leave secure connections open and unattended.
Go to the top of the page
 
accessDatabase
post Mar 7 2017, 06:50 AM
Post#3



Posts: 40
Joined: 17-December 15



Hi Ranman, thanks for your reply. Are you suggesting that this is an official safety procedure by Office365? If it is, do you know how what the timings are and why it doesn't warn the user?

I should clarify that the connections aren't being left open and unattended. Users close the database down and if they try to re-open it again after a pause of a few days, Access reports that they are signed in and 'Online with Sharepoint' (Access remembers their login), but the spinning circle on attempting to make first connection to the backend data is as far as it goes. If this is an intentional safety feature it is not informing the user of what is going on or what is required to resolve it.
Go to the top of the page
 
accessDatabase
post Jun 1 2017, 05:51 AM
Post#4



Posts: 40
Joined: 17-December 15



Hello all,

Does anyone know if there is a time limit of inactivity on a SharePoint backend before the user has to log their MS Access front-end out of Office 365 and log back in to get access to the SharePoint backend?

This is becoming quite an issue for some users, would really appreciate a steer on this.

Thanks!
Go to the top of the page
 
accessDatabase
post Jun 5 2017, 06:12 AM
Post#5



Posts: 40
Joined: 17-December 15



Is there a more suitable forum I should be addressing this question on?
Go to the top of the page
 
accessDatabase
post Jul 14 2017, 07:24 AM
Post#6



Posts: 40
Joined: 17-December 15



Is this something to ask MS directly? If so, I can't find where they are?!
Go to the top of the page
 
Dan Dungan
post Jul 14 2017, 01:32 PM
Post#7



Posts: 242
Joined: 20-July 10
From: chatsworth, ca


Hi,

I googled "Sharepoint unresponsive" and found this link:

Sharepoint unresponsive

HTH

--------------------
Dan
Go to the top of the page
 
accessDatabase
post Jul 17 2017, 08:06 AM
Post#8



Posts: 40
Joined: 17-December 15



Hi Dan,

Thanks for the link. I read it through but I don't think it was quite the same issue that I've been having.
I posted a question on that forum however. If anything comes of it I will post it back here too.

Have you come across this kind of timing out on any of your Sharepoint backend systems?
Go to the top of the page
 
Dan Dungan
post Jul 17 2017, 01:32 PM
Post#9



Posts: 242
Joined: 20-July 10
From: chatsworth, ca


Hi Accessdatabase,

I don't have sharepoint, so I can't be of much more help.


--------------------
Dan
Go to the top of the page
 


Custom Search
RSSSearch   Top   Lo-Fi    26th July 2017 - 01:33 PM