locked
Self-Service Portal keeps going into Maintenance Mode RRS feed

  • Question

  • Hi,

    I had installed Self-Service Portal and successfully created and approved a infrastructure request. The next step is to create a Virtual Machine. But I keep receving the error  of "self-service portal in maintenance mode and cannot process jobs at this time"  when the Operation Mode field of the global setting is in "Normal Mode".

    Anyone can help in this issue?

    thanks

     

     

    Tuesday, January 25, 2011 9:29 AM

Answers

  • Hi Kerry,

     

    Did you change credential for service account? If yes then

    ·         Please execute below 2 commands on Service machine’s powershell command prompt

    UpdateServiceAccount.exe -M Service -U <Service account domain>\<Service account user name> -P password

    UpdateServiceAccount.exe -M  Web -U <Service account domain>\<Service account user name> -P password

     

    ·         Restart VMMSSP Service on engine machine

    ·         IISreset

     

    If no then could you please check below things:-

    1.   Try renewing of certificate on MSMQ.  (Steps: Go to Service machine -> features ->Message queuing -> Right click properties -> Certificate -> click on renew certificates -> once done restart the service)

     

    2.  If you are facing issue in getting certificate then please check messaging queue installation mode (domain/Workgroup). If it is installed in workgroup mode then please do below steps to install MSMQ in domain mode.

     

    Details: This step will remove Engine machine from domain and add back to domain. Please check if it is possible in your case.

    Step 1: Remove all message queuing features

    Step 2.   Run from command prompt 

                       Netdom remove /d: MyDomain ComputerName /ud: MyDomain\Username /pd: Password

     Step 3. Join domain, again:

        1. Click Start, point to Settings, and then click Control Panel.
       2. Open System in Control Panel.
       3. Under Computer name, domain, and workgroup settings click Change settings.
       4. On the Computer Name page, click Change.
       5. Under Member of, click Domain, type the domain name, and then click OK.
       6. When prompted, provide a valid user name and password.
       7. When prompted, restart your computer to apply the changes.

     Step 4. Install messaging feature & directory integration together 

     

    Now try creating vm.  Let me know if it resolves your issue.

    Thanks,

     

    • Edited by Yogesh C Tuesday, March 8, 2011 6:20 PM Wrong command
    • Marked as answer by Yogesh C Thursday, April 7, 2011 5:35 PM
    Tuesday, March 8, 2011 6:01 PM

All replies

  • It looks like you are facing MSMQ issue. Did you changed service account credential recently?

    What Error do you see in Service log file ? You can locate service log file in Service machine's <Install Location>/Program file/Microsoft system Center Virtual machine manager Self Service portal 2.0\Service\

    Thanks,

    Wednesday, January 26, 2011 12:25 AM
  • Hi Yogesh,

    Below is the error entry in the Service log. As you had suspected it is something related to MSMQ. Any suggestion to fix this problem?

    Big thank you

    Best Regards

    Timestamp: 1/26/2011 8:30:39 AM
    Message:
    Error Details
    -------------------------------
    1/26/2011:4:30 PM

    Source: JobManager
    Error Code: 1323
    Message: Error queuing job 109f904e-8727-4cb6-8a47-99416e1078c4 of type CreateVM to MSMQ.


    Error Stack
    ------------------------
    1) User's internal Message Queuing certificate does not exist.

    Stack Trace
    ------------------------
       at System.Environment.get_StackTrace()
       at Microsoft.DDTK.Common.DDTKException.BuildErrorStack()
       at Microsoft.DDTK.Common.DDTKException.FormatException()
       at Microsoft.DDTK.Common.DDTKLogger.LogException(DDTKException ddtkException, TraceEventType eventType)
       at Microsoft.DDTK.Common.DDTKException.LogException(Exception exception)
       at Microsoft.DDTK.ProvisioningService.DDTKService.ProcessJob(Guid jobId)
       at SyncInvokeProcessJob(Object , Object[] , Object[] )
       at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
       at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
       at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
       at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage4(MessageRpc& rpc)
       at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)
       at System.ServiceModel.Dispatcher.ChannelHandler.DispatchAndReleasePump(RequestContext request, Boolean cleanThread, OperationContext currentOperationContext)
       at System.ServiceModel.Dispatcher.ChannelHandler.HandleRequest(RequestContext request, OperationContext currentOperationContext)
       at System.ServiceModel.Dispatcher.ChannelHandler.AsyncMessagePump(IAsyncResult result)
       at System.ServiceModel.Diagnostics.Utility.AsyncThunk.UnhandledExceptionFrame(IAsyncResult result)
       at System.ServiceModel.AsyncResult.Complete(Boolean completedSynchronously)
       at System.ServiceModel.Channels.FramingDuplexSessionChannel.TryReceiveAsyncResult.OnReceive(IAsyncResult result)
       at System.ServiceModel.Diagnostics.Utility.AsyncThunk.UnhandledExceptionFrame(IAsyncResult result)
       at System.ServiceModel.AsyncResult.Complete(Boolean completedSynchronously)
       at System.ServiceModel.Channels.SynchronizedMessageSource.SynchronizedAsyncResult`1.CompleteWithUnlock(Boolean synchronous, Exception exception)
       at System.ServiceModel.Channels.SynchronizedMessageSource.ReceiveAsyncResult.OnReceiveComplete(Object state)
       at System.ServiceModel.Channels.SessionConnectionReader.OnAsyncReadComplete(Object state)
       at System.ServiceModel.Channels.StreamConnection.OnRead(IAsyncResult result)
       at System.ServiceModel.Diagnostics.Utility.AsyncThunk.UnhandledExceptionFrame(IAsyncResult result)
       at System.Net.LazyAsyncResult.Complete(IntPtr userToken)
       at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr userToken)
       at System.Net.Security.NegotiateStream.ProcessFrameBody(Int32 readBytes, Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.NegotiateStream.ReadCallback(AsyncProtocolRequest asyncRequest)
       at System.Net.FixedSizeReader.CheckCompletionBeforeNextRead(Int32 bytes)
       at System.Net.FixedSizeReader.ReadCallback(IAsyncResult transportResult)
       at System.ServiceModel.AsyncResult.Complete(Boolean completedSynchronously)
       at System.ServiceModel.Channels.ConnectionStream.ReadAsyncResult.OnAsyncReadComplete(Object state)
       at System.ServiceModel.Channels.SocketConnection.FinishRead()
       at System.ServiceModel.Channels.SocketConnection.AsyncReadCallback(Boolean haveResult, Int32 error, Int32 bytesRead)
       at System.ServiceModel.Diagnostics.Utility.IOCompletionThunk.UnhandledExceptionFrame(UInt32 error, UInt32 bytesRead, NativeOverlapped* nativeOverlapped)
       at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)


    Category: Service
    Priority: 1
    EventId: 1323
    Severity: Error
    Title:Error queuing job 109f904e-8727-4cb6-8a47-99416e1078c4 of type CreateVM to MSMQ.
    Machine: ACCO2008
    Application Domain: Microsoft.DITSC.ProvisioningService.exe
    Process Id: 5420
    Process Name: C:\Program Files\Microsoft System Center Virtual Machine Manager Self Service Portal 2.0\Service\Microsoft.DITSC.ProvisioningService.exe
    Win32 Thread Id: 2624

    Wednesday, January 26, 2011 3:10 AM
  • To get certificate – Could you please log off from engine machine and log in back with Service account credential?  Once done, please restart Virtual machine manager self-service portal 2.0 Service.

     

    Now try creating VM,

    Thanks,

    Thursday, January 27, 2011 12:38 AM
  • I've run into the same issue.  Logging in as the service account and restarting VMMSSP service did not help.  Loggin in as the service account and rebooting does not help either.

    Update: re-installed with a "normal user" account for everything and it works.  We must be restricting our service accounts somehow.

    Wednesday, March 2, 2011 10:35 PM
  • Hi Kerry,

     

    Did you change credential for service account? If yes then

    ·         Please execute below 2 commands on Service machine’s powershell command prompt

    UpdateServiceAccount.exe -M Service -U <Service account domain>\<Service account user name> -P password

    UpdateServiceAccount.exe -M  Web -U <Service account domain>\<Service account user name> -P password

     

    ·         Restart VMMSSP Service on engine machine

    ·         IISreset

     

    If no then could you please check below things:-

    1.   Try renewing of certificate on MSMQ.  (Steps: Go to Service machine -> features ->Message queuing -> Right click properties -> Certificate -> click on renew certificates -> once done restart the service)

     

    2.  If you are facing issue in getting certificate then please check messaging queue installation mode (domain/Workgroup). If it is installed in workgroup mode then please do below steps to install MSMQ in domain mode.

     

    Details: This step will remove Engine machine from domain and add back to domain. Please check if it is possible in your case.

    Step 1: Remove all message queuing features

    Step 2.   Run from command prompt 

                       Netdom remove /d: MyDomain ComputerName /ud: MyDomain\Username /pd: Password

     Step 3. Join domain, again:

        1. Click Start, point to Settings, and then click Control Panel.
       2. Open System in Control Panel.
       3. Under Computer name, domain, and workgroup settings click Change settings.
       4. On the Computer Name page, click Change.
       5. Under Member of, click Domain, type the domain name, and then click OK.
       6. When prompted, provide a valid user name and password.
       7. When prompted, restart your computer to apply the changes.

     Step 4. Install messaging feature & directory integration together 

     

    Now try creating vm.  Let me know if it resolves your issue.

    Thanks,

     

    • Edited by Yogesh C Tuesday, March 8, 2011 6:20 PM Wrong command
    • Marked as answer by Yogesh C Thursday, April 7, 2011 5:35 PM
    Tuesday, March 8, 2011 6:01 PM