Azure asp.net mvc 3 publishing/deployment issue - asp.net-mvc-3

Hi I have a MVC 3 web project which has been deployed to Azure successfully previously.
Since i had some problems with github,
and the Azure cloud project just won't publish, we have tried to delete/create new projects; updated varies settings, endpoints; include all of the dlls; tried to look for diagnostics.
even we tried to created a blank new projects and deployed it
so far nothing works
3:37:12 PM - Preparing deployment for Subscription with Subscription ID: 519e1c......
3:37:13 PM - Connecting...
3:37:14 PM - Verifying storage account 'blahblah'...
3:37:15 PM - Uploading Package...
3:37:45 PM - Creating...
3:39:53 PM - Created Deployment ID: 244f269afefe40fb99........
3:39:53 PM - Starting...
3:40:28 PM - Initializing...
3:40:28 PM - Instance 0 of role Web is in an unknown state
3:45:34 PM - Instance 0 of role Web is starting the virtual machine
3:46:42 PM - Instance 0 of role Web is in an unknown state
then busy, cycling.....

If you want to see what is going on, just activate Remote Desktop on the instance.
I found that between recycling of the instance there is enough time to run the web site and get the yellow screen of death telling you which dll you are missing.

Related

Upgrade from Business Central On-Premise V14.23 to V15.17 On-Premise

I'm attempting to upgrade our Business Central On-Premise installation from Version 14 to 15, using the procedure on the link below.
Installing a Business Central 2019 Release Wave 2 Update
I got to: 'Upgrade control add-ins' Step 1 (Open the Business Central client) This is the first time run after the upgrade. At this point we get: 'Something Went Wrong. An Error occurred.'
The Event Viewer reports:-
The metadata object Page 9006 was not found.
Message Fatal error during metadata load -- Type:Page; Id:0;MetadataGroup:0;MetadataLoaded:False; CLRLoaded:False; ThreadGroup:0
The metadata object Page 0 was not found.
Any thoughts?

MS Exchange 2019 Install Error - Active Directory Operation Failed on dc.domain - Directory Object Not Found

Completely new install of MS Exchange 2019, installed all the prerequisites for the Mailbox role successfully and schema created across the 4 domain controllers in the environment.
Had to manually create the schema on the root domain as the Exchange server was on the child domain, however schema replicated successfully across the domains in the environment.
During the installation on the Exchange server, the installation stages will always stop at stage 8/12 (Installation of Mailbox role). Checked the logs and it returns the following error messages:
***[ERROR] Active Directory operation failed on dc.domain. The error is not retriable. Additional information: Directory object not found.
Active Directory response: 0000208D: NameErr: DSID-03100288, problem 2001 (NO_OBJECT), data 0, best match of: 'DC= dc, Dc= dc, Dc= dc'
[ERROR] The object does not exist
[ERROR-REFERENCE] Id=MailboxServiceControlLast_05b3bbd421504e0c93fefa6d5d1ae590
Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
Setup is stopping now because of one or more critical errors
Finished executing components tasks
Ending process Install-MailboxRole***
P.S In the right security groups to execute the installation (Schema and Enterprise Admins).
Any help or advice will be highly appreciated!
Have you changed the Users Container CN=Users,DC=domain,DC=com or the Object in question from Type Container to an Organizational Unit? The setup expects some Objects as Container. Users is one of them.

Trying to convert existing WCF service to Web Role can't deploy without errors

I've converted existing WCF application to web role by adding it with "Add web role project in solution". Convert menu doesn't offer me option to convert. Our application requires .NET 4.6.1
Application runs fine on full emulator. However deployment fails with two scenarios:
osFamily attribute set to "5" in Serviceconfiguration(no .NET 4.6.1 installation script required):
19:15:16 - Instance 0 of role Severa.API is restarting
Details: [11/28T17:15Z]Failed to load role entrypoint. System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
at System.Reflection.RuntimeModule.GetTypes(RuntimeModule module)
at System.Reflection.Assembly.GetTypes()
at Microsoft.WindowsAzure.ServiceRuntime.RoleEnvironment.GetRoleEntryPoint(Assembly entryPointAssembly)
--- End of inner exception stack trace ---
at Microsoft.WindowsAzure.ServiceRuntime.RoleEnvironment.GetRoleEntryPoint(Assembly entryPointAssembly)
at Microsoft.WindowsAzure.ServiceRuntime.RoleEnvironment.CreateRoleEntryPoint(RoleType roleTypeEnum)
at Microsoft.WindowsAzure.ServiceRuntime.RoleEnvironment.InitializeRoleInternal(RoleType roleTypeEnum) Last exit time: [2016/11/28, 17:15:06.916]. Last exit code: 0.
osFamily attribute set to "4" in Serviceconfiguration with .NET 4.6.1 installation:
The feature named NetFx451 that is required by the uploaded package is not available in the OS * chosen for the deployment.
I've used the .NET installation script in other projects with success. Also I have added WebRole.CS class to the project.
Is the issue here that the webrole is not WCF type meaning some setting etc. is missing?
We've managed to identify and fix the issue.
I've enabled Fusion logging and immediately got the missing information.
What would have saved a lot of time and point us to right direction would have been to understand that web role in CS consists of two processes: WAIISHost which runs RoleEntryPoint code in startup and good old W3WP for the Web application itself.
WAIIShost can't read Web.config and requires an empty Web.config file named after name of the project and redeployed successfully. I followed instructions from this article:
Post about the issue

Process Engine Dispatcher exception while transferring the workflow

When a workflow is being transferred the PE error occurred. I am using custom components other than CE_Operations in workflow.
ERROR STACK:
[FATAL 09 Apr 2014 15:25:21] Dispatcher got exception while doing query at April 9, 2014 3:25:21 PM GMT+05:30. Cause=[FNRPE2131090092E]The work space time stamp is stale
The work space has been updated by transfer, so the client workstation needs to load new workspaces and a new time stamp.
at filenet.pe.peorb.client.ORBUtility.mapServerException(ORBUtility.java:529)
at filenet.pe.peorb.client.ORBSession.executeRPC(ORBSession.java:1266)
at filenet.pe.peorb.client.ORBSession.fetch(ORBSession.java:2112)
at filenet.vw.api.VWQuery.fetch(VWQuery.java:653)
at filenet.vw.api.VWQueueQuery.dofetch(VWQueueQuery.java:429)
at filenet.vw.api.VWQuery.hasNext(VWQuery.java:768)
at filenet.vw.api.VWQueueQuery.hasNext(VWQueueQuery.java:461)
at filenet.vw.integrator.base.VWAdaptorControlEx$WorkflowDispatcher.run(VWAdaptorControlEx.java:359)
Root Cause:
[FNRPE2131090092E]The work space time stamp is stale
The work space has been updated by transfer, so the client workstation needs to load new workspaces and a new time stamp.
at filenet.jpe.server.common.IVWRuntimeServer.checkTimeStamps(IVWRuntimeServer.java:4754)
at filenet.jpe.server.common.IVWRuntimeServer.InitSession(IVWRuntimeServer.java:4064)
at filenet.jpe.rpc.orb.OrbRPC.<init>(OrbRPC.java:696)
at filenet.jpe.rpc.orb.ORBPERPC.orb_rpc_fetchQuery(ORBPERPC.java:911)
at filenet.pe.peorb.FileNet_PERPC.PERPCPOA._invoke(PERPCPOA.java:697)
at com.ibm.CORBA.poa.POAServerDelegate.dispatchToServant(POAServerDelegate.java:402)
at com.ibm.CORBA.poa.POAServerDelegate.internalDispatch(POAServerDelegate.java:334)
at com.ibm.CORBA.poa.POAServerDelegate.dispatch(POAServerDelegate.java:256)
at com.ibm.rmi.iiop.ORB.process(ORB.java:518)
at com.ibm.CORBA.iiop.ORB.process(ORB.java:1574)
at com.ibm.rmi.iiop.Connection.respondTo(Connection.java:2880)
at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2753)
at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:63)
at com.ibm.rmi.iiop.WorkerThread.run(ThreadPoolImpl.java:202)
at java.lang.Thread.run(Thread.java:736)
How can I resolve this issue. Thanks!
Check the configuration of your connection point
to make sure it work :
run (install dir)FileNet\AE\Router\routercmd.bat
click on connection point, in the right panel under general tab clic on buton "display work queue"
-> this action try a connection from AE to PE, to retrieve names of your work queues.
if it work your connection point should be working
if not, see vwtaskman.log under (install dir)FileNet\AE\Router\ for more details

Error deploy BMP project using Tibco Business Studio

I try to deploy a BPM project but I get error when create application as such:
create.app:[AMXAdminTask] INFO - Processing 1 objects[AMXAdminTask]
INFO - Adding application...[AMXAdminTask] ERROR - Failed to add
Application 'com.example.bmpsample'[AMXAdminTask] ERROR - Follower
application component
urn:amx:BPMEnvironment/com.example.bmpsample/BMPSampleProcessFlow_1.0.0.201311211151
requires capability
com.tibco.amf.sca.model.componenttype.impl.RequiredCapabilityImpl#7396acb
(id: com.tibco.bx.capability.implementation.bx, version: 1.0.0, type:
factory) but the target application does not provide it.
BUILD
FAILEDD:\wsbmp.BSServers\scripts\com.example.bmpsample.deployment-build.xml:37:
Failed on error Total time: 7 seconds
I also got same error while deploying bpm project from studio, to resolve that below information will help you :
Summary When using TIBCO Business Studio to deploy a DAA that is
dependant on another DAA which is not in the deployed state results in errors
such as:
Follower application component
urn:amx:BPMEnvironment/com.example.appa/APPAProcessFlow requires
capability
com.tibco.amf.sca.model.componenttype.impl.RequiredCapabilityImp
l#7ee0f191 (id: com.tibco.bx.capability.implementation.bx,
version: 1.0.0, type: factory) but the target application does
not provide it.
Workaround Make sure the dependant DAA is deployed.
Thanks & Regards,
Srinivasa Reddy P

Resources