UserProfile Sync problem:Could not connect to http://(server):5725/ResourceManagementService/MEX

Problem: You are trying to sync user profiles from active Directory and get an error:

Could not connect to :5725/ResourceManagementService/MEX. TCP error code 10061: No connection could be made because the target machine actively refused it


Solution: Verify that windows service "Forefront Identity Manager Service" and "Forefront Identity Manager Synchronization Service" are started. If not, please start them and then check the effect.

Office 2013 breaks your SharePoint 2010

Problem:
After installing Office 2013 on your SharePoint 2010 box you experience the following, when trying to upload an InfoPath form:

There are some policy files that reference the wrong assemblies. The following post got me to the right solution: http://smindreau.wordpress.com/2012/12/04/office-preview-2013-breaks-your-sharepoint-2010-enterprise-notably-infopath/

Solution:
Basically you must:
1. Entering the path C:\Windows\Assembly\GAC_MSIL in the Start/Run
2. Delete the following three folders:
 Policy.14.0.Microsoft.Office.InfoPath
 Policy.14.0.Microsoft.Office.InfoPath.Client.Internal.Host
 Policy.14.0.Microsoft.Office.InfoPath.FormControl
3. Run an IISRESET from a command prompt.

Can't connect to my Windows Azure VM!

Problem: Tried to RDP one of my VM’s and I can’t connect. Possible firewall port issue?

Explanation:  It’s important to remember that the port that you’re using for RDP is not the traditional 3389.
“It’s not? How does that work?”
Let’s step back for a second and consider what you see when you first create a virtual machine in Windows Azure and you get to the screen where “endpoints” are defined. By default, it looks something like this…

…Notice that, even though the operating system is going to have Remote Desktop enabled and will be listening on the traditional port 3389, the external “public port” value that will be redirected to the “private port” 3389 is going to be something different.
“Why?”
Security. We take the extra precaution of randomizing this port so that tools that are scanning for open 3389 ports out there won’t find those machines and then start attempting to log in.
---
Let’s go one step further here and propose a couple of solutions to this, in case you also run into this problem.
Solution #1: Open up the proper outbound firewall ports
In the properties of your virtual machine, you can find what “public port” was assigned to the VM under the endpoints tab…

So this web server of mine is answering to my RDP requests via my ability to connect to it’s service URL and port 56537. Since I am not restricting outbound ports, this isn’t a problem for me. But knowing what this port is can help you understand what needs to be opened for a particular machine.
“Is there a range of ports that I need to have open outbound?”
The port that will be assigned automatically is going to come from the “ephemeral port range” for dynamic or private ports (as defined by the Internet Assigned Numbers Authority) of 49152 to 65535. So if you simply enable outbound connections through that range, the defaults should work well for you.
Solution #2: Modify the VM End Points
You’ll note on the above picture that there is an “edit” option. You have the ability to edit and assign whatever port you want for the public port value. For example, I could do this…

…and just use port 3389 directly. Of course, this would defeat the purpose for using a random, non-standard port for remote desktop connections. But it could be done.
Solution #3: Use some other remote desktop-esque tool over some other port.
The server you’re running as a VM in Windows Azure is your machine, so there’s no reason you couldn’t install some other tool of choice for doing management or connecting to a remote desktop type of connection. Understand the application, what port needs to be enabled on the firewall of the server, and then add that port as an endpoint; either directly mapped with the same public/private port or using some other public port. It is entirely configurable and flexible. And as long as you’ve enabled the public port value as a port you’re allowing outbound from your workplace, you’re golden.
Solution #4: Use a Remote Desktop Gateway
How about instead of connecting to machines directly, you do something more secured, manageable, and along the same lines of what you would consider for allowing secured access into your own datacenter remote desktop session hosts: Configure one server as the gateway for access to the others. In this way you have the added benefits of just one open port; and that port is SSL (443). You’re very likely already allowing out port 443 for anyone doing secured browsing (HTTPS://…), so the firewall won’t get in the way.

The media family on device '' is incorrectly formed. SQL Server cannot process this media family

If you get this messge, usually you are trying to restore a backup file from a newer version of SQL Server to an older version. (i.e. SQL Server 2012 => SQL Server 2008 R2)

If backup is correct and one is trying to restore on lower version
Error: The media family on device 'C:\test.bak' is incorrectly formed. SQL Server cannot process this media family
If backup is corrupt and either you try to restore on same or lower version
Error: The file on device 'C:\test.bak' is not a valid Microsoft Tape Format backup set.

Solution: SQL server doesn’t support restore from higher to lower version. There is no "downgrade" possible using backup/restore or detach/attach. You'd have to use the Import/Export wizards (scripts) to migrate everything.

COMException: Die NumberFormat-Eigenschaft des Range-Objektes kann nicht Festgelegt werden

The error in english is:
Unable to set the NumberFormat property of the Range Class

Solution:
In Excel you have two Fields:

• NumberFormat
• NumberFormatLocal

NumberFormat takes the format always locale invariant in the american standard and NumberFormatLocal expects the format with the locale formatting string.

Out of memory exception when setting an excel chart name

xlChart.Name = "A name";

This property is read-only for chart objects (embedded charts).

Solution:
The charts are "floating" on the page (not sepearate chart sheets), so the "read-only" remark applies and explains why you're getting an error. A seperate "chart only sheet" can have a name via this property.

Hyper-V virtual machine failed to start after copying VHD

On Windows 8 running Hyper-V, I copied a VHD from an external drive using Windows Explorer to the local machine. I reconfigured the new location in Hyper-V and tried to start the machine. I got the following error message:

‘VM’ failed to start.
Microsoft Emulated IDE Controller (Instance ID {…}): failed to Power on with Error ‘General access denied error’ (0×80070005). [Event ID 12010]
IDE/ATAPI Account does not have sufficient privilege to open attachment ‘D:\Virtual Machines\VM01\Virtual Hard Disks\DRIVE.VHD’. Error: ‘General access denied error’ (0×80070005). [Event ID 12290]
‘VM failed to start. (Virtual machine ID 6B78D45F5-71DF-4725-B4B2-E651800BE80EF) [Event ID 12030]

This issue occurs if the permissions on the virtual hard disk (.vhd) file or the snapshot file (.avhd) are incorrect.
Every Hyper-V virtual machines has a unique Virtual Machine ID (SID). If the Virtual Machine SID is missing from the security permissions on the .vhd or .avhd file, the virtual machine does not start.

Solution:
Give the Virtual Machine ID (SID) access to the .vhd or .avhd file, type the following command, and then press Enter:

icacls [Path of .vhd or .avhd file] /grant "NT VIRTUAL MACHINE\[Virtual Machine ID from step 1]":(F)

Ressource: http://support.microsoft.com/kb/2249906/en-us