For all the folks out there still running Windows XP, you will be in for a surprise when you go to upgrade Quickbooks. Starting with Quickbooks 2015, you can not install it on Windows XP. I haven’t tried all the possible workarounds yet, but the installer will check to see if you are running Windows XP and will prevent you from continuing. You can also see the list of requirements for Quickbooks 2015 here.
If I discover a workaround, I will post it. However, I highly recommend that you upgrade to Windows 7 or later. It’s way past time for you to upgrade. 😉
I had a customer call me to say that his computer seemed to freeze for him, so he did a hard restart on it. Once it booted back up, Microsoft Outlook 2010 would not start but give the following error message.
Cannot start Microsoft Outlook. Cannot open the Outlook window. Invalid XML, the view cannot be loaded.
Starting Outlook in safe mode didn’t work either. Fortunately the fix is really easy.
If you are on Windows 7 simply type the following command in the search or run box.
Its been very interesting to me seeing all the changes that are occurring in the domain space, especially with all hundreds of generic top level domains that will be flooding the market this year. I’ve been experimenting with a new gTLD domain name and seeing if its possible to setup in Office 365. Unfortunately, there doesn’t seem to be very good support for the new gTLD domain names currently. I’ve been running into several brick walls. The very first thing you will notice is that you can not add a generic domain name, the field verification requires it to be a domain that ends with .com or similar extension.
Fortunately there is a fairly easy workaround for this issue. Yup, you guessed it. Powershell!! This article gives step by step instructions on how to add a domain to your office 365 account via powershell. Here are the concise steps if you are already used to using Office 365 & Powershell.
Connect to your Office 365 account using the command “connect-msolservice”. (without quotation marks)
Use the “New-MsolDomain” cmdlet to add your domain. Just like this “New-MsolDomain -name example.technology”
Bingo! It works.
I was even able to verify the domain
The problem is I’m now stuck on Step 2. Which is the step where you need to “Setup Office 365 and keep your website where it’s hosted today”. It gives an error message that “Sorry, we couldn’t save that. Please try again.”
Grrr.. So I’m still stuck. If anyone has any tips, feel free to comment. Otherwise I’ll update this post once I figure out to continue.
Update 3/3/2014: I’ve discovered that at this point it is not possible to use a generic top level domain with Office 365 Small Business and Office 365 Small Business Premium. I upgraded my account to Office 365 Mid Sized Business, and I was able to add, verify, & activate the domain name following the steps above. So in short, if you want to use a new cool domain name, make sure you are using Office 365 Mid Sized Business plan or any of the Enterprise plans.
I was attempting to restore an Active Directory User that was accidentally deleted on a SBS 2011 server using the steps outlined in this Microsoft KB Article, however I kept coming up short with the following error message.
“Error 0x2077 Illegal modify operation. Some aspect of the modification is not permitted.”
I was a bit stumped until I read a few of the comments on that article. If you are experiencing this error, check out these tips by Brandon in the comments. Worked perfectly after I followed these steps. Thank you, kind sir.
Insure that you are connecting to your DC by using LDAPS (SSL, port 636)
When performing the rename operation using LDP.exe, insure that you are changing the distinguishedName to an object that doesn’t exist. In my case, I received this error when I forgot to include the computer’s name in the DN (meaning, I only had OU=x,DC=y,DC=z instead of CN=Server,OU=x,DC=y,DC=z)
If using powershell and you receive this error: use LDP.exe and insure you are using LDAPS and a DN that doesnt exist
Yesterday Microsoft released a few updates for Windows & Office. One of the updates, KB2817630, appears to break Outlook 2013. The screenshot to the right is what happened to one of our customers after the update was automatically installed. Absolutely no folders appear in the folder pane.
At this point it appears the fix is to install this hotfix available from Microsoft. Update: Hotfix has been pulled for some reason.
After installing Extensis Portfolio Desktop Client software on a few Windows 7 desktops today, we noticed that after rebooting the computers would no longer connect to the internet. They could access local files & services, but the network connection was local only.
After a bit of digging, we discovered that a service called Bonjour was installed and running. I stopped the service, set it to disabled, and restarted the PC. This fixed the issue. It didn’t seem to affect how Extensis Portfolio operates, so I’m not sure why they are installing the service. A quick google search shows quite a few people with Bonjour network issues, so apparently it is a service used by quite a few software vendors.
On several occasions I’ve noticed that Comcast seems to be blocking port 25 on their internet connections. This, of course, is an issue for SBS 2011 networks and outgoing SMTP email. For most cases I use a Smart Host for outbound email such as DynDNS. However, the built in wizard for configuring the Smart Host does not allow you to specify which port to use. Fortunately, with two simple powershell commands you can change this.
Open Exchange Management Shell (EMS) as an administrator.
Type the following cmdlet to list all the current Send Connectors.
Using the SMTP Send Connector name extracted from the above cmdlet type the following cmdlet to change to the desired port. (2525 in this case)
Set-SendConnector “SMTP Send Connector Name goes here” -Port 2525
Whoa. Wait. Did I just say Windows Azure Linux VM? Yes. I sure did. Microsoft recently announced the General Availability of the Windows Azure Linux Virtual Machines. We’ve been looking for a good hosting solution, so I thought this would be a good time to do some experimentation on the Microsoft Azure Cloud.
I fired up a OpenLogic Centos 6.3 Virtual Machine. The process to get the machine running was amazingly quick and in just a couple minutes I was logged in via SSH. My next step was to install cPanel & WHM. The install script would start, run for a couple minutes, and then give a few “No package kernel-headers available.” Finally it would abort with the following fatal error. (FATAL): yum failed 6 times. Cannot continue! Removing /root/installer.lock
Fortunately there is a simple fix. Simply install the kernel-headers by running the following command. sudo yum –disableexcludes=main install kernel-headers-2.6.32-279.14.1.el6.openlogic.x86_64
Restart the cPanel installation script and it should install successfully now.