This is the second post about issues that one of our client's found recently when they transitioned from BPOS to Office. You can see all of these issues in Support Stories
. This time, we're talking about an issue that lead to a significant number of users being unable to access the transitioned site collections. Just to be clear, all users could access the default SharePoint Online site collection (the Team Site found at companyname.sharepoint.com
Users Can't Access Transitioned SharePoint Site Collections
So, this was a strange issue for us. After transition to Office 365, whenever quite a few users tried to open up one of the transitioned SharePoint site collections, the connection would just time out and give one of the very useful 'Microsoft Online Services is unavailable from this site...' messages. I contacted Microsoft's transition support team and they gave a terribly simply solution, outlined below.
- In Internet Explorer, on the Tools menu, click Internet options.
- Click the Security tab, click the Trusted sites zone, and then click Sites.
- Verify that the following entries are listed in the Websites list:
If these entries are not present, add them to the Trusted sites list of websites.
Now, go back to the Security tab and click Local intranet zone, click Sites, and then click Advanced.
Add the following entries are listed in the Websites list:
One of our clients was recently transitioned from Microsoft's BPOS (Business Productivity Online Suite) to Office 365 as part of the upgrade cycle for Microsoft's Online Services. We encountered a few issues which we resolved, occasionally with (excellent, as always) support by Microsoft's support team. We're going to take the time to highlight a few of the issues that we encountered, in the hope that this will help other BPOS administrators in the future.
You can see all of these issues in Support Stories
. We'll start with an issue related to workflows, which was easily solved.
We encountered two issues with workflows post-transition to Office 365. The first was that none of the workflows would start at all, the error given in the workflow status being "[Workflow name] failed on Start". This happened for all of the workflows that we had created on the SharePoint site collections that transitioned. The (admittedly very simple) solution for this was to open up SharePoint Designer 2010 (remember, once you've transition to Office 365 you need to use the 2010 version of the programme, not 2007), then open the workflow and press the 'Publish' button on the taskbar - simple!
The second issue was that any issues in-progress during the transition failed when they tried to continue. For this client, this meant that there were a number of workflows which, before transition, had paused for a short amount of time. After transition, these workflows did not restart and the workflows failed. There was no way to directly fix this issue, the only thing to do was to start the workflows again.
Here's hoping this helps to indicate any potential issues that you might have with transitioning from BPOS to Office 365. We'll have more coming over the next few weeks under the category Support Stories
, come back then, sign up to the RSS feed
or join our newsletter
With the beautiful day that it was on Monday, I was lucky enough to be working out in Co. Kildare for the day. In fact, if you look below, you'll see that I was actually just working in a field! This didn't prevent me from working at all though, in fact the day was extremely productive. The combination of a USB modem and Office 365 meant that it felt like I was at my desk, but in the beautiful sunshine! I even managed to run two Lync Online meetings: One a development meeting and the other an introduction to using Lync for online meetings, which involved (among other tasks) me sharing my desktop to show how to set up Lync Online meetings and explaining the best techniques in hosting online meetings.
Working From Wherever - Using Lync Online from Office 365
This was a great learning experience for me - with a USB modem (and a relatively decent Internet connection), I was able to work from a field. This means I'm not as tied to the office as I would otherwise be - I can work from wherever I want.
Lync Online is one of the components of Office 365
. Contact Conor in TaskLight today on 01 901 0304 or firstname.lastname@example.org
to start your free 30-day trial of Office 365
and discover your dream office.
Believe it or not, it is entirely possibly to hit the 5000 item limit that is put in place for any view of lists in SharePoint Online in Office 365. If you do hit this, you will find an error telling you that the item limit set by the administrator has been exceeded.
There is a limit of 5000 items in any view on a list - if your list is going to get anywhere near that limit, use an indexed column and then create filters that make sure that you won't go beyond 5000 items in a view. For example, limit a view to the last 12 months of data, or limit the view to 4000 items.
If you find yourself in the situation where you can't do anything with the list, having exceeded this 5000 item limit in the default view, you won't even be able to delete the list! If this happens, open the list in SharePoint Designer 2010, then click 'Administration Web Page' in the 'Manage' group on the ribbon. The ID is indexed by default, so create a view that is that is guaranteed to return less than 5000 items, using filtering based on the ID of the column. Now, go into that view and move out enough of the items in the list to get you below the 5000 item limit. Once that's done, you can create a new indexed column (or maybe more than one). Now, edit your views to filter based on those indexed columns. Good to go!
Again, prevention is better than cure here - It took me a few hours to find this work-around and you should always aim to reduce impact on users. After I first encountered this issue, I future-proofed using the tips above (indexing and view limits) to make sure that this wouldn't happen for other lists.
I hope this has helped a little bit. Drop a comment below if you have any questions or comments.