Edited: problem steel present. Look at post bellow.
It's one tip of using MS Office 2016 with AOS.
Do not install "Microsoft SharePoint Foundation Support" component form "Office Tools" section. It marks in registry as HKEY_LOCAL_MACHINE\SOFTWARE\SyncIntegrationClients.
The problems is:
The known solution EnableADAL=0 does not help me at all.
Solved! Go to Solution.
Yes it work.
Second tip.
Don't mount more then one disk for repository. Better don't mount disks at all. Than file moves from one disk to anothe, windows delete source node and makes new. Naturely, document looses all its versions, comments and ather metadate.
Insted of disks, Add a network location to Computer folder in next format:
\\your.domain.com@SSL\DevWWWRoot\alfresco\aos\...
User could have what ever his want qantity of network location folders and move content betwin it by Windows Explorer.
The problem steel present. After installing latest security updates of Office 2016, unstabel connections to aos backed and Word again can't compare versions.
So we discuss to downgrade to 2013 version.
Does anyone have any sugestion how to reanimate Office 2016?
Alfresco 6.1.2-ga / Share 6.1.0 / AOS 1.2.2 / Kerberos SSO
Clients Windows 7 / Office 2016
alfresco-global.properties
# Alfresco Office Services override aos.baseUrlOverwrite=https://dms.uos.ua/alfresco/aos aos.sitePathOverwrite=/alfresco/aos
nginx ssl revers proxy
# SharePoint URLs for Office clients location ~ (^/spp|^/_vti_bin/|^/_vti_history/|^/_vti_inf.html$) { proxy_pass http://alfresco; proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504; proxy_redirect off; proxy_buffering off; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_pass_header Set-Cookie; }
Next manipulations with server.xml doesn't help:
Share dockerfile
# Proxy pass configuration for SSL RUN sed -i '/<Connector port="8080" protocol="HTTP\/1.1"/a \ proxyName="domain.com"\n\ proxyPort="443" \n\ scheme="https" \n\ secure="true" \ ' $TOMCAT_DIR/conf/server.xml
Alfresco dockerfile
# In nginx you should also set the X-Forwarded-* header to remap them in tomcat's server.xml # to avoid trouble with DAV and AOS. e.g. by setting RemoteIpValve: RUN sed -i '/pattern="\%h \%l \%u \%t "\%r" \%s \%b" \/>/a \ <Valve className="org.apache.catalina.valves.RemoteIpValve"\n \ remoteIpHeader="x-forwarded-for"\n \ remoteIpProxiesHeader="x-forwarded-by"\n \ protocolHeader="x-forwarded-proto"\n \/>' $TOMCAT_DIR/conf/server.xml
Hi,
i've got the same problem with MS Office 2016 and 2019 and Windows 10.
Currently, i don't have any solutions
Matthieu
In my case the problem is coming after any of one of this office 2016 updates:
KB4475583, KB4462242, KB4462146, KB4461535, KB4461437, KB4032233, KB448414, KB4475542.
Yes, Windows 10 + office 2016 has the problem too.
We steel have a problem online editing on Office 2016. It's the same resoults on 32 bit win platform and 64 bit. After installing Office updates file opening, but couldn't be saved and have no version history.
Documentation says: Supported versions - Microsoft Office 2016 for Windows (boxed version).
Trobleshouting says: Troubleshooting AOS, Issue with Online Editing, so we take Windows 7 / Office 2016 32 bit both.
Does any body have worked Office 2016, or I should make jira issue?
Thanks!
Hi,
I have the same error, with microsfot word 2016 and 2013 vs Alfresco 6.1 content serives and Alfresco content App 1.8.
desperatly looking for solution i found this link https://answers.microsoft.com/en-us/msoffice/forum/all/upload-failed-were-sorry-someone-updated-the/... .
but i still have this problem.
In my case Office 2013 works fine. Problem solved by downgrading to 2013 version. Users can edit and compare versions of document directli from MS Word.
Hi, finaly i solved the problem,
I've change the aos.baseUrlOverwrite to
aos.baseUrlOverwrite=https://{ip}/alfresco/webdav
It seems that Microsoft word dont able to write at the /alfresco/aos/... path and after i change it to /alfresco/webdav the upload works perfectly on microsoft word 2013 and 2016.
Ask for and offer help to other Alfresco Content Services Users and members of the Alfresco team.
Related links:
By using this site, you are agreeing to allow us to collect and use cookies as outlined in Alfresco’s Cookie Statement and Terms of Use (and you have a legitimate interest in Alfresco and our products, authorizing us to contact you in such methods). If you are not ok with these terms, please do not use this website.