I am using FrameMaker and the CMS feature to check documents out of our SharePoint repository at work. I can check documents out and edit them after I have logged into the repository manager. I edit my document but then when I right click on the document in the repository manager to check it back in, the "check in" option is grayed out or not selectable. Does anybody know what I have to do to correct this? I have the correct permissions to the SharePoint directory since I am the one who created the directory in the first place.
I thank you for your help!
I know this post is quite old, but I am facing the same problem. When I try to check-in any files, that particular option is grayed-out. I've also read about this in the other forum discussions. None of the proposed solutions has helped yet. Anybody around with some ideas?
If nothing has worked for you yet, you could try the demo version of FM12 to see if this behaves better with Sharepoint. There has been some work done on the connectors in the the two releases since FM10.
Also, are you fully patched in FM10? The latest version was 10.0.2 (see: http://www.adobe.com/support/downloads/product.jsp?product=22&platform =Windows)
Thanks for your quick response! I should have mentioned, that I was already trying FrameMaker 12 and we are using SharePoint 2013. As this didn't work and had tried my luck with RoboHelp 11. Now what seems a bit odd to me is the fact it is running with RoboHelp and its SharePoint Connector. When I try the same with FM12 it won't let me check in any files, RH works fine. I think from that perspective it not authorization related.
Just to be sure -- have you saved the file before trying to check it in?
It's a litle while since I've worked with FM and the SharPoint connector, and I no longer have the ability to test this. But when you check out a file, Adobe creates a local copy. You may need to save the local copy before you can check it back in.
It has been the same for every version from 9 forward. Should 12 be any different?
I use Adobe FrameMaker because it's the best solution available. What incenses me is that Adobe IGNORES these kinds of problems.
If you have CMS integration with SharePoint, DON'T MAKE YOUR CUSTOMERS RESPONSIBLE FOR TROUBLESHOOTING IT!!!!!
Stop acting like Miicrosoft!!!!!