Try to sign the wiki with the ID of the server which runs it. Since 8.5.1 it seems all XPages require this. This is btw annoying if you replicate it to another server which should be used if the normal server fails, because it could only have the signature of one server at the same time, which also means on one server it produces that error.



Knows anybody a solution to this?

I just started playing with Dom 8.5.1 and installed a cpl of test servers on my Macs (in boot camp and vmware). Here are some of the issues I ran into, and this may be of help to you..

1. On my default test install it made the hostname: CL-Win7.hsd1.ca.comcast.net
   
   I changed this to CL-Win7 in the server document so that the wiki would allow me to edit documents on the web.
   
   
   
2. The hosts file on windows 7 is located in c:\Windows\System32\Drivers\etc\hosts. You can just go to the start menu and search programs and files for hosts and it will turn up. After modifying it and adding:
   
   
   
   127.0.0.1 localhost
   
   127.0.0.1 CL-Win7
   
   
   
   If you just dbl click on the hosts file to edit it, you will NOT be able to save changes as it is in a Windows protected directory. The way to edit it is to bring up notepad on the Windows Start menu and right click on it and choose "Run as Administrator". Then open the hosts file in it and you will be able to save into the protected directories.
   
   
   
3. Small Modifications to my notes ini
   
   
   
   Changed From:
   
   $$HasLanPort = 1
   
   Ports = TCPIP, Lan3
   
   Disabled Ports = (was missing Lan3, I added it)
   
   
   
   To:
   
   $$HasLanPort = 0
   
   Ports = TCPIP
   
   Disabled Ports = (was missing Lan3, I added it)
   
   
   
4. Cpl more changes to server config document:
   
   In Ports section removed:
   
   Port: Lan3
   
   Protocol: NetBIOS
   
   NotesNetwork: Network
   
   Net Address: CL-Win7
   
   
   
5. In the server doc you have to go to the security tab and put the user id (Administrator in my test) into the field "sign or run unrestriected methods and operations" and also in "sign agents or xPages to run on behalf of the invoker"
   
   
   
6. Also, in designer, open the application properties and go to the xPages tab and tick "Display default error page", this will give useful error messages if xpages fail because of a server side script.
   
   
   
   I'm new to Win7 as well as Dom 8.5.1 so anyway, the above are the changes I went thru to work with xsp's.