Symptom:

When you open a Remote Desktop connection from a client to Windows Server 2012, you receive an “Internal error occurred” error message.

The connection setup is neither possible via IP address nor via the DNS name of the server.
The connection is interrupted before authentication.

The connection to the server can either not be established by a single client or not by a group of clients.

Assumption/Background:

• The Remote Desktop Session Service (Termservice.exe) is in a non-regular state.
• The Remote Desktop Session Port is used by another program.
• A self-signed RDP certificate is corrupt.
• A self-signed RDP certificate is not provided by the server during connection establishment.

Workaround:

Restart the service for the terminal service if there is still access to the server.

If there is no more access to the server, restart the entire server or the VM.

Links:

https://docs.microsoft.com/de-de/azure/virtual-machines/troubleshooting/troubleshoot-rdp-internal-error

 
Now something to laugh at for the admin…

Keine Produkte gefunden.

Keine Produkte gefunden.

Keine Produkte gefunden.

All the links in this text are Amazon Affiliate Links, and by clicking on an affiliate link I will earn a percentage of your subsequent Amazon purchases. However, this circumstance does not influence the background of my product recommendation. This product recommendation is independent, honest and sincere. 

Bei allen genannten Links handelt es sich um Amazon-Affiliate-Links. Durch einen Klick auf einen Affiliate-Link werde ich prozentual an Euren darauf folgenden Amazon-Einkäufen beteiligt. Dieser Umstand beeinflusst aber nicht die Hintergründe meiner Produktempfehlung. Diese Produktempfehlung erfolgt unabhängig, ehrlich und aufrichtig.

Der Beitrag Workaround: Error message “An internal error has occurred” on RDP Remote Desktop Connection erschien zuerst auf Pixelfriedhof.

You are trying to save, export or bounce an Apple Logic project, but you encounter an error which results in a crashing Logic-App.

I worked out that this error occurs, when the app is trying to get file-system access in a file-browser-window.

To solve this problem simply keep logic closed, go to system settings and deactivate iCloud Drive under iCloud settings.

Now restart Logic and you are ready to save your project.

Der Beitrag Solution: Apple Logic crashing when trying to save, export or bounce a project erschien zuerst auf Pixelfriedhof.

If you try uploading a large source of files to a cloud backupstorage via “Hyper Backup” you might encounter a problem where your backup gets stuck immediately after a connection loss. Especially when creating the initial backup-set, which uploads all files that are available at the source, the job might need a few days to complete. It is very likely, that during this long time there will be a connection-loss or a connection-reset by your ISP which will freeze the procedure. So you might think: “I’ll never get my data into the cloud”.

Don’t give up, there is a workaround. 

To understand the workaround you first have to understand how “Hyper Backup” works. After the initial backup-set (the first time you upload the source-files to the backup-destination), in future backup-tasks “Hyper Backup” only updates or adds altered or new data, which means, that the following backups are far smaller as they only contain everything that is not already at the destination. Depending on how your backup-task is configured and scheduled, we might speek of incremental and differential backups.

This behaviour is the key to our workaround. Most people suffering from this problem, will not have this problem with the everyday-backup-tasks, but with the first initial backup, as it is much larger as I explained above. So we need to only workaround the initial backup-task.

In my case, my destination for the backups is the cloudstorage-provider “hubiC” but this should be similar when using other providers.

My backup-source is for example 250GB large, which is not uploadable within one day because of compression-time and encryption-time. My ISP resets the Internetconnection at 1pm and the backup gets stuck.

Let’s say that my backup-source, my share to backup, consists of 25 folders. If I try to upload every 25 folders at once it will fail, so we go to configure our backup-task to initially only backup folders 1 to 3.

We start the backup-task and folders 1 to 3 are successfully uploaded in less than a day.

Now we reconfigure the backup-task, adding folders 4 to 6 and start the backup again (meaning we have now activated folders 1, 2, 3, 4, 5, and 6 to be uploaded).

As I mentioned above, only new or altered files, in this case folders 4 to 6 will be uploaded. This procedure will also finish within one day.

Repeating this until folder 25, this workaround allows us to partially upload our whole source. When every folder was uploaded, we go to our backup-settings once again and activate the whole share at the higher root level.

Der Beitrag Synology Hyper Backup: Finish large backups despite connection loss erschien zuerst auf Pixelfriedhof.