ERROR 404

nati218 — Wed, 06 Mar 2019 16:55:27 GMT

Hola, He estado intentando instalar el modulo de auditoria, pero ahora ya no me carga el share... ¿alguna idea que podría ser? dejo el log2019-03-06 13:47:59 Commons Daemon procrun stdout initialized2019-03-06 13:48:09,874 ERROR [extensions.config.BaseConfigService] [localhost-startStop-1] Input str

Re: ERROR 404

angelborroy — Wed, 06 Mar 2019 17:07:31 GMT

Hay un error de configuración en el archivo alfresco/web-extension/share-config-custom.xm

El XML no es correcto.

Re: ERROR 404

nati218 — Wed, 06 Mar 2019 17:12:34 GMT

si, pero no lo he modificado...

<alfresco-config>

<flags>

<!--

Developer debugging setting to turn on DEBUG mode for client scripts in the browser

-->

<client-debug>false</client-debug>

<!--

LOGGING can always be toggled at runtime when in DEBUG mode (Ctrl, Ctrl, Shift, Shift).

This flag automatically activates logging on page load.

-->

<client-debug-autologging>false</client-debug-autologging>

</flags>

</config>

<web-framework>

<!--

Developers can set mode to 'development' to disable; SpringSurf caches,

FreeMarker template caching and Rhino JavaScript compilation.

-->

<mode>production</mode>

</autowire>

<module-deployment>

<mode>manual</mode>

<enable-auto-deploy-modules>true</enable-auto-deploy-modules>

</module-deployment>

</web-framework>

</config>

<!--

</config>

-->

<!--

To run the CSRF Token Filter behind 1 or more proxies that do not rewrite the Origin or Referere headers:

1. Copy the "CSRFPolicy" default config in share-security-config.xml and paste it into this file.

2. Replace the old config by setting the <config> element's "replace" attribute to "true" like below:

3. To every <action name="assertReferer"> element add the following child element

<param name="referer">http://www.proxy1.com/.*|http://www.proxy2.com/.*</param>

4. To every <action name="assertOrigin"> element add the following child element

<param name="origin">http://www.proxy1.com|http://www.proxy2.com</param>

-->

<!--

Remove the default wildcard setting and use instead a strict whitelist of the only domains that shall be allowed

to be used inside iframes (i.e. in the WebView dashlet on the dashboards)

-->

<!--

<cross-domain>

<url>http://www.trusted-domain-1.com/</url>

<url>http://www.trusted-domain-2.com/</url>

</cross-domain>

</config>

-->

<!--

<name>X-Frame-Options</name>

<enabled>false</enabled>

</header>

</headers>

</config>

-->

<!--

<name>Strict-Transport-Security</name>

</header>

</headers>

</config>

-->

<share-urls>

<!--

To locate your current repositoryId go to Admin Console > General > Repository Information:

http://localhost:8080/alfresco/s/enterprise/admin/admin-repositoryinfo

Example config entry:

<share-url repositoryId="622f9533-2a1e-48fe-af4e-ee9e41667ea4">http://new-york-office:8080/share/</share-url>

-->

</share-urls>

</config>

<tree>

<!--

Whether the folder Tree component should enumerate child folders or not.

This is a relatively expensive operation, so should be set to "false" for Repositories with broad folder structures.

-->

<evaluate-child-folders>false</evaluate-child-folders>

<!--

Optionally limit the number of folders shown in treeview throughout Share.

-->

<maximum-folder-count>1000</maximum-folder-count>

<!--

Default timeout in milliseconds for folder Tree component to recieve response from Repository

-->

</tree>

<!--

Used by "Manage Rules" -> "Add aspect" action.

If an aspect has been specified without a title element in the content model,

or you need to support multiple languages,

then an i18n file is needed on the Repo AMP/JAR extension side for the aspect to

be visible when creating rules:

custom_customModel.aspect.custom_myaspect.title=My Aspect

Used by the "Manage Aspects" action.

For the aspect to have a localised label add relevant i18n string(s) in a Share AMP/JAR extension:

aspect.custom_myaspect=My Aspect

-->

</visible>

</addable>

</removeable>

</aspects>

<!--

Used by "Manage Rules" -> "Specialise type" action.

If a type has been specified without a title element in the content model,

or you need to support multiple languages,

then an i18n file is needed on the Repo AMP/JAR extension side for the type to

be visible when creating rules:

custom_customModel.type.custom_mytype.title=My SubType

Used by the "Change Type" action.

For the type to have a localised label add relevant i18n string(s) in a Share AMP/JAR extension:

type.custom_mytype=My SubType

Define valid subtypes using the following example:

</type>

-->

<types>

</type>

</type>

</type>

</types>

<!--

If set, will present a WebDAV link for the current item on the Document and Folder details pages.

Also used to generate the "View in Alfresco Explorer" action for folders.

-->

<repository-url>http://localhost:8080/alfresco</repository-url>

<!--

Google Docs™ integration

-->

<google-docs>

<!--

Enable/disable the Google Docs UI integration (Extra types on Create Content menu, Google Docs actions).

-->

<enabled>false</enabled>

<!--

The mimetypes of documents Google Docs allows you to create via the Share interface.

The I18N label is created from the "type" attribute, e.g. google-docs.doc=Google Docs™ Document

-->

<creatable-types>

<creatable type="doc">application/vnd.openxmlformats-officedocument.wordprocessingml.document</creatable>

<creatable type="xls">application/vnd.openxmlformats-officedocument.spreadsheetml.sheet</creatable>

<creatable type="ppt">application/vnd.ms-powerpoint</creatable>

</creatable-types>

</google-docs>

<!--

File upload configuration

-->

<file-upload>

<!--

Adobe Flash™

In certain environments, an HTTP request originating from Flash cannot be authenticated using an existing session.

See: http://bugs.adobe.com/jira/browse/FP-4830

For these cases, it is useful to disable the Flash-based uploader for Share Document Libraries.

-->

<adobe-flash-enabled>true</adobe-flash-enabled>

</file-upload>

</config>

<!--

-->

<!--

-->

</actionGroup>

</actionGroups>

</config>

<rootLabel>location.path.documents</rootLabel>

<uri>slingshot/doclib/treenode/site/{site}/{container}{path}?children={evaluateChildFoldersSite}&max={maximumFolderCountSite}</uri>

</container>

</siteTree>

</config>

<!--

Root nodeRef or xpath expression for top-level folder.

e.g. alfresco://user/home, /app:company_home/st:sites/cm:site1

If using an xpath expression, ensure it is properly ISO9075 encoded here.

-->

<root-node>alfresco://company/home</root-node>

<tree>

<!--

Whether the folder Tree component should enumerate child folders or not.

This is a relatively expensive operation, so should be set to "false" for Repositories with broad folder structures.

-->

<evaluate-child-folders>false</evaluate-child-folders>

<!--

Optionally limit the number of folders shown in treeview throughout Share.

-->

<maximum-folder-count>500</maximum-folder-count>

</tree>

<!--

Whether the link to the Repository Library appears in the header component or not.

-->

</config>

<!--

Password for HTTP service account.

The account name *must* be built from the HTTP server name, in the format :

HTTP/<server_name>@<realm>

(NB this is because the web browser requests an ST for the

HTTP/<server_name> principal in the current realm, so if we're to decode

that ST, it has to match.)

-->

<password>secret</password>

<!--

Kerberos realm and KDC address.

-->

<realm>ALFRESCO.ORG</realm>

<!--

Service Principal Name to use on the repository tier.

This must be like: HTTP/host.name@REALM

-->

<endpoint-spn>HTTP/repository.server.com@ALFRESCO.ORG</endpoint-spn>

<!--

JAAS login configuration entry name.

-->

<config-entry>ShareHTTP</config-entry>

<!--

A Boolean which when true strips the @domain sufix from Kerberos authenticated usernames.

Use together with stripUsernameSuffix property in alfresco-global.properties file.

-->

</kerberos>

</config>

<!--

<activiti-admin-url>http://localhost:8080/alfresco/activiti-admin</activiti-admin-url>

</config>

-->

<id>alfresco-noauth</id>

<name>Alfresco - unauthenticated access</name>

<description>Access to Alfresco Repository WebScripts that do not require authentication</description>

<connector-id>alfresco</connector-id>

<endpoint-url>http://localhost:8080/alfresco/s</endpoint-url>

</endpoint>

<id>alfresco</id>

<name>Alfresco - user access</name>

<description>Access to Alfresco Repository WebScripts that require user authentication</description>

<connector-id>alfresco</connector-id>

<endpoint-url>http://localhost:8080/alfresco/s</endpoint-url>

</endpoint>

<id>alfresco-feed</id>

<name>Alfresco Feed</name>

<description>Alfresco Feed - supports basic HTTP authentication via the EndPointProxyServlet</description>

<connector-id>http</connector-id>

<endpoint-url>http://localhost:8080/alfresco/s</endpoint-url>

<basic-auth>true</basic-auth>

</endpoint>

<id>alfresco-api</id>

<parent-id>alfresco</parent-id>

<name>Alfresco Public API - user access</name>

<description>Access to Alfresco Repository Public API that require user authentication.

This makes use of the authentication that is provided by parent 'alfresco' endpoint.</description>

<connector-id>alfresco</connector-id>

<endpoint-url>http://localhost:8080/alfresco/api</endpoint-url>

</endpoint>

</remote>

</config>

<!--

Overriding endpoints to reference an Alfresco server with external SSO enabled

NOTE: If utilising a load balancer between web-tier and repository cluster, the "sticky

sessions" feature of your load balancer must be used.

NOTE: If alfresco server location is not localhost:8080 then also combine changes from the

"example port config" section below.

*Optional* ssl-config contains:

keystore for managing client key and certificate.

truststore for managing trusted CAs.

Used to authenticate share to an external SSO system such as CAS or

to make share talk to SSL layers that require client certificates.

Remove the ssl-config section if not required i.e. for NTLM.

NOTE: For Kerberos SSO rename the "KerberosDisabled" condition above to "Kerberos"

NOTE: For external SSO, switch the endpoint connector to "alfrescoHeader" and set

the userHeader value to the name of the HTTP header that the external SSO

uses to provide the authenticated user name.

NOTE: For external SSO, Share now supports the "userIdPattern" mechanism as is available

on the repository config for External Authentication sub-system. Add the following

element to your "alfrescoHeader" connector config:

<userIdPattern>^ignore-(\w+)-ignore</userIdPattern>

This is an example, ensure the Id pattern matches your repository config.

NOTE: For external SSO, Share now supports stateless (no Http Session or sticky session)

connection to the repository when using the alfrescoHeader remote user connector.

e.g. You can change endpoint config to use the faster /service URL instead of the

/wcs URL if you are using External Authentication and then remove sticky session config

from your proxy between Share and Alfresco. Note that this is also faster because Share

will no longer call the /touch REST API before every remote call to the repository.

-->

<!--

<ssl-config>

<keystore-path>alfresco/web-extension/alfresco-system.p12</keystore-path>

<keystore-type>pkcs12</keystore-type>

<keystore-password>alfresco-system</keystore-password>

<truststore-path>alfresco/web-extension/ssl-truststore</truststore-path>

<truststore-type>JCEKS</truststore-type>

<truststore-password>password</truststore-password>

<verify-hostname>true</verify-hostname>

</ssl-config>

<id>alfrescoCookie</id>

<name>Alfresco Connector</name>

<description>Connects to an Alfresco instance using cookie-based authentication</description>

<class>org.alfresco.web.site.servlet.SlingshotAlfrescoConnector</class>

</connector>

<id>alfrescoHeader</id>

<name>Alfresco Connector</name>

<description>Connects to an Alfresco instance using header and cookie-based authentication</description>

<class>org.alfresco.web.site.servlet.SlingshotAlfrescoConnector</class>

<userHeader>SsoUserHeader</userHeader>

</connector>

<id>alfresco</id>

<name>Alfresco - user access</name>

<description>Access to Alfresco Repository WebScripts that require user authentication</description>

<connector-id>alfrescoCookie</connector-id>

<endpoint-url>http://localhost:8080/alfresco/wcs</endpoint-url>

<external-auth>true</external-auth>

</endpoint>

<id>alfresco-feed</id>

<parent-id>alfresco</parent-id>

<name>Alfresco Feed</name>

<description>Alfresco Feed - supports basic HTTP authentication via the EndPointProxyServlet</description>

<connector-id>alfrescoHeader</connector-id>

<endpoint-url>http://localhost:8080/alfresco/wcs</endpoint-url>

<external-auth>true</external-auth>

</endpoint>

<id>alfresco-api</id>

<parent-id>alfresco</parent-id>

<name>Alfresco Public API - user access</name>

<description>Access to Alfresco Repository Public API that require user authentication.

This makes use of the authentication that is provided by parent 'alfresco' endpoint.</description>

<connector-id>alfrescoHeader</connector-id>

<endpoint-url>http://localhost:8080/alfresco/api</endpoint-url>

<external-auth>true</external-auth>

</endpoint>

</remote>

</config>

-->

<!--

<plug-ins>

<element-readers>

<element-reader element-name="cookie" class="org.alfresco.web.config.cookie.CookieElementReader"/>

</element-readers>

</plug-ins>

<enableCookie>false</enableCookie>

<cookies-to-remove>

<cookie-to-remove>alfUsername3</cookie-to-remove>

<cookie-to-remove>alfLogin</cookie-to-remove>

</cookies-to-remove>

</cookie>

</config>

-->

<advanced-search>

<!– Forms for the advanced search type list –>

<forms>

<form labelId="search.form.label.cm_content" descriptionId="search.form.desc.cm_content">cm:content</form>

<form labelId="search.form.label.cm_folder" descriptionId="search.form.desc.cm_folder">cm:folder</form>

<form labelId="type.pr_ejemplo" descriptionId="search.form.desc.pr_ejemplor">pr:ejemplo</form>

</forms>

</advanced-search>

</config>

</alfresco-config>

Re: ERROR 404

angelborroy — Wed, 06 Mar 2019 17:30:53 GMT

Parece que hay un carácter extraño aquí:

<!– Forms for the advanced search type list –>‍

Elimina esa línea.

Re: ERROR 404

nati218 — Wed, 06 Mar 2019 17:47:09 GMT

intente con varios cambios,pero nada...incluso desinstale el modulo de auditoria y nada...

Help please jajaj

Re: ERROR 404

nati218 — Wed, 06 Mar 2019 18:05:43 GMT

De hecho ahora me arroja el siguiente error

2019-03-06 15:02:51,504 ERROR [solr.tracker.AbstractTracker] [org.alfresco.solr.AlfrescoCoreAdminHandler@11307b21_Worker-2] Model tracking failed
org.alfresco.error.AlfrescoRuntimeException: 02060000 GetModelsDiff return status is 404
at org.alfresco.solr.client.SOLRAPIClient.getModelsDiff(SOLRAPIClient.java:1181)
at org.alfresco.solr.tracker.ModelTracker.trackModelsImpl(ModelTracker.java:256)
at org.alfresco.solr.tracker.ModelTracker.trackModels(ModelTracker.java:214)
at org.alfresco.solr.tracker.ModelTracker.ensureFirstModelSync(ModelTracker.java:236)
at org.alfresco.solr.tracker.CoreWatcherJob.registerForCore(CoreWatcherJob.java:145)
at org.alfresco.solr.tracker.CoreWatcherJob.execute(CoreWatcherJob.java:82)
at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:563)

Re: ERROR 404

roberto_gamiz — Wed, 06 Mar 2019 18:45:11 GMT

No hagas caso a ese error, da porque el repositorio no esta levantado y el proceso de SOLR que intenta buscar las modificaciones para actualizar los indices no encuentra respuesta.

El error que tienes que buscar son los que dan durante el inicio del repositorio.

¿Has probado lo que te han sugerido antes?

Los comentarios en xml se indican con la combinación

<!-- ... -->

Sin embargo en esa linea pone:

<!– ... –>

Re: ERROR 404

nati218 — Wed, 06 Mar 2019 19:08:24 GMT

No, no me ha funcionado.

he leído esta conversación Status 404 after applying new AMP mi problema ocurrió porque cuando instale el modulo de auditoria no bote el servicio....en resumen eliminé lo que mencionaban y funcionó nuevamente.

GRACIAS POR LA AYUDA y BUENA DISPOSICIÓN!

topic Re: ERROR 404 in Alfresco Archive

ERROR 404

Re: ERROR 404

Re: ERROR 404

Re: ERROR 404

Re: ERROR 404

Re: ERROR 404

Re: ERROR 404

Re: ERROR 404