Archive for month: April, 2012

You are here: / / / April

SOLVED System Center Unified Installer with SQL Server 2008 R2

Unified InstallerMicrosoft Unified Installer

The installer instructions completely ignore the fact that you can’t just download SP1 and CU4 and put them in folders.

You will get “Invalid Location”.

Unified Installer Solution:

To fix this, you must decompress the download file. It is a .exe file.

It is self-extracting.

But you still aren’t done. The decompressed download file will create another .exe.

If you try to run this one, it will start to install SP1 / CU4. DO NOT LET IT INSTALL.

Try renaming this to setup.exe.

This will fix the Invalid File Location and replaced it with File Version Invalid Needs: 10.50.2900 Actual: 10.51.2900)

It was completely misleading.

Use a tool like 7-zip to extract the .exe file. This will put a setup.exe file in the folder. THIS file is the one that Unified Installer looks for.

Stop cursing and move on.

See our System Center Page for more information!

For additional help, visit Microsoft’s Unified Installer support page by clicking the link below:

https://enterprise.microsoft.com/en-us/trends/microsoft-unified-support-solutions/

/by

SOLVED Windows 2008 R2 Remote App black screen – never loading

R2 Remote AppWindows R2 Remote App

 

For the longest time I’ve been battling an issue with a client where one of the users had issues with a R2 remote app. Multiple people used the remote app but only one user had an issue. She complained that it took over 20 minutes for the remote app to load when she clicked the .rdp shortcut on her desktop. It would open a new window that was a black screen and take forever to load up the app.

I tried updating the remote app server, remaking her shortcut, and even trying the connection from a different network, all to no avail.

R2 Remote App Solution:

I finally stumbled on a kb article that contained a hotfix for a problem similar to mine. I installed the hotfix on the server and it finally fixed her problem.

The issue started after her remote app locked up. She closed it and immediately opened a new session by clicking the .rdp shortcut. It locked up again and she repeated this process multiple times. From this point on, she always experienced the black screen with long load times. The kb article states that this process can cause the issue but at random. The issue is more likely to occur with slow connections, especially WAN based connections.

Here is KB 981156

 

Thanks for reading and see how our Network Support team can help you!

/1 Comment/by
,

SOLVED: Removing Failed File from Failover Clustering

Failover ClusteringFailover Clustering

If you use Windows Failover Clustering and use a File Share Witness as your quorum configuration, you might have a situation in which you have removed your server that had contained the file share without first removing it from the cluster. EDIT:  If you haven’t destroyed your File Share, just bring it back online.  In this case you find out two things: your cluster has lost its failover protection, and  you can’t easily remove the failed file share witness (FSW).  EDIT:  You don’t lose failover protection, but you may have problems if you need to restart the cluster.  See the comments below and the Microsoft link to Quorum Configurations.

When you add a new file share witness using the Quorum Configuration Wizard, the new FSW is visible.  However, it is not active and your cluster will still fail if one node is turned off. The graphical interface has no way to delete the failed file share witness.  Further, the “recommended” method of removing it (using the cluster.exe resource /delete command) does not work.  This happens because the Failover Cluster will say that the resource cannot be deleted because it is a “core resource”.

Failover Clustering Solution

Run the Quorum Configuration Wizard and temporarily change the mode from Node and File Share Majority to Node Majority. There is no danger in doing this. It will not affect your running cluster, and it only takes a few seconds. After you make the change, you will see that the failed File Share Witness is gone from the cluster. Make sure you already have a new File Share to use, and then run the Quorum Configuration Wizard again and choose Node and File Share Majority, selecting a new file share as the witness.

See our Microsoft Failover Cluster and Hyper-V pages for more information!

For additional help, contact Microsoft Support by clicking the link below:

https://support.microsoft.com/en-us

/1 Comment/by
Meet our Team Get a Quote Read Reviews

CONTACT US

  • Call: 314-343-1800
  • Contact

    Use red “Contact Us” button (right)

  • Chat

    Use red “We are online” button (bottom)

BUSINESS HOURS

Monday – Friday: 8am – 5pm
Saturday – Sunday: Closed
24 Hour Support Service Available

Customers Receiving Support:

Disclaimer: Acumen Consulting is an independent service provider of technical service for business networks. We have reseller partner agreements with all of the companies and brands for which we are offering service on acumenitsupport.com. All partner trademarks, registers trademarks, company names, product names, and brand names, are the property of their respective owners. We provide ONLY reseller services for the products listed.

Call Now