Same problem - default site is up and running, can register users, email workin - but EVERY module in Admin menu gets a "Selected Module does not Exist" - so i can't even configure Xoops...

Doesn't appear to be a domain issue - the URL looks fine??? It's gotta be something simple here???? - Windows 2003 server - IIS - PHP 4.3.3 - Plesk 6.5 for the hosting config - virtual host C:/inetpub/vhosts/domain... for the XOOPS dir

(I KNOW I KNOW - everybody will say change to Redhat & Apache but that's not an option for me right now - please help somebody must have got this working on Win2003 IIS, etc. etc.. and ran into the same problem...)

I use Windows 2003 Server and IIS 6, works a treat. Can you take a screen pic at all? I'm assuming that it is under the modules listing in the module admin section that this error is coming up? I have seen this com up when the modules directory structure isn't copied to the server properly.

I guess I could take a screenshot but really no need - there's no error message.... basically, login works no prob. User registration works no prob. But login with admin access, then click on Administration - mouse over system admin then anything in that menu click on and get "selected module does not exist" - example - "Banners" module - points to ...../modules/system/admin.php?fct=banners seems correct to me.

Checked the modules files all look fine. Virtual host so all files are in c:\inetpub\vhosts\domainname.com\httpdocs\) where domainname.com = whatever domain - i'm trying to set up a few XOOPS sites. DNS not an issue. Modules are in c:\inetpub\vhosts\domainname.com\httpdocs\modules\ all look fine to me:
06/04/2004 03:16 AM <DIR> .
06/04/2004 03:16 AM <DIR> ..
06/04/2004 03:15 AM <DIR> contact
06/04/2004 03:15 AM 33 index.html
06/04/2004 03:15 AM <DIR> mydownloads
06/04/2004 03:15 AM <DIR> mylinks
06/04/2004 03:15 AM <DIR> newbb
06/04/2004 03:16 AM <DIR> news
06/04/2004 03:16 AM <DIR> sections
06/04/2004 03:16 AM <DIR> system
06/04/2004 03:16 AM <DIR> xoopsfaq
06/04/2004 03:16 AM <DIR> xoopsheadline
06/04/2004 03:16 AM <DIR> xoopsmembers
06/04/2004 03:16 AM <DIR> xoopspartners
06/04/2004 03:16 AM <DIR> xoopspoll
1 File(s) 33 bytes

Any special PHP config or IIS settings you had to change when you installed your config?

Sorry if this has beem covered before, but it might be worth double checking that your IUSR_MACHINENAME account has at least NTFS read permissions to all directories and files under your XOOPS root. It will also need NTFS write permissions to the cache, template_c and upload directories. You may need to force an update of permissions by selecting the "reset permissions on all child objects" from under the advanced button in your security properties window.

Yeah played with that - actually set the IUSER_MACHINENAME account to have full control of everything from root on down. LOL I know I know - I'll fix the perms once I get this working - just wanted to make sure that wasn't an issue.

Anyway - with NTFS full control to internet guest account - still get the same - Selected module does not exist on all modules under system admin...

WHat about IIS permissions?

Gah, wrong thread! lol *ignore me*

Not quite sure i follow you on the IIS permissions... IUSR_MACHINENAME has complete access to all of the root XOOPS files + DIR... IIS is set up to use that account for guests ??? There's an IWAN_MACHINENAME account - not sure if that's what you're talking about - changed it's permissions for those folders/files and no go.... still same. Can you elaborate on the IIS permissions?

EDIT: btw brash - nice website I see yours is running fine - that's 2003 server with IIS 6 right? I'm on 4.3.3 PHP what's yours? Also my box is config'd using Plesk 6.5 hope that doesn't be an issue.

Thanks for the comment on my site gman . Yep, I use Windows 2003 Enterprise Server using IIS 6, PHP 4.3.3 and MySQL 4.017-nt. The IWAN_MACHINENAME account is used for out of process functions, so won't be needed here. By IIS permissions I meant the settings from under the home directory tab of your website properties, however I'm 99.99% they would be right if you have gotten as far as you have. The most likely reason I can think of for getting the error you are is if the path to your system module folder is different from what XOOPS is expecting. Under your XOOPS root you should have something like;

\modules\system\

and under system there should be 5 directories called admin, blocks, images, language and templates. There also should also be about half a dozen other files.

I tend to agree that all files/settings are correct but it might not be passing the right directory/path info through php. Doublechecked all files/etc and everything look a.o.k.

What's the easiest way to debug this? i.e. turn on some logging to see what the server is trying to pass to that common.php or whatever when it gets the module does not exist error?