Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
iwproxy_isapi.dll not loading
Paul
We are using TeamSite 6.1 SP2 on a windows2003 server and the iwproxy_isapi.dll will not load properly (we get a red arrow pointing down) and when we try and preview any page it comes up blank. The page previews ok (sort of) if we don't enable the iwproxy_isapi.dll but Server Side includes will not review unless they are at the same level or below the page that they are included in. Has anyone else experienced this and possibly figured out how to overcome it?
Find more posts tagged with
Comments
kailash1
Try uninstalling and reinstalling SP2. This might help. Also if you have another box test with previous version of ISAPI dll.
Regards
Kailash
new_report.rptdesign
Paul
Have tried both and still the iwproxy_isapi.dll will not load. We have it loading and working on a test server and the settings are exactly the same for each server.
I have tried enabling the iw_isapi logging but the log file won't even generate because the filter never loads. I have tried using the iwproxy_isapi.dll off of the machine that is working and it still won't load.
Paul
In trying to troubleshoot this issue we put the tsimp_ ID in the administrator group and the iwproxy_isapi.dll loads properly and we are able to view pages and SSI properly. However, we should NOT have to put tsimp in the admin group and our security guys will NOT allow us to do this on the production box. It appears to be a permissions issue but I am at my wits end trying to figure out where to look or what to change.
Paul
Migrateduser
Does you iw-home have read permissions for everyone. The very first time we every installed Teamsite our admins locked done everything including the kitchen sink.
Read this knowledge base article for correct info about setting permissions.
https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=53298
You may need to setup Teamsite on a second new server without them touching the permissions, then have them go and apply whatever settings they want so that they can see how their settings are breaking the server. This is what we had to do to convince our admins to change the permissions to what was needed.
masterpage.jpg