Outlook 2016 - Startet nicht - Fehler beim Anmelden

Fehlermeldung

Beim Start von Outlook erscheint die Meldung:

Fehler beim Anmelden. Überprüfen Sie die Netzwerkverbindung sowie den Server- Postfachnamen. Der Microsoft Exchange- Informationsdienst Ihres Profil enthält nicht alle erforderlichen Informationen. Überprüfen Sie ihr Profil.




Oder in Englisch:
Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The Mailbox Exchange information server in your profile is missing required information. Modify your profile to ensure that you are using the correct Microsoft Exchange information service.

Lösung 

XML Dateien im Benutzerordner C:\Users\%username%\AppData\Local\Microsoft\Outlook\16
verursachten in meinem Fall das Problem.

Ordner von Hand oder mit Befehl löschen:
rd C:\Users\%username%\AppData\Local\Microsoft\Outlook\16 /q /s



Danach sollte Outlook wieder korrekt starten. Der gelöschte Ordner sowie XML Dateien mit korrektem Inhalt werden automatisch wieder erstellt.

Activate Windows 10 Enterprise 2016 LTSB with KMS

Problem

Can't activate Win 10 Ent LTSB 2016 on Win2012R2 KMS server

Solution

We had to add the Windows Server 2016 KMS Host Key to the Win Server2012R2 KMS Server.
Make sure KB3172614 and KB3058168.


Grab the Windows Server 2016 KMS Host Key from VLSC.
Next add the key to the Win2012R2 KMS Server, and activate

run:
slmgr -ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX (Win2016KMS Host Key)


Activate
slmgr -ato


Then verify to see if the Win2016KMS Host Key is installed and activated.
slmgr -dlv


After this I was able to activate Windows 10 Ent LTSB 2016
Hopefully this will work for you.



Source: https://social.technet.microsoft.com/Forums/en-US/6b05ee31-e6b5-4658-86d1-3015d4ecf79e/mastering-windows-10-enterprise-2016-ltsb-workgroup-kms-activation-issue?forum=win10itprosetup

HP ProLiant Gen9 - Installation VMware ESXi on internal SD Card

I try to install a HP Custom ESXi Image (ESXi 5.1 U2) on a HP ProLiant Gen 9 Server (BIOS Version 1.5).
The Server has no Disk only a internal SD Card.


First i try to install ESXi over the HP Intelligent Provisioning Tool. But no luck. I get this error:

A runtime error occured
TypeError: PCIDevice is undefined
controllerinfo.js: 174

OK, next try is an installation from a usb stick (created with Rufus).

The installation starts, but hangs on "Relocating modules and starting up the kernel"

Solution to get this thing running:

• Press Shift+O during startup of an ESXi 5.1 installation.
• Append the boot option
• ignoreHeadless=TRUE
• Press the Enter key to continue boot.

In the end, the ESXi Installer run, but only start the ESXi Server from the USB Stick. That was not the idea. I want install ESXi on the internal SD Card.

OK, next try (and finally working solution) is to install ESXi over iLO.

This requieres a iLO license!

• Connect to iLO
• Install iLO license (if not already done)
• Start the iLO Remote Console
• Add Virtual Drives > Image File > [Your ESXi ISO File]
• Start Server
• Press F11 for Boot Menu and select CD-ROM to boot from the virtual drive

Now the ESXi Intaller startup and its now possible to select the SD Card as Install Target.

Conclusion

The installation not work, if a usb stick is plugged in. So, I think there must be a bug with the BIOS or something.

I tried with an other ESXi Image (6.0) and an other USB Stick and  changed BIOS in legacy mode and disabled USB 3.0 Mode. But all this helps not to get a working installation from an usb stick.

At the moment the only solution is to use iLO for the installation.

Maybe there comes a BIOS Update and fix that...

Visual Studio 2015 Update 1 crash on install

Microsoft has released the Visual Studio Update 1
Source:

On my test machine I get the following error when I tried to start the Setup (on Windows Server 2008 R2):

Microsoft Visual Studio Community 2015 has stopped working

Problem Details

Description:

  Stopped working

Problem signature:

  Problem Event Name:                        CLR20r3

  Problem Signature 01:                       vs_community.exe

  Problem Signature 02:                       14.0.23107.156

  Problem Signature 03:                       55414f16

  Problem Signature 04:                       PresentationCore

  Problem Signature 05:                       3.0.0.0

  Problem Signature 06:                       4ef6cf9b

  Problem Signature 07:                       1f

  Problem Signature 08:                       28

  Problem Signature 09:                       Exception

  OS Version:                                          6.1.7601.2.1.0.274.10

  Locale ID:                                             2055

Solution

I need to install the .NET Framework 3.5. This seems to be a prerequisite for the setup.

OK, lets go to Servermanager and install the feature .NET Framework 3.5.1:

Features Wizard: Install .NET Framework 3.5.1

After Installation the setup for Visual Studio 2015 Update 1 works :)

MSSQL Snippet: Grösste SQL Tabelle finden

Das folgende SQL Skript zeigt die grössten Tabellen nach MB oder Rows

SELECT 
    t.NAME AS TableName,
    i.name as indexName,
    sum(p.rows) as RowCounts,
    sum(a.total_pages) as TotalPages, 
    sum(a.used_pages) as UsedPages, 
    sum(a.data_pages) as DataPages,
    (sum(a.total_pages) * 8) / 1024 as TotalSpaceMB, 
    (sum(a.used_pages) * 8) / 1024 as UsedSpaceMB, 
    (sum(a.data_pages) * 8) / 1024 as DataSpaceMB
FROM 
    sys.tables t
INNER JOIN      
    sys.indexes i ON t.OBJECT_ID = i.object_id
INNER JOIN 
    sys.partitions p ON i.object_id = p.OBJECT_ID AND i.index_id = p.index_id
INNER JOIN 
    sys.allocation_units a ON p.partition_id = a.container_id
WHERE 
    t.NAME NOT LIKE 'dt%' AND
    i.OBJECT_ID > 255 AND   
    i.index_id <= 1
GROUP BY 
    t.NAME, i.object_id, i.index_id, i.name 
ORDER BY 
    object_name(i.object_id)

Sortiert nach Anzahl Rows:

ORDER BY RowCounts DESC

Sortiert nach Speicherplatz:

ORDER BY TotalSpaceMB DESC

Quelle:
http://stackoverflow.com/questions/2094436/how-to-find-largest-objects-in-a-sql-server-database

SQL Error: Object reference not set to an instance of an object

Problem

Beim Ausführen eines Maintenance Plans kommt es zur folgenden Fehlermeldung:














TITLE: Execute Maintenance Plan
------------------------------
Execution failed. See the maintenance plan and SQL Server Agent job history logs for details.
------------------------------

ADDITIONAL INFORMATION:
Object reference not set to an instance of an object. (Microsoft.SqlServer.SqlEnum)

Mögliche Lösung

Im Namen des Maintenance Plans wurde ein Sonderzeichen verwendet.

In meinem Fall "Backup & Wartung". Nach dem Entfernen des Und-Zeichen (&) funktionierte das Ausführen des Maintenance Plans korrekt.
Es empfiehlt sich also auf Sonderzeichen zu verzichten.