Technology at Geneseo Community School District 228
Occasionally the Webspeed powered web side of Skyward will take a crash and users will be greeted with a message that simply says service not available. Logging into the server itself you will see generic error messages relating to the wsisa.dll and some executable files attempt to use it. Simply restarting IIS will fix this error and only takes a minute but the issue can still be annoying. If you are running Server 2003 you may find that the wsisa.dll executable file is prone to memory leaks and after heavy usage or given enough time it will crash. Without extensive debugging to find the exact source of the memory leak there is an easier fix which is simply to use. cgiip.exe instead of wsisa.dll.
You can do this by simply chaning the link
Notice that just past the word scripts I simply change wsisa.dll to cgiip.exe. Both files can be used interchangeably and performance should be about the same, however I have found that cgiip.exe is more stable. If you are running Server 2008 and IIS 7.0 (7.5) the wsisa.dll file has been improved and this should not be a concern. This fix seems to only apply for Server 2003 using IIS 6 and Webspeed.
If you are set on using wsisa.dll you can also set a scheduled task to reset the webserver once a day perhaps at 3Am, this should also keep skyward running and reset any memory leaks. To do this create a batch file and place this command
Schedule a task to run this batch daily at a set time. You could also do both switch to cgiip.exe and do schedule a daily reset which should keep the service running 99.9% of the time.
By default Server 2008 does not use a NTP Time Server to sync its clock but relies only on the internal clock. If this server also houses VM images through Hyper V these images will by default pull time info from the host. To me I have always like to have clocks synced to a NTP time server which just gives peace of mind that all machines, VM’s, etc will have the correct time. This prevents issues with clients accessing resources or logging in being denied due to Kerberos or other time sensitive security measures.
Personally I have find this strange that there is not a simple GUI button to check to to enable this, the fix though is easy enough. My instructions below will cause Server 2008 to use the time.windows.com NTP server for time syncing.
To Set Server 2008 to use a NTP Time Server in 3 easy steps.
1. Edit the Registry (regedit)
2. Now change these three registry keys
(You are changing this from a 10 to a 5 )
(Again change the contents of this key to simply NTP)
(This is by default a 0 you are changing to a 1).
3. Last step open a command prompt with administrative access.
Net stop w32time
Net start w32time
I did find a windows support on this topic but it is a bit lengthly http://support.microsoft.com/kb/816042