Error upgrading to 6.1

[awjudge]

Hi,

I've successfully upgraded both the ID server the VCAC server and the IAAS DB.

Now, when I go to upgrade the IAAS components, I get:

Should all the IAAS server services be running, in order to do the upgrade? It doesn't say anything about that in the documentation...

TIA.

[kilzer]

Hi Guys,

I have exactly the same error. On my single IaaS Host (Windows Server 2008R2) are all Services installed like Web API Model Manager Web, Administration Web Site, Manager Service, Model Manager Data and the DEM Worker and the DEM Orchestrator.

In my Windows Event log i found two Errors:

Event ID 0 Source VMware Repository

Timestamp: 11.09.2014 08:42:49

Message: Failed to start repository service. Reason: One or more errors occurred.

Category: Error

Priority: -1

EventId: 0

Severity: Error

Title:

Machine: VCAC02

App Domain: /LM/W3SVC/1/ROOT/Repository-182-130548985670709942

ProcessId: 4936

Process Name: c:\windows\system32\inetsrv\w3wp.exe

Thread Name:

Win32 ThreadId:1040

Extended Properties:

And a Warning Event ID 1309: Source ASP.NET 4.0.30319.0

Event code: 3005

Event message: An unhandled exception has occurred.

Event time: 11.09.2014 10:48:28

Event time (UTC): 11.09.2014 08:48:28

Event ID: c6bf545e00ed48a3909ca6c2a38ac0a1

Event sequence: 2

Event occurrence: 1

Event detail code: 0

Application information:

    Application domain: /LM/W3SVC/1/ROOT/Repository-207-130548989060369942

    Trust level: Full

    Application Virtual Path: /Repository

    Application Path: C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Web\

    Machine name: VCAC02

Process information:

    Process ID: 4936

    Process name: w3wp.exe

    Account name: AD\svc-vmware

Exception information:

    Exception type: HttpException

    Exception message: One or more errors occurred.

   at System.Web.HttpApplicationFactory.EnsureAppStartCalledForIntegratedMode(HttpContext context, HttpApplication app)

   at System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers)

   at System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context)

   at System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context)

   at System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext)

One or more errors occurred.

   at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)

   at VMware.Cafe.GenericRestClient.PagedRequestEnumerator`1.MoveNext()

   at System.Linq.Enumerable.WhereEnumerableIterator`1.MoveNext()

   at System.Linq.Enumerable.<DistinctIterator>d__81`1.MoveNext()

   at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)

   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)

   at DynamicOps.Repository.Runtime.SecurityModel.CafeSecurityProvider.get_Scopes()

   at DynamicOps.Repository.Runtime.SecurityModel.CafeSecurityProvider.IsInitialized(String connectionString, String applicationName)

   at DynamicOps.Repository.Runtime.Common.RepositoryRuntime.Initialize()

Not Found (404)

   at VMware.Cafe.JsonRestClient.<HandleErrorResponse>d__88`1.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()

   at VMware.Cafe.JsonRestClient.<GetResource>d__7`1.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at VMware.Cafe.GenericRestClient.PagedRequestEnumerator`1.<InitializeAndGetFirstPage>d__3.MoveNext()

Request information:

    Request URL: https://XXX.XXX:443/repository/Data/TrackingModel.svc/$batch

    Request path: /repository/Data/TrackingModel.svc/$batch

    User host address: fe80::5e7:576d:7d02:e930Full

    User: 

    Is authenticated: False

    Authentication Type: 

    Thread account name: AD\svc- XXX

Thread information:

    Thread ID: 23

    Thread account name: AD\svc-XXX

    Is impersonating: False

    Stack trace:    at System.Web.HttpApplicationFactory.EnsureAppStartCalledForIntegratedMode(HttpContext context, HttpApplication app)

   at System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers)

   at System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context)

   at System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context)

   at System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext)

Custom event details:

Does anybody can help me out?

Kind Regards

Andreas

[awjudge]

I've just opened a SR with VMware, on the phone to them now. Will report back when I have more information...

[dphowes]

Hi Guys, did you get any resolution to this ?  Having the same problem here.

[awjudge]

Not yet, still on a dial in with VMware. 6 hours and counting. I'll post back once I know more.

[dphowes]

Wow, ouch.  Just raised a SR as well.  First to a solution wins

[awjudge]

Ok, so let's compare notes...

On your VCAC appliance under the Services tab, do you see both the IAAS-Service and Shell-UI-App service as FAILED?

[kilzer]

Positive.

[awjudge]

Allrighty. Looks like we're in the same boat then. A positive...

[SeanKohler]

Similar scenario here.

Site is available via vcac sitepath even though it says failed for shell-ui-app. (https://blahblah/vcac/org/ versus https://blahblah/shell-ui-app/org)

IAAS becomes registered after the upgrade, however we are receiving a 404 error on the Infrastructure tab in VCAC and haven't been able to get around it on subsequent attempts.

[awjudge]

The advice I have from VMware for the moment is to roll back to the pre-6.1 version. Thankfully I have snapshots and an IAAS DB backup. I think this is going to Engineering for further analysis.

[kilzer]

Thanks for the information. Than i will roll back, too. It would be nice to hear from you, when you got new information from VMware.

[dphowes]

My upgrade has gone along the same lines.  Rolled back with VMware last night and re-installed updates to appliances.  Still issues so logs being referred to Engineering.  Looks like the issue is not the IAAS but the appliance upgrades at the moment.

[dphowes]

Quick question, how did you guys do the update ?  I opted for the CD-ROM update method, is this the same for you guys or did you opt for different methods to apply the virtual appliance updates ?

[awjudge]

I did the online update from the appliances directly from the VMware repo.

[dphowes]

Hmm, ok, back to the drawing board for now then.

[awjudge]

I have word from VMware that they have managed to replicate the issue.

[HS_SYMC]

Same problem here... Please update if/when there is solution.

Thank you.

[dphowes]

That at least is positive.

Will chase my SR and see what they are saying.

[sbeaver]

I am having the same issue with shell-ui-app failed on fresh install.  Seems to have something to do with messaging also