I have in one site a server release 5 on windows 2000, running on the same machine as the IIS, with the websphere plugin installed and running smoothly for more then a year with no problems.
This one is the last server release 5, so we are planning to upgrade it to release 6.53FP1 and windows 2003. The new server is already installed in a separate network for tests, but I can’t manage to work with the IIS as the previous release did.
The problems are very strange, and I did all the instructions from the release notes, and the white papers from IBM, and a few suggestions from the forum as well. I have tryed using the WAS4 and WAS5, where the WAS5 isn’t working at all. I did all the changes in the windows registry, notes.ini and IIS as instructed.
The bottom line is not working. sometimes it just doesn’t work, and sometimes the whole IIS stop responding. When IIS stop responding I have to restart the service, and it works up to the first time someone open the site. It opens BUT the IIS stop responding. I have no clue. Can someone spot some light to help me upgrade this server?
I have in one site a server release 5 on windows 2000, running on the same machine as the IIS, with the websphere plugin installed and running smoothly for more then a year with no problems.
This one is the last server release 5, so we are planning to upgrade it to release 6.53FP1 and windows 2003. The new server is already installed in a separate network for tests, but I can’t manage to work with the IIS as the previous release did.
The problems are very strange, and I did all the instructions from the release notes, and the white papers from IBM, and a few suggestions from the forum as well. I have tryed using the WAS4 and WAS5, where the WAS5 isn’t working at all. I did all the changes in the windows registry, notes.ini and IIS as instructed.
The bottom line is not working. sometimes it just doesn’t work, and sometimes the whole IIS stop responding. When IIS stop responding I have to restart the service, and it works up to the first time someone open the site. It opens BUT the IIS stop responding. I have no clue. Can someone spot some light to help me upgrade this server?
The whole stuff is not working. When we point a browser to the IIS (which have 8 sites running) there is no problem. But when we try to open an nsf file the whole IIS stop responding imediately.
All the configuration seems to be OK, I have the green sign in the plugin.
No messages in the windows event viewer, nor in the domino. Just the all IIS stucked. Restarting the service will work, but when the first nsf is reached the whole server stop responding again.
There are some known problems with Domino/IIS in this upgrade scenario. One of the problems is that when a browser request contains .nsf, IIS crashes. This is caused by old metadata that is left in IIS. The metadata is related to the ISAPI filter, but even removing and adding the ISAPI filter back won’t remove these old metatdata entries. You’ll have to run MetaEdit to remove this old metadata stuff, as far as it pertains to the Domino ISAPI filter. Here’s a Microsoft technote that has more on MetaEdit:http://support.microsoft.com/default.aspx?scid=kb;en-us;240225
If you are using version 5 of the plugin you’ll need to update the reg key entry to use 5.0.0.0 instead of the setting 4.0 you would have had for version 4.
If you are using windows 2003 and IIS6, you’ll need to ensure that you have created a new web service extension for the dll and set it allowed. (There’s an IBM support note on this)
When I did the test with version 5 of the plugin, I did all the changes in registry and I did created a server extension as in the documentation. But it didn’t worked out.
I will give another try later on today to double check it.