Everything work fine but I can't edit online MS Office documents.
When I click on "Edit online" for excel/word file Excel/Word application starts but I have message:
"Sorry we can't open http://127.0.0.1:8080/alfresco/MG/documentLibrary/Test/curruculum.docx"
Then appear message that Document couldn't get access to that file.
As a client I have MS Office 2016.
Thanku You for any help
Alfresco has to be configured to run on SSL environment, Check the below link:
http://docs.alfresco.com/5.1/tasks/configure-ssl-prod.html
If you are running a non-production environment then you may try to lower the security levels in the local registry to allow MS Office to interact in a non-SSL(http) way with Alfresco.
You have to change share.host=127.0.0.1 in your alfresco-global.properties file to the servers' DNS Name, like alfresco.domain
Related
I'm trying to use the boxr package to link my box account to R-Server.
I get as far in the box_auth() instructions as step 3 from the box pdf https://cran.r-project.org/web/packages/boxr/boxr.pdf
A window pops up and I authorise connection then I get the error 'Safari can't connect to the server'.
I have no knowledge of how apache or web development works so forgive my naivety, I've come to understand the problem is I don't have localhost set up on my Mac.
I'm unable to turn these features on because it requires admin rights and my company won't allow users to have this.
Is there something else I can put in the redirect_uri box apart from localhost that will allow this to authenticate?
Thanks
The issue i had was mostly that authenticating box through R-Server isn't supported. https://github.com/brendan-r/boxr/issues/23
To get around this I used my personal laptop to authenticate locally then uploaded the .Renviron and .boxr-oauth files to R server (which is the advice in the github post)
This was slightly tricky as R wasn't showing the .boxr-oauth file but I managed to copy it to a folder, zip the folder, then upload that to R-Server.
Now running the box_auth() function authenticates as it should.
As of v0.3.5 (November 2019) boxr has a new alternative authentication method designed for remote servers, box_auth_service(), that closes issue 23. It's slightly is different than the oAuth way, because it uses "Service" accounts as the actors instead of the "User" account. But the "Service" accounts are what's needed to maintain security within a organization, so we opted for that. Please open an issue on the repo if you run into any issues.
Our company recently joined a larger company that utilizes Bit9 for application whitelisting. Previously, we had a large amount of users using Harmon.IE to interface with our Sharepoint-based document management system. I'm trying to figure out what to allow in Bit9 to allow the document open process to work in the Harmon.IE outlook add-in.
What's happening is the user tries to open a file from the Harmon.IE pane and Bit9 blocks the auto-generated, randomly-named vbs file used to launch the file from Sharepoint. Since this file is different each time and has a different hash, we can't simply approve the vbs file.
We also can't set wscript as a trusted source as many malware sources utilize wscript. Likewise, can't really allow anything that comes out of Outlook as that would open the door for malware delivery via email.
I'm trying to find out if there's a dll that I can trust somewhere in the stack that will allow these VBS files to be trusted and allowed to run.
Add OpenFilesUsingScript key with default value "False"- harmon.ie will launch files directly without using VB script
[HKEY_CURRENT_USER\Software\Mainsoft\Prefs\OpenFilesUsingScript]
#="False"
A custom rule with an action of Execute Allow on the path of the VBS with the name wild carded as deep as possible should cover you just fine.
I am running C# ASP.NET 4.5 web application on Windows 7 64-bit using IIS 7.5. The application pool it uses has the name 'ASP.NET v4.0' and its identity is ApplicationPoolIdentity. The application uses MS Office Interop (Microsoft Excel 14.0 Object Library).
At line wBook = wBooks.Add(Missing.Value);, it throws the following error:
Microsoft Excel cannot open or save any more documents because there
is not enough available memory or disk space.
u2022 To make more memory available, close workbooks or programs you
no longer need.
u2022 To free disk space, delete files you no longer need from the
disk you are saving to.: at
Microsoft.Office.Interop.Excel.Workbooks.Add(Object Template)
1) I gave the account IIS apppool\ASP.NET v4.0 full control on MS Excel Application in DCOM Config.
2) I gave IIS apppool\ASP.NET v4.0 full control on 'C:\Windows\SysWOW64\config\systemprofile' and created a Desktop folder in it.
3) I need to continue using Interop though it's not recommended.
4) The application works fine on Windows Server 2003/Windows XP 32-bit.
5) MS Office 2010 (64-bit, trial version) is installed on the machine.
6) I would prefer not to change the app. pool identity from ApplicationPoolIdentity to Network Service etc.. ApplicationPoolIdentity is the new type of Identity in IIS 7 and it's recommended.
It works fine if I select 'Interactive User' (I have logged in as an admin) in DCOM Config, but it causes other problems. I need to use 'Launching User' which is ASP.NET v4.0. So it looks like it's a permission issue.
Please help.
Thank you.
Right click on the file with file explorer, choose Properties, then General tab and click on the Unblock button. This error message is very misleading.
Go to this key on Registry Editor (Run | Regedit)
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
change key Cache to something like C:\Windows\Temp
My similar problem was solved like this.
Regards,
Ripley
I had this same issue, there was no issue regarding memory in my server machine, Finally i was able to fix it by following steps
In your application hosting server, go to its "Component Services"
3.Find "Microsoft Excel Application" in right side.
4.Open its properties by right click
5.Under Identity tab select the option interactive user and click Ok button.
Check once again. Hope it helps
NOTE: But now you may end up with another COM error "Retrieving the COM class factory for component...". In that case Just set the Identity to this User and enter the username and password of a user who has sufficient rights. In my case I entered a user of power user group.
Test like this.Sometimes, permission problem.
cmd => dcomcnfg
Click
Component services >Computes >My Computer>Dcom config> and select
micro soft Excel Application
Right Click on microsoft Excel Application
Properties>Give Asp.net Permissions
Select Identity table >Select interactive user >select ok
I too encountered the same scenario and found out two solutions after googling for several times. Hope this helps.
Way 01:
Before trying to open the file in Excel, find it in Windows' File Explorer. Right-click the file and select Properties. At the bottom of the General tab, click the Unblock button. Once you unblock a file, Windows should remember and Excel should not ask you again.
This option is available for some file types, but not others. If you don't have an Unblock button, use Way 2.
Way 02:
This option is better if you usually store your downloaded Excel files in one folder. In Excel, click File » Options » Trust Center » Trust Center Settings » Trusted Locations. Click Add new location. Browse to the folder where you store your Excel files, select Subfolders of this location are also trusted, and click OK.
If none of the above worked, try these as well:
In Component services >Computes >My Computer>Dcom config>Microsoft Excel Application>Properties, go to security tab, click on customize on all three sections and add the user that want to run the application, and give full permissions to the user.
Go to C:\Windows\Temp make sure it exists and it doesn't prompt you for entering.
After giving necessary permissions in DCOM configurations I also needed to change the identity of my application in the IIS to a custom account
A user with permission to create folders and components is not able to copy and paste items through WebDAV. This User is using Mac OS X Lion. The error he gets is that he does not have read and write permissions. Is there any resolution?
The WebDAV Connector is enabled by default server-side per the SDLLiveContent documentation at least for SDL Tridion 2011.
Only valid items are allowed via WebDAV which includes binaries (multimedia in Tridion), .xml components, and other types.
It seems like the user doesn't have permissions to read and write for a given folder. You can confirm by having them attempt creating folders or components in the same folder in the Content Manager Explorer (CME).
Is it possible that the Mac does not authenticate properly to Windows. In this case, you should be able to see the failed connections in your server logs. Is this user (or any other Mac user) able to use webdav successfully in any other folders?
As it's been suggested already, you will have to do some detective work to determine what exactly is failing. Tridion permissions do not change based on the client you use, so if they work from one client, they must work from another (excluding authentication issues here).
Go to your Windows Event Viewer, Tridion Content Manager log, check for error messages written to it when you try to copy content from the mac.
Post the exact error message you're getting. I doubt that Tridion is telling you "user is don't have read and write access"
Bottom line, if it works from Windows and not Mac, the issue is not with the WebDav server, but with the WebDav Client.
I also fail to see the programming question on this one...
What version of Tridion are you using? First action which you should do is to check Event Log for error messages (it was already suggested by Peter Kjaer), if you don't have anything there you can try to enable webdav debug logging by modifying cc_crtd_def.xml file which is situated in Tridion\webdav\WebDAVcartridges\Default\ folder. You should change loglevel property (as far as I remember it should be 4 for debug). And then there should be a log file created in the same folder or in webdav folder. You can try to find exact error message in this log file and post it here.
I use the following code snippet to open a local docx file and it runs fine when I press Ctrl+F5 in Visual Studio. I just click the button and the Word2007 on my machine is opened and the docx is displayed there. But after I publish the application to the production server, it didn't work. After I click the same button, nothing happened. Could someone tell me why?
What I want is to open a local stored docx in client side's Word 2007 from asp.net application. I don't want to use office COM object.
My code:
ProcessStartInfo psi = new ProcessStartInfo(#"winword.exe",#"/test.docx");
Process.Start(psi);
Many thanks.
Your code is attempting to open Word on the server and not on the client. The only reason it works in development is the the client and server are on the same machine.
You cannot open Word on the client due to browser security restrictions. However if you provide a link to the file, the user will be able to download and open the file if they have Word installed.
If you want to open a local stored document, on the client's machine, you should create a link to the document (using the path on the client's harddisk). The browser will ask the user for permission to open it, but this should work.
The reason your code worked, was because the server and the client are the same machine when debugging. The development server even runs using your profile.
In production the server can be on the other side of the world. The C# code you show in your snippet is executed on the server.
Check if the file exists in the same location.
ProcessStartInfo psi = new ProcessStartInfo()
is working on server and it is trying to pick the file from server location and it can never run client side file.
The only thing you can do is let them download the file. If they don't have office, or don't have the right compatability pack, they won't be able to open it.