Techsavy
asked on
SharePoint help
Hi,
We have a custom application, that we want the users be able to directly from SharePoint. Just like the Office documents. The custom mime type has been registered in the IIS and the necessary changes to docicon.xml have been made.
So, the issue is, when a user tries to open the application from SharePoint, it shows following error message. Same application opens fine on a different server.
The only difference is the server where this is not working is SSL enabled. am i missing any specific setting on the server that is preventing this?
"The document could not open for editing. A Windows SharePoint Services 3.0 compatible application could not be found."
Any help is greatly appreciated.
We have a custom application, that we want the users be able to directly from SharePoint. Just like the Office documents. The custom mime type has been registered in the IIS and the necessary changes to docicon.xml have been made.
So, the issue is, when a user tries to open the application from SharePoint, it shows following error message. Same application opens fine on a different server.
The only difference is the server where this is not working is SSL enabled. am i missing any specific setting on the server that is preventing this?
"The document could not open for editing. A Windows SharePoint Services 3.0 compatible application could not be found."
Any help is greatly appreciated.
Minesh Shah
depends on what custom application and how did you embdeded into sharepoint & how are you accessing it from sharepoint.
ASKER
The application has a similar packaging structure as office documents, and we save these files in a document library. So, nice thing is WSS is recognizing the applications' icon, which means mime-type have been correctly registered. So, the point is now when we right-click our application file in SharePoint and say "Edit in our custom application" we get the above error. We do not get this error on a server, where we dont have a fully qualified domain name.
Also, some additional information: The server where this is not working has a fully qualified domain name and has ssl enabled.
Let me know if you need any additional information, I will continue to debug.
Thanks for the help.
Also, some additional information: The server where this is not working has a fully qualified domain name and has ssl enabled.
Let me know if you need any additional information, I will continue to debug.
Thanks for the help.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi Andre,
Your solution seems to work fine in the case where this error is seen with office documents. But in this case, all office documents work within SharePoint context with no error.
thanks for the suggestion.
Your solution seems to work fine in the case where this error is seen with office documents. But in this case, all office documents work within SharePoint context with no error.
thanks for the suggestion.
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.