I think that this box should make the differentiation a bit clearer on the "(local)" connection.

 

2.  Thanks - fix request information submitted.  will be in next service pack.

 

3. I've seen this behaviour (i.e. the autoclosing) when you do a V4 import, and straight after that, but that is the only time.  I'll give some more upgrade installs a go and see if I can cause this again.   I'll get the text changed for this to something more useful.

 

4.  The default is with the most common of the two at the moment - probably a change to a non-commital *.log would be best for the default log files mask here, as it will cover both.  I've submitted the change request for this also.

 

 

5.  as far as I can tell this is fixed in the latest build - from my tests, tabbing from the "Default User Name" field tabbed into the "Password" box.

 

 

Thanks again for your comments.

 

 

 

The Remote Access form  of the New site Wizard has a majorly screwed up tab order.  I tab out of Default User Name and focus does not move to the very next field, it jumps to the Next button.  It gets worse after that.  It's almost funny.

 

Here are a few of the many bugs I went on about previously, as I run into them again and again.

 

1. When the "Connect to WhosOn Server" first runs after install, the "Server Name Or IP Address field is set by default to my server's sole IP address, but it does not work.  I get:

Not Connected To WhosOn

[10061] Connection refused

Bug.

 

I figured out that I have to change it by manually selecting (local).  But, it is extra fun that everytime something goes wrong in the WhosOn Administrator, including dialog boxes, it crashes/vanishes, and I have to start all over.  Bug.

 

2. The Configure Db Wizard has a field for "Database Path", which is populated with "C:\ProgramData\Parker Software\WhosOnV5\".  I don't want db files on my Windows drive, and nobody should put them there.  Fine, I'll change it.  Wait, no I won't.  The field is enabled/unlocked, but cannot be changed.  Why?  Apparently the MaxLen is too short for any realistic path name.  Bug.

 

I'm clever, I'll manually drill into the path using the "..." common dialog button.

3.  I then get a prompt telling me that I need to restart the WhosOn Administrator.  I click "Okay".  I click "Finish", and WhosOn crashes/vanishes.  I did not get to restart it.  You stuck me with a restart at the time of your choosing.  This ^@!*ing thing vanishes every other click.  It's not fun anymore.  Bug.  The message should have said: "We won't tell you exactly when, but somtime in your next several clicks, we're going to close WhosOn, and you have to start it again, and again, and again."

 

4. The New Site Wizard has an incorrect Log File Mask for IIS 7 (the current version).  It uses "ex*.log", but IIS 7 uses "u_ex*.log".  Bug.

 

Okay, 4 main bugs with a few sub bugs in about 3 minutes of trying to use WhosOn (minus all the time relaunching it after in vanishes 7 times).  I've had enough for one day.

 

 

WebUsername=Admin
WebPassword=

 

Yeah, that's what I was trying, but it does not work!  Bug.

 

Okay, I'm game, I'll try the Settings.ini in a V4 folder.  Hey, those credentials work.  What in the world?  My credentials for V5 are stored in the V4 settings?  Seriously?  This is a mess.

 

Now the server is magically working, despite crashing yesterday.  When will it crash again?  Who knows.

 

The WhosOn client on the server seems to work fine, but I don't need there.  The client on my remote machine, where I actually need it, is just a sea of blank whiteness.  How do I make the sites, which should be showing up, show up?

 

Your lack of awareness of all the bugs does not make them any less frustrating.

 

Yes, v-e-r-y latest builds.  Sever = Windows Server 2008 Web Edition.  Client = XP Pro SP3.  Both have all of the very latest service packs and updates.

 

Now, when I relaunch the WhosOn Administrator (server) the default connection credentials don't work, so I'm locked out of trying to fix the broken thing.  I did not knowingly change any credentials.

 

Have I mentioned that this sucks?  I like WhosOn when it's working, but this is ridiculous.

 

You didn't get a notification because in your forum settings "notify me of replies to posts" is set to no.

 

I'm not aware of all these bugs in the installer you go on about previously.   If you get error messages in the installer about OCX or DLLs then the service will not run. 

 

Are you using all the latest builds of clients and server downloads?  What OS are you trying to install the server on to?

 

Contact the sales department for a refund.

 

 

I never got a notification of your reply.  I guess there's a bug with that, too.

 

I manually cleaned up what your V5 so-called uninstaller left behind.  I ran into all of the same bugs during install.  I got V5 installed despite all the bugs.  I try to start the service and the app crashes.

 

One last effort, I try to install the client on another machine, and I get:

---------------------------
WhosOn Client
---------------------------
Error

 

Sincerely disappointed,

Lee

 

I'm ready to give this one more try.  If I run into more bugs, I'd just like to get a refund.

 

, Lee

 

Now that I've wasted an hour and a half on what should have been a 10-minute upgrade, how do I get WhosOn 5 to ask me about importing my version 4 settings again?  One of the many bugs in the installer screwed me out of importing.

 

Of course every time I come here to ask for help, the stupid forum makes me re-register, because my account cannot be found!

 

So frigging annoyed and wanting my time back,

Lee