The error you're getting is probably due to the fact that your client (Firefox) is trying to use SSL, but you Apache virtual host does not have SSL enabled.
In order for your clients to be able to communicate via SSL with your front-end proxy, you're going to need to do SSL on the front-end, not in Tomcat. You gain absolutely nothing by using SSL between Apache and Tomcat.
In your <VirtualHost>
block, you're going to need at least:
SSLEngine On
SSLCertificateFile ...
SSLCertificateKeyFile ...
Also, note htat SELinux has absolutely nothing to do with SSL, other than the fact that a misconfigured SELinux environment could prevent Apache from being able to read the necessary SSL certificates.
If you're not using Apache as anything other than a simple proxy and you're really not comfortable with Apache configuration you could in theory get rid of it and just have Tomcat listen on port 443 (by modifying the appropriate Connector
block).
I know this is late, but just in case it might still help someone, I came to find that the odd exception is probably due to a miss-format in the CAML query that is sent to interrogate the list.
In my case, I forgot to add the />
tag closing at the end of an FieldRef
tag.
Here's my stack trace:
[COMException (0x80004005): Cannot complete this action.
Please try again.]
Microsoft.SharePoint.Library.SPRequestInternalClass.GetListItemDataWithCallback2(IListItemSqlClient pSqlClient, String bstrUrl, String bstrListName, String bstrViewName, String bstrViewXml, SAFEARRAYFLAGS fSafeArrayFlags, ISP2DSafeArrayWriter pSACallback, ISPDataCallback pPagingCallback, ISPDataCallback pPagingPrevCallback, ISPDataCallback pFilterLinkCallback, ISPDataCallback pSchemaCallback, ISPDataCallback pRowCountCallback, Boolean& pbMaximalView) +0
Microsoft.SharePoint.Library.SPRequest.GetListItemDataWithCallback2(IListItemSqlClient pSqlClient, String bstrUrl, String bstrListName, String bstrViewName, String bstrViewXml, SAFEARRAYFLAGS fSafeArrayFlags, ISP2DSafeArrayWriter pSACallback, ISPDataCallback pPagingCallback, ISPDataCallback pPagingPrevCallback, ISPDataCallback pFilterLinkCallback, ISPDataCallback pSchemaCallback, ISPDataCallback pRowCountCallback, Boolean& pbMaximalView) +349
[SPException: Cannot complete this action.
Please try again.]
Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx) +40346562
Microsoft.SharePoint.Library.SPRequest.GetListItemDataWithCallback2(IListItemSqlClient pSqlClient, String bstrUrl, String bstrListName, String bstrViewName, String bstrViewXml, SAFEARRAYFLAGS fSafeArrayFlags, ISP2DSafeArrayWriter pSACallback, ISPDataCallback pPagingCallback, ISPDataCallback pPagingPrevCallback, ISPDataCallback pFilterLinkCallback, ISPDataCallback pSchemaCallback, ISPDataCallback pRowCountCallback, Boolean& pbMaximalView) +40195455
Microsoft.SharePoint.SPListItemCollection.EnsureListItemsData() +4292
Microsoft.SharePoint.SPListItemCollection.GetEnumerator() +124
Best Answer
There was an error somewhere in either the list instance, list definition, list schema or the feature receiver, unfortunately with MOSS - you don't always get real error messages or an easy way to debug... So I ended up starting over... completely and building in functionality 1 line at a time....