I’ve recently been trying to get a DS18B20 working with the Raspberry Pi, and although its well documented around the internet I ran into a bit of an issue where mine was always returning t=85000. Although alot of people claims this is wiring (which could be the case) for me it was actually to do with how it was reading the value in the kernel module. Originally in modules I had:

Been looking for something like this in a while to test newly setup or existing SMTP setups for simple server notification or business applications e.g. SharePoint, as it saves you having to install telnet or putty in order to send a quick test email to make sure its not getting blocked somewhere i.e. spam: ## Update ## Just found out there’s an actual powershell Cmdlet for this: Send-MailMessage! $msg = new-object Net.

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.

Came across and issue during the deployment of Office Web Apps 2013 when hooking up with SharePoint which caused some confusion. Issue: Error messages from the web apps when activating through SharePoint documents: Word Document : “Sorry, there was a problem and we can’t open this document. If this happens again, try opening the document in Microsoft Word.” Excel Document: “We couldn’t find the file you wanted. It’s possible the file was renamed, moved or deleted”

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=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c. Could not load file or assembly ‘Microsoft.Office.InfoPath, Version=15.0.0.0, 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.

As I started to configure our new SharePoint 2013 farm today I came across a problem when running the pre-requisites tool when it was attempting to install “Application Server and IIS Web Server roles” which resulted in very little in terms of error messages apart form “configuration error”. After much searching and reading on Technet I wasn’t able to find out exactly what roles and features needed to be install so I could do this step manually.

Everytime I have to open log file I always wished it would update on its own so I didn’t have to close it and open it again. I know applications like visual studio notify you when a file updates but its usually not a good idea to install it on the production machine and across the network access can be painful. In comes PowerShell to save the day… And its install on pretty much all modern windows servers these days as standard.

If anyone has been using Volker Bandke’s turnkey-mvs trying to change their password using the provided job in SYS2.JCLLIB.CHGPWD and then noticed that they are unable to login, the provided job has a slight flaw in it that actually changes the username and not the password. Original Script (Lines 21-23) ACCOUNT CHANGE (_theuid) DATA(_thepass) END The job jcl should in fact be: ACCOUNT CHANGE (_theuid _curpass) DATA(_newpass) END This will then successfully change the password for the account, however please note that the target user will need to be logged off of TSO.

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.