New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

uploading issue - operation failure popup. #122

Open
monicakumari opened this Issue Aug 22, 2017 · 27 comments

Comments

Projects
None yet
4 participants
@monicakumari

monicakumari commented Aug 22, 2017

uploadexception.docx

while using uploader plus, applying on document library(the root folder of a site) - it just through some exception and a popup on the sceen, says operation failure. - multiple users reported the issue.
I have attached the exception details.
as a developer, what I should do? or where should I look for the issue ?

@yregaieg

This comment has been minimized.

Show comment
Hide comment
@yregaieg

yregaieg Aug 22, 2017

Collaborator

Sounds like you have a node with a corrupt name, try replacing

"path": "${node.displayPath}\/${node.properties.name}",

with

"path": "${node.displayPath!js_string}\/${node.properties.name!js_string}",

in tomcat/webapps/alfresco/WEB-INF/classes/alfresco/templates/webscripts/com/softwareloop/uploader-plus/upload-folders-new.post.json.ftl
then restart alfresco or refresh repo webscripts
and let me know if that solves it ?

Collaborator

yregaieg commented Aug 22, 2017

Sounds like you have a node with a corrupt name, try replacing

"path": "${node.displayPath}\/${node.properties.name}",

with

"path": "${node.displayPath!js_string}\/${node.properties.name!js_string}",

in tomcat/webapps/alfresco/WEB-INF/classes/alfresco/templates/webscripts/com/softwareloop/uploader-plus/upload-folders-new.post.json.ftl
then restart alfresco or refresh repo webscripts
and let me know if that solves it ?

@monicakumari

This comment has been minimized.

Show comment
Hide comment
@monicakumari

monicakumari Aug 23, 2017

I did the same.. but it did not worked.

I am attaching the error popup. and the exceptions.
uploader-plus_exception.docx
screenshot from 2017-08-23 12-01-24

monicakumari commented Aug 23, 2017

I did the same.. but it did not worked.

I am attaching the error popup. and the exceptions.
uploader-plus_exception.docx
screenshot from 2017-08-23 12-01-24

@yregaieg

This comment has been minimized.

Show comment
Hide comment
@yregaieg

yregaieg Aug 23, 2017

Collaborator

@monicakumari does admin user face the same issue ?

Collaborator

yregaieg commented Aug 23, 2017

@monicakumari does admin user face the same issue ?

@monicakumari

This comment has been minimized.

Show comment
Hide comment
@monicakumari

monicakumari Aug 23, 2017

yes, I am working as an admin.

monicakumari commented Aug 23, 2017

yes, I am working as an admin.

@yregaieg

This comment has been minimized.

Show comment
Hide comment
@yregaieg

yregaieg Aug 23, 2017

Collaborator

Alright, if you confirm that you can easily reproduce this as admin, can you also confirm that solr tracking is working ?

Collaborator

yregaieg commented Aug 23, 2017

Alright, if you confirm that you can easily reproduce this as admin, can you also confirm that solr tracking is working ?

@monicakumari

This comment has been minimized.

Show comment
Hide comment
@monicakumari

monicakumari Aug 23, 2017

yes. solr tracking is working fine.

monicakumari commented Aug 23, 2017

yes. solr tracking is working fine.

@monicakumari

This comment has been minimized.

Show comment
Hide comment
@monicakumari

monicakumari Aug 23, 2017

This error is only coming when we try to apply the uploader plus on the documentLibrary of the particular site.

monicakumari commented Aug 23, 2017

This error is only coming when we try to apply the uploader plus on the documentLibrary of the particular site.

@monicakumari

This comment has been minimized.

Show comment
Hide comment
@monicakumari

monicakumari Aug 23, 2017

uploader plus is working fine for the individual folders. but issue comes when we are applying this to the documentLibrary folder of a particular website.

monicakumari commented Aug 23, 2017

uploader plus is working fine for the individual folders. but issue comes when we are applying this to the documentLibrary folder of a particular website.

@yregaieg

This comment has been minimized.

Show comment
Hide comment
@yregaieg

yregaieg Aug 23, 2017

Collaborator

Alright then! Is there a chance your site (or any of the folders inside document library) has a strange (or special) names ?

Collaborator

yregaieg commented Aug 23, 2017

Alright then! Is there a chance your site (or any of the folders inside document library) has a strange (or special) names ?

@monicakumari

This comment has been minimized.

Show comment
Hide comment
@monicakumari

monicakumari Aug 23, 2017

I have applied an action on a folder using add-on.

monicakumari commented Aug 23, 2017

I have applied an action on a folder using add-on.

@monicakumari

This comment has been minimized.

Show comment
Hide comment
@monicakumari

monicakumari Aug 23, 2017

can you please help me to understand, what kind of strange or special names ??

monicakumari commented Aug 23, 2017

can you please help me to understand, what kind of strange or special names ??

@monicakumari

This comment has been minimized.

Show comment
Hide comment
@monicakumari

monicakumari Aug 23, 2017

I have applied some rule on some folders.

monicakumari commented Aug 23, 2017

I have applied some rule on some folders.

@yregaieg

This comment has been minimized.

Show comment
Hide comment
@yregaieg

yregaieg Aug 23, 2017

Collaborator

Can you share more details about the addon?

Collaborator

yregaieg commented Aug 23, 2017

Can you share more details about the addon?

@yregaieg

This comment has been minimized.

Show comment
Hide comment
@yregaieg

yregaieg Aug 23, 2017

Collaborator

Is there a chance it has behaviours that fiddle with file names / add some custom permission logic / add some custom versioning logic ?

Collaborator

yregaieg commented Aug 23, 2017

Is there a chance it has behaviours that fiddle with file names / add some custom permission logic / add some custom versioning logic ?

@monicakumari

This comment has been minimized.

Show comment
Hide comment
@monicakumari

monicakumari Aug 23, 2017

yes.. I have applied folder-quota action/add-on on some folder. applied some rules over some folders. other than this, all folders/data looks fine

monicakumari commented Aug 23, 2017

yes.. I have applied folder-quota action/add-on on some folder. applied some rules over some folders. other than this, all folders/data looks fine

@monicakumari

This comment has been minimized.

Show comment
Hide comment
@monicakumari

monicakumari Aug 23, 2017

I have checked the documentLibrary folder using node browser too.. but there is no issue with this folder.

monicakumari commented Aug 23, 2017

I have checked the documentLibrary folder using node browser too.. but there is no issue with this folder.

@yregaieg

This comment has been minimized.

Show comment
Hide comment
@yregaieg

yregaieg Aug 23, 2017

Collaborator

OK,

I will give you this last hint, although I am not confident it would work !
Could you try and set this as the content of your upload-folders-new.post.js

<import resource="classpath:/alfresco/templates/webscripts/org/alfresco/slingshot/documentlibrary/parse-args.lib.js">

var storeType = url.templateArgs.store_type;
var storeId = url.templateArgs.store_id;
var id = url.templateArgs.id;

var nodeRef = storeType + "://" + storeId + (id == null ? "" : ("/" + id));
var node = ParseArgs.resolveNode(nodeRef);
model.node = node;
logger.warn("Just fetched the node and nodeRef was set to :" + node.nodeRef); // new line

if (node.hasAspect("up:UploadFolder")) {
    model.status = 1;
    } else {
    var props = new Array(2);
    props["up:allowedTypes"] = null;
    node.addAspect("up:UploadFolder", props);
    node.save();
    logger.warn("Just saved the node and nodeRef was set to :" + node.nodeRef); // new line
    model.node = node; // new line
    model.status = 0;
    }

Restart alfresco/refresh repo webscripts and see if that solves it !

Collaborator

yregaieg commented Aug 23, 2017

OK,

I will give you this last hint, although I am not confident it would work !
Could you try and set this as the content of your upload-folders-new.post.js

<import resource="classpath:/alfresco/templates/webscripts/org/alfresco/slingshot/documentlibrary/parse-args.lib.js">

var storeType = url.templateArgs.store_type;
var storeId = url.templateArgs.store_id;
var id = url.templateArgs.id;

var nodeRef = storeType + "://" + storeId + (id == null ? "" : ("/" + id));
var node = ParseArgs.resolveNode(nodeRef);
model.node = node;
logger.warn("Just fetched the node and nodeRef was set to :" + node.nodeRef); // new line

if (node.hasAspect("up:UploadFolder")) {
    model.status = 1;
    } else {
    var props = new Array(2);
    props["up:allowedTypes"] = null;
    node.addAspect("up:UploadFolder", props);
    node.save();
    logger.warn("Just saved the node and nodeRef was set to :" + node.nodeRef); // new line
    model.node = node; // new line
    model.status = 0;
    }

Restart alfresco/refresh repo webscripts and see if that solves it !

@monicakumari

This comment has been minimized.

Show comment
Hide comment
@monicakumari

monicakumari Aug 23, 2017

okay, I am checking it.

monicakumari commented Aug 23, 2017

okay, I am checking it.

@monicakumari

This comment has been minimized.

Show comment
Hide comment
@monicakumari

monicakumari Aug 23, 2017

getting the same popup. didn't worked.

exceptions..
uploader-plus_exception.docx

monicakumari commented Aug 23, 2017

getting the same popup. didn't worked.

exceptions..
uploader-plus_exception.docx

@yregaieg

This comment has been minimized.

Show comment
Hide comment
@yregaieg

yregaieg Aug 23, 2017

Collaborator

I would be interested in checking the warn messages from the two lines in the log before the errors !

Collaborator

yregaieg commented Aug 23, 2017

I would be interested in checking the warn messages from the two lines in the log before the errors !

@monicakumari

This comment has been minimized.

Show comment
Hide comment
@monicakumari

monicakumari Aug 24, 2017

sure, can you please tell me - what line should be added to show this warn message in log4j.properties file ?
because whatever the exception or messages came, I have already sent you.
thank you.

monicakumari commented Aug 24, 2017

sure, can you please tell me - what line should be added to show this warn message in log4j.properties file ?
because whatever the exception or messages came, I have already sent you.
thank you.

@monicakumari

This comment has been minimized.

Show comment
Hide comment
@monicakumari

monicakumari Aug 24, 2017

I have tried curl command using noderef id.

curl -uadmin:admin -X POST http://localhost:8080/alfresco/service/uploader-plus/upload-folders-new/workspace/SpacesStore/8f2105b4-daaf-4874-9e8a-2152569d109b
got result-----

{
"status": 0,
"node": {
"nodeRef": "workspace://SpacesStore/9b38e1b6-7d8c-4504-bb97-97aac47e225d",
"path": "/Company Home/Sites/testSite/documentLibrary",
"allowedTypes": []
}
}
this was correct and uploader plus was working fine for this node.

another one--
curl -uadmin:admin -X POST http://localhost:8080/alfresco/service/uploader-plus/upload-folders-new/workspace/SpacesStore/00b4b77b-f57e-42ff-86dc-49302c2a34d0

and the result ----

{
"status" :
{
"code" : 500,
"name" : "Internal Error",
"description" : "An error inside the HTTP server which prevented it from fulfilling the request."
},

"message" : "07240089 Wrapped Exception (with status template): 07240021 Error during processing of the template 'get(properties) failed on instance of org.alfresco.repo.template.TemplateNode. See cause exception.\n\nThe failing instruction:\n==> ${node.properties.name!js_string} auto-escaped [in template "uploader-plus/upload-folders-new.post.json.ftl" at line 6, column 31]'. Please contact your system administrator.",
"exception" : "",

"callstack" :
[

],

"server" : "Community v5.2.0 (r135134-b14) schema 10,005",
"time" : "Aug 24, 2017 4:26:20 PM"
}

here the issue for this documentLibrary folder.

monicakumari commented Aug 24, 2017

I have tried curl command using noderef id.

curl -uadmin:admin -X POST http://localhost:8080/alfresco/service/uploader-plus/upload-folders-new/workspace/SpacesStore/8f2105b4-daaf-4874-9e8a-2152569d109b
got result-----

{
"status": 0,
"node": {
"nodeRef": "workspace://SpacesStore/9b38e1b6-7d8c-4504-bb97-97aac47e225d",
"path": "/Company Home/Sites/testSite/documentLibrary",
"allowedTypes": []
}
}
this was correct and uploader plus was working fine for this node.

another one--
curl -uadmin:admin -X POST http://localhost:8080/alfresco/service/uploader-plus/upload-folders-new/workspace/SpacesStore/00b4b77b-f57e-42ff-86dc-49302c2a34d0

and the result ----

{
"status" :
{
"code" : 500,
"name" : "Internal Error",
"description" : "An error inside the HTTP server which prevented it from fulfilling the request."
},

"message" : "07240089 Wrapped Exception (with status template): 07240021 Error during processing of the template 'get(properties) failed on instance of org.alfresco.repo.template.TemplateNode. See cause exception.\n\nThe failing instruction:\n==> ${node.properties.name!js_string} auto-escaped [in template "uploader-plus/upload-folders-new.post.json.ftl" at line 6, column 31]'. Please contact your system administrator.",
"exception" : "",

"callstack" :
[

],

"server" : "Community v5.2.0 (r135134-b14) schema 10,005",
"time" : "Aug 24, 2017 4:26:20 PM"
}

here the issue for this documentLibrary folder.

@tusharkhanka

This comment has been minimized.

Show comment
Hide comment
@tusharkhanka

tusharkhanka Jun 19, 2018

hi one of our customers got affected with the same kinda issue i checked in the node browser from admin console turns out the buggy folder that gets this "operation Failed issue" has an issue with "cm:tagScopeCache | d:content | null | " so couldn't exactly reproduce the steps. can you plase share if it can be a cause to the isse since on the logs it is same as @monicakumari has shared

tusharkhanka commented Jun 19, 2018

hi one of our customers got affected with the same kinda issue i checked in the node browser from admin console turns out the buggy folder that gets this "operation Failed issue" has an issue with "cm:tagScopeCache | d:content | null | " so couldn't exactly reproduce the steps. can you plase share if it can be a cause to the isse since on the logs it is same as @monicakumari has shared

@deepaktalape

This comment has been minimized.

Show comment
Hide comment
@deepaktalape

deepaktalape Sep 10, 2018

@monicakumari You got any resolotion/work around for this issue, As I am also facing same issue, and not do anything. Thanks in Advance.

deepaktalape commented Sep 10, 2018

@monicakumari You got any resolotion/work around for this issue, As I am also facing same issue, and not do anything. Thanks in Advance.

@deepaktalape

This comment has been minimized.

Show comment
Hide comment
@deepaktalape

deepaktalape Sep 10, 2018

Please update if anyone is having update/resolution for this issue.

deepaktalape commented Sep 10, 2018

Please update if anyone is having update/resolution for this issue.

@monicakumari

This comment has been minimized.

Show comment
Hide comment
@monicakumari

monicakumari Sep 11, 2018

please check tusharkhanka's resolution.

monicakumari commented Sep 11, 2018

please check tusharkhanka's resolution.

@deepaktalape

This comment has been minimized.

Show comment
Hide comment
@deepaktalape

deepaktalape Sep 11, 2018

@monicakumari Actually I am not clear with the comments provided by @tusharkhanka , It will be helpful if you share the cause of issue and resolution for this. Thanks in Advance

deepaktalape commented Sep 11, 2018

@monicakumari Actually I am not clear with the comments provided by @tusharkhanka , It will be helpful if you share the cause of issue and resolution for this. Thanks in Advance

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment