addon enable error Authorization 'NTLM' not supported

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2012 10:21 AM
The character encoding of the plain text document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the file needs to be declared in the transfer protocol or file needs to use a byte order mark as an encoding signature.
I following the following tutorials
http://code.google.com/p/share-extras/wiki/MediaViewers
http://code.google.com/p/share-extras/downloads/detail?name=media-viewers-2.0.jar&can=2&q=
https://ffmpeg.org/trac/ffmpeg/wiki/CentosCompilationGuide
http://ffmpeg.org/download.html
cd x264./configure –enable-shared –prefix=/usrmakemake install
http://kb.liquidweb.com/install-git-on-centos-5/
I am using centos5 64bit
alfresco 4.0d
- Labels:
-
Archive
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2012 06:19 AM
it is unclear to me at which point of your procedure this error appears. Is is part of some log output, presented in a browser window …? Which file is the affected "plain tet document".
Regards
Axel

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2012 06:21 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2012 07:45 AM
- your filesystem encoding
- your Tomcat connector URI encoding settings
- the encoding of the affected file
- the name of the file
- which module you deploy
- what console log the output is on (Share Tomcat, Repository Tomcat, "combined" Tomcat)
Any further information you may have would be helpful.
Regards
Axel

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2012 07:50 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2012 08:06 AM
does the addon actually work? As long as it does and the error is only shown in FireFox console, I would say "don't mind"…
Regards
Axel

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2012 09:24 AM
The extra file is /opt/alfresco-4.0.d/tomcat/shared/classes/alfresco/web-extension/site-webscripts/org/alfresco/components/preview/web-preview.get.config.xml
contents of this file is found here http://code.google.com/p/share-extras/wiki/MediaViewers
Even the alfresco portlet extension add-on does not work
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-28-2012 11:04 AM
Please provide post a screenshot of the error that you see in the browser, and the full stack trace associated with the error, from your log file (or the console).
This is common best practice on technical forums and is part of the Alfresco forum guidelines. I would suggest you review these if you have not already done so.
The error text you mention is not familiar to me, but it would be interesting to know if you also see issues when using the packaged version of the add-on, rather than compiling it yourself, and also if you still see the error after removing your custom web-preview.get.config.xml file.
Thanks,
Will

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-28-2012 11:20 AM
[img]http://img818.imageshack.us/img818/4239/37229016.png[/img]
When I add any of the modules and try to apply changes i get the following. I do not get anything in the log files. I also get the same when i remove the media-preview add-on
[img]http://img593.imageshack.us/img593/3808/pdfviewer.png[/img]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-28-2012 11:36 AM
Since you're using Firebug, you could use the Net panel to see what actual response text gets returned from the server (or try a different browser to see if it will display it). Assuming the response is not empty, there may be some clues in there as to what's going wrong.
Cheers,
Will
