Are you using ActiveStates Perl?  

If so, what version and are you using it (Perl) as PerlISAPI or with a shebang line?

Otherwise - what Perl are you using???

Thanks

sausagenet wrote on Jun 12^th, 2012 at 12:51pm:

Considering the alternatives here, including my lack of any real knowledge about using a Windows server, I think your best course of action might be to again try a brand new install.

I admire your persistence.  

By the way, I have the same problem as you do, but on a UNIX server. Like you, I've followed YaBB's instructions to the letter, and I still have the same related problem that you have.

I'm beginning to think that both you and I may have installed a corrupted download of YaBB. I'm just reaching, but that is a possibility.

Maybe someone here with "actual substantial knowledge" can download YaBB's current YaBB 2.5 and do what will be for them a quick install to see if something's gotten corrupted.

Edited:


***************************************

JonB wrote on Jun 12^th, 2012 at 12:49pm:

Ironically, if you look at my track record of helping people here in this forum, I seem to be able to help them even when people with knowledge about a subject aren't able to provide a solution. Go figure. I think it has to do more with trying than actually knowing what to do.

Also, I think it helps to have a fresh set of eyes on a problem from a regular user versus an expert who often can't see the forest because of the trees. I know that it's not uncommon for an expert to clue in on a solution after they've read through help that I've tried to give.

It's like, "No, no, no, Bill. That's not the way to do it. This is the way to do it."

How someone helps shouldn't matter if that help provides a solution to any given problem, or it leads to a solution. So far, even a qualified expert like you can't seem to figure out what the real problem is. So neither one of us is helping much here; at least not yet.

So how are we different here?

If it makes you feel any better, my money's on you since you actually have substantial knowledge, and as I've already qualified the help I've been trying to give, I do not.

In any case, give a guy a break for trying to help. You're seriously complaining about that?

Since it was asked - I have a zipped copy of 2.5AE dated 6/21/11 (1635 kb zipped) and just now unzipped it, FTPed the files and directories to my Linux test site into cgi-bin/yabber, set the permissions on YaBB.pl, AdminIndex.pl and Setup.pl to 755, everything else is 644.

No problems. The hosting service is Knownhost.
Perl 5.8.8, Apache 2.2.16, unspecified Linux version.

The known issues with YaBB and Perl 5.10 are non-fatal warnings concerning some out-dated syntax. These warnings should not effect the install.

So, if you think you need a verified-as-good zipped file of 2.5AE, I have one.

Unfortunately, I don't have a 2.4 forum to transfer member or message files from to check if there's a complicating issue there.

And yes, I know this is not a Win server solution.  

Set Paths.pl to writable using IIS manager

I'm glad you are making progress.  

If the URL of the new installation is the same as the old one:  you might want to flush your browser cache (the objects will have the same names)

Actually, I was just thinking... can I have the beta of Yabb Next Edition and I can run that?  Look smuch nicer and you'll get a production forum with live feedback?  My forum is 9 years old, and has 100s of 1000s of message, and 1000s of legacy users, but less than 100 actives now - I'm sure they wouldn't mind

sausagenet wrote on Jun 12^th, 2012 at 9:15pm:

Excellent!

***************************************

Dandello wrote on Jun 12^th, 2012 at 6:36pm:

Thank you so much to going to the trouble to verify that the installation package works perfectly fine.
You've inspired me to give it another try.  

But not today ... had a really long one, and I'm having a hard time staying awake.

I'm very pleased that Ian's installation issues seem to pretty much be behind him. He seems to have figured out what was going on all on his own. Excellent!

So for anyone else who may have the same issues, "The key to the whole thing was windows rights in the cgi directory (nothing to do with IIS rights)."

This is actually very helpful for me as well even though I'm on a UNIX machine. Thanks Ian!

More clues to ponder while I get a good night's sleep.  

2 Questions:

Did you test posting before you brought over the data?

Can you post in the converted forum?

Thanks