I have recently been working on a Multi-tenant Web Application that makes use of delegated permissions. After developing the application for a while I found that I needed to add another delegated permission to the application which I did using the normal methods. However, when I tried to make use of the new delegated permission with the test user I had been using for a while I didn’t get prompted for the application’s consent as I did originally and I ran into the error:
Its not very clear fromt he documentation that adding an ACL also affects internal virtual network communications as well as external endpoint access on the port defined. For Example: If you have two machines in different services connected via the same virtual network and are using the internal subnet IP for communication, the ACL will be applied to the traffic on the internal IP aswell as the external IP/Endpoint you apply it to, even if your not accessing the port via the external IP/endpoint.
After the correct updates have finally been released last week (Exchange 2010 SP3 and Exchange 2013 CU1) it was time to get some Guinea Pigs… sorry, “Test Users” migrated over to Exchange 2013. Some of the very small mailboxes were fine, but when it came to a real users mailbox the progressed appeared awfully slow. After taking a look at the log, I found it was full of: The job is currently stalled due to ‘Content Indexing’ lagging behind on resource ‘CiAgeOfLastNotification()’
I’ve been migrating classic mode SharePoint 2010 sites to claims sites for a while now, so much that I even have a script to do it for me. However, for some reason I have never come across the problem I encountered today. The documentation on converting a classic mode web application to a claims based application I though was pretty solid on technet. Today I came across a strange issue where the site collection administrator was getting access denied in odd locations… or locations I thought were odd because SharePoint hadn’t security trimmed the links as I thought it would if access really was denied.
If your trying to setup or change the configuration of SharePoint on a development machines which has Office 2013 install you may encounter some strange errors relating to types such as: Failed to call GetTypes on assembly Microsoft.Office.InfoPath.Server, Version=126.96.36.199, Culture=neutral, PublicKeyToken=71e9bce111e9429c. Could not load file or assembly ‘Microsoft.Office.InfoPath, Version=188.8.131.52, Culture=neutral, PublicKeyToken=71e9bce111e9429c’ or one of its dependencies. The system cannot find the file specified. This is related to the way in which SharePoint is loading certain assemblies and struggles with the new assembly for InfoPath.
I recently found a small bug in the SharePoint 2010 PowerShell comlets for creating the state service database using “New-SPStateServiceDatabase”. You will receive the rather unhelpful error message “Operation is not valid due to the current state of the object”. I believe this is a generic WCF error as that’s all I was able to find when researching what may cause the problem. However, it later transpired that this was because I was trying to use a database alias (or potentially database server) which SharePoint isn’t currently aware of, as using the alias (or database server) that was used for the initial farm setup didn’t result in the same issue.
Upgrading Lync to 2013 recently I came across a problem where the front end service simply wouldn’t start but would get stuck in “Starting” mode. I spent quite a bit of time trying to figure out what the problem was and got caught up in some false information on the technet forums that it was related to Server 2012. In fact the problem was fairly simple if you know whats going on under the hood.
Symptoms Multiple Upload is disabled along with the Explorer option on Document Libraries. Resolution This problem is usually caused by a mismatch with Office and Internet Explorer. If you are workign on a 64bit version of Windows you will have two Internet Explorer links, one which opens the 32bit version (x86) and another which will open the 64bit version. The client integration options will only be available in the version which matches your office bit version.
After moving a few Windows Server Hyper-V hosts recently from one Virtual Machine Manager server to another, a couple of virtual machines started exhibiting some strange behaviour in regards to networking. So I break out trusty “ping” and it doesn’t report any problems. At that point the remote desktop session is working again so I lost interest assuming it to be “one of those things…”. After a couple of days this started happening more and more.
The sysprep automation within Virtual Machine Manger 2008 is a really nice feature which can help you deploy machines quickly and in a “set and forget” manner. If however you are unfortunate enough to not run your servers in the US locale you may have noticed that even if you change all the regional settings on your template target, after the sysprep has completed and produced a template any machine generated from it will be in the US locale.
Came across a problem recently while on site with a client which I have never come across before. If you are trying to test your SharePoint Server web applications locally on a SharePoint server and you find that it is refusing to accept the locally logged on user or another user who should have access to the site by asking for your credentials 3 times before telling you that you don’t have access, it is because of a security feature within IIS which will not allow the use of integrated security for a hostheader that is not the server’s hostname.
Well i’ve been at it a couple of hours now and i’ve gotta say that Lync 2010 is WAY easier to install and setup compared with Office Communications Server 2007. Loving the new topology tool and the migration of users from one to another is seamless. The new control panel is awesome too, no longer do you need to use the manager and AD to get users into Lync and as an added benefit the management interface is all Silverlight and follows a similar model to Exchange where there are lots of uses of policy’s which can be moved up and down similar to exchange policy’s Microsoft.
Today when upgrading a products codebase from Visual Studio 2008 to Visual Studio 2010 I discovered that Microsoft have removed support for smart device projects in Visual Studio 2010. The decision to exclude support for smart device projects in Visual Studio 2010 appears to be a clear sign that Microsoft does not intend on continuing the Windows Mobile roadmap independently of Windows Phone 7. Windows Phone 7 is clearly targeted at the consumer space to complete with the likes of Apple iPhone and Google Android.
Message Queues are a great tool for interprocess communication if you need to ensure that a message is processed, regardless of the target process’s connectivity or runtime state. If you are developing with Microsoft’s .Net Framework you can take advantage of Windows Communication Foundations built-in support for Microsoft Message Queues. I have been using WCF with Microsoft Message Queues on a recent project, which as part of a back-end processor, the queues are automatically created in the event that they do not exist.