Vsphere Content Library: RuntimeFault.Summary cannot delete content library item


When trying to delete an image from content library and you receive an error of:

“RunTimeFault.Summary”

“Cannot Delete File [Datastore] /PathtoContentLibraryVMDK”

Solution I found:

  1. Log into VCenter Server
  2. Select Content Library
  3. Right click content library item
  4. Rename item
  5. Delete item

I was trying to update some images i had on my home lab and i ran into the issue and issue when trying to delete some old templates from the library. I tried multiple times to delete the template i had stored only to receive the same error.

I investigated and found that the path from the error had no VMDK in it from the content library. That being said I had two options. Delete the folder in the datastore, which could corrupt the content library or rename the library item and try to delete again.

So when I renamed the content library item and deleted the item and it worked like a charm. I could not find a KB article for this particular issue or at least one that was relevant to content library but this worked for me.

 

EMC SourceOne – Exchange 2016 “system call failed”

“System call failed.  Unknown error”

“CoExExchProvider::LogonDS: Cannot log into mailbox”

If after you migrated the SourceOne service account and journal mailbox to Exchange 2016, and your jobs keep failing you may have a similar issue to me.

During the process of migrating the last two mailboxes (Both SourceOne) to the new environment I was getting permission errors throw in the logs while attempting to run the journaling jobs. This was because SourceOne DOES NOT SUPPORT HTTPS. 

In order to get SourceOne working properly on exchange 2016 if you are forcing HTTPS you need to enable RPC over http using the KB articles below.


Each step must be done on each worker node after migration has completed:

  1. Log into worker node using SourceOne Service account
  2. Control Panel > Mail (32-Bit) > Delete old mail profile > Create new profile (Make sure to uncheck Cached exchange mode)
  3. Regedit.exe navigate to “HKEY_CURRENT_USER\Software\Microsoft\Exchange”
  4. Create new DWORD “MapiHttpDisabled”
  5. Set value to “1”
  6. Restart Outlook client

There is an KB from Microsoft that shows you how to remove this setting, so i did not add it because it may have been confusing. But the KB is 2937684.

 

EMC SourceOne 7.2 SP6- Cannot connect to journal mailbox in a mixed Microsoft Exchange scenario (2010 and 2016)

So this has bitten me for the past couple of weeks we would try to fail over our last two mailboxes from exchange 2010 to exchange 2016. One Journal and One Service account. Come to find out (No thanks to EMC SourceOne install documentation) That the service account needs to be the last mailbox to move.

Take a look at this bug report: https://community.emc.com/docs/DOC-60862

If you are going to run in a mixed environment for a long time follow the steps below in the article and always make sure you migrate your SourceOne Service account last!

With 2010/2016 co-existence, there are certain requirements for it to work.    
    
    These requirements are:-    
    
    1) Service Account mailbox needs to be always on the lower exchange version.It should be the last mailbox to move to 2016. Exchange 2010 should be configured with RPC over https.    
    2) Exchange 2016 should have RPC over https enabled. By default Exchange 2016 has MAPI over https which is not supported by SourceOne. Customer will have to enable RPC over https and configure it correctly    
    3) All ES1 servers should have only Outlook 2010 SP2 + KB2878254. No other HF or update. Updates for Outlook should be disabled.    
    4) Profile needs to be configured on Outlook to have Outlook using RPC over https with the proxy server pointing to the 2016 server. For these changes you will need to configure AutoDiscovery.    
    5) Set the correct permissions mailbox on 2016    
    
    Without these 5 criteria, they will not be able to communicate between 2 versions of exchange.       

VMworld 2018: The return of the cloud – Part 2

Vendors


The vendors at VMworld this year was what you would expect from one of the biggest conferences in tech. There was a lot of big vendors such as Dell/EMC, Lenovo, AWS, and IBM, but I really find interest in the small vendors. The up and coming technology that is the way of the future.

These are just three of the vendor’s i enjoyed seeing at VMworld 2018

Docker

You had some great vendors like Docker at the event. Containers are the way of the future and Docker is the leader in the industry. I really enjoyed chatting with them this year and I gained a lot of knowledge from the breakout sessions I went to where Docker was a topic (I don’t know if they lead those sessions or not), So much so that I really want to do a Docker for noobs video series where I video document my whole experience in learning Docker from zero to hero. But more about that later on.

@Docker                                                                                        https://docker.com

Men & mice

This is a super awesome group of icelandic men/women. They specialize in DNS/DHCP/IPAM in the cloud solutions, and while it is not a new problem people have faced (As it pertains to private cloud)  there is a lot that can be said about the people at the booth, they love what they do and they are passionate about the product. That is why I love this company and the booth. They know they are the best and they let the product do the talking for them. Really impressive company and even more impressive people.

@MenAndMice                                                                https://menandmice.com


 

Rubrik

This company has been killing it over the last three-year. Rubrik has been Dominating the backup space at what seems like hyper-speed. Although I have never used Rubrik as a backup solution from what people have said it’s an awesome intuitive product. They sell Rubrik based on future proofing your backup and anyone I have asked has not had any complaint with them. This year at VMworld Rubrik took home best of show. Which in my opinion is well deserved. The way Rubrik cares about the community of technologists and their work to be top of the line backup earns them that spot.

@RubrikInc                                                                              https://www.rubrik.com/

VMworld 2018: The return of the cloud – Part 1


So VMworld 2018 is a wrap and i had the awesome privilege to attend this year! I would like to say first thing, if you have never been to VMWorld the networking opportunities alone is worth the price of admission. The technology you will be seeing most of the time first hand is worth the flight and hotel fee’s.

This year was full of great keynotes and some awesome vendors both large and small. So lets dive into it.

 

Keynotes


The keynotes were the usual setup, just like last year they came out on stage after a dramatic opening to the first day of vmworld, and just like last year they went hard on the usual products AWS/NSX/VSAN.  Which I cannot blame them honestly its the way of the future, and will be the biggest money maker for VMware and its partners.

Day one and two were good keynotes with the usual technical announcements nothing major that we haven’t seen in the past, but some improvements on already existing technologies. With the exception of the 64Bit ARM platforms, which is awesome in my opinion. A lot of people have waited for this announcement and I got really good feedback from people i asked who had an interest in ESXi for the ARM platform.

Day three was interesting, with an hour long round table interview with the Sanjay Poonen with multiple C level exec’s from big non relevant companies, the external stream ended for people watching online and the interview that everyone was waited for began. For some reason VMware had the last keynote end with a hour long discussion with Malala, while the noble peace prize winner is admirable and a really fantastic human being i don’t see the point of having that discussion at a tech conference. Some people i talked to loved the interview, some not so much.I was in-between, i was impressed with her but didn’t really see the point. Some people took it at a jab of the technical community for being unfair to women in the field, and VMware highlighting that.

When you bring in someone like Malala it is impressive, but her message is so direct that it felt like VMware was trying to send a message to the tech world, whether purposely or it just happen to show like that some people took it that way.

 

Part 2 Coming up.

EMC ESRSve admin password reset (VXRail Edition)

Resetting a password on a ESRS appliance is pretty straight forward. But there is a pesky error that can pop up from time to time with ESRS appliances that get deployed via the VXRail deployment.

The normal esrs admin password reset goes something like this:


ESRSapplicance:~ # cd /opt/esrs/webuimgmt-util/
ESRSapplicance:~ # ./passwordAdmin.sh

Normally this would then ask you for a new password for the admin account associated with your ESRS appliance.

But what is the error you might ask? Well it happens in lieu of asking for a new password.

“User Configuration File Missing. Please contact ESRS Support”

In order to get around this error it is a simple command you must run before starting the ./passwordadmin.sh script:


ESRSapplicance:~ # echo admin > /etc/esrsadmin.conf
ESRSapplicance:~ # cd /opt/esrs/webuimgmt-util/
ESRSapplicance:~ # ./passwordAdmin.sh

And thats it! Have fun with ESRS and let me know it this article helped you!

A General system error occurred: Connection refused

Got this error today when trying to start up a VM.

A General system error occurred: Connection refused

 

While it was annoying to see, this issue is easily resolved. At least for me.

Log into your VCSA and first check the drive space

user@VCSA:$ df -h

Confirm the none of the drives are full

Then check the status and start the vmware-vpx-workflow service

user@VCSA:$ service-control --status vmware-vpx-workflow
user@VCSA:$ service-control --start vmware-vpx-workflow

It will take a second to start the service but that should do the trick!