Installation Windows server 2012 R2 Domain
anderson last edited by
I am not able to perform installation on windows 2012 R2 domain
Installation is done however when I go to clonedeploy it presents this attachment error
What can I do to work on Windows server 2012
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
Detailed Error Information:
Module IIS Web Core
Handler Not yet determined
Error Code 0x80070021
Config Error This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault="Deny"), or set explicitly by a location tag with overrideMode="Deny" or the legacy allowOverride="false".
Config File \?\C:\Program Files (x86)\clonedeploy\web\web.config
Requested URL http://localhost:80/clonedeploy
Physical Path C:\Program Files (x86)\clonedeploy\web
Logon Method Not yet determined
Logon User Not yet determined
56: <validation validateIntegratedModeConfiguration="true" ></validation>
58: <remove name="ExtensionlessUrlHandler-Integrated-4.0" ></remove>
This error occurs when there is a problem reading the configuration file for the Web server or Web application. In some cases, the event logs may contain more information about what caused this error.
View more information »
Was this a newly installed OS? Can you attach the install log?
Hey, i have the same problem over here. Mine is a server 2012 std that gives the same error. what can i do to solve this and start working with CloneDeploy...
Thanks for the free software en help !!
Is this a clean install of server 2012? Is IIS already serving something else?
this is not een clean install, it is an exting server system. IIS is specially installed for CloneDeploy. It wasnt installed before.
How about the install log
where do i find the install log?
found the setup file, i paste a part of the file under here, i get some errors
could this be the problem:
-- Run entry --
2017-03-30 02:25:25.616 Run as: Current user
2017-03-30 02:25:25.616 Type: Exec
2017-03-30 02:25:25.616 Filename: cmd
2017-03-30 02:25:25.616 Parameters: /c net user cd_share_ro CD2016 /add
2017-03-30 02:25:25.663 Process exit code: 2
2017-03-30 02:25:25.663 -- Run entry --
2017-03-30 02:25:25.663 Run as: Current user
2017-03-30 02:25:25.663 Type: Exec
2017-03-30 02:25:25.663 Filename: cmd
2017-03-30 02:25:25.663 Parameters: /c net user cd_share_rw CD2016 /add
2017-03-30 02:25:25.710 Process exit code: 2
2017-03-30 02:25:25.710 -- Run entry --
2017-03-30 02:25:25.710 Run as: Current user
2017-03-30 02:25:25.710 Type: Exec
2017-03-30 02:25:25.710 Filename: cmd
2017-03-30 02:25:25.710 Parameters: /c WMIC USERACCOUNT WHERE "Name='cd_share_ro'" SET PasswordExpires=FALSE
2017-03-30 02:25:32.699 Process exit code: 2147749889
2017-03-30 02:25:32.699 -- Run entry --
2017-03-30 02:25:32.699 Run as: Current user
2017-03-30 02:25:32.699 Type: Exec
2017-03-30 02:25:32.699 Filename: cmd
2017-03-30 02:25:32.699 Parameters: /c WMIC USERACCOUNT WHERE "Name='cd_share_rw'" SET PasswordExpires=FALSE
2017-03-30 02:25:32.786 Process exit code: 2147749889
2017-03-30 02:25:32.787 -- Run entry --
That's unrelated to IIS. Here is a link for that error with a possible solution. I would try the accepted solution.
Thanks for this link. the result is that i am getting an other error : 500.21 (see below)
Is this error a common issue?
HTTP Error 500.21 - Internal Server Error
Handler "ExtensionlessUrlHandler-Integrated-4.0" has a bad module "ManagedPipelineHandler" in its module list
Most likely causes:
•Managed handler is used; however, ASP.NET is not installed or is not installed completely.
•There is a typographical error in the configuration for the handler module list.
•During application initialization, either the application initialization feature has set skipManagedModules to true, or a rewrite rule is setting a URL that maps to a managed handler and is also setting SKIP_MANAGED_MODULES=1.
Things you can try:
•Install ASP.NET if you are using managed handler.
•Ensure that the handler module's name is specified correctly. Module names are case-sensitive and use the format modules="StaticFileModule,DefaultDocumentModule,DirectoryListingModule".
•Ensure that any application initialization rewrite rules set SKIP_MANAGED_MODULE=0 when setting a URL that maps to a managed handler (such as .aspx, for example.)
•As an alternative, ensure that application initialization rewrite rules map the request to an unmanaged handler (for example, to an .htm file, which is mapped to the StaticFileHandler.)
Detailed Error Information:
IIS Web Core
C:\Program Files (x86)\clonedeploy\web
Not real sure what's going on. I typically recommend you install on a newly installed OS, that's the route I would take.
Ok , thanks for yout help, i will try your suggetion