WHMCS IIS7 and DNP

[pod]

Does anyone here have WHMCS running on IIS7 32bit or 64bit and provisioning sites using DNP (DotNetPanel)?

[Onionman]

Yep- IIS 7.5 on 2008 R2(so x64), what problems you having?

[dila12v]

Yes, same as above, IIS 7.5 on 2008 R2 (x64) with DNP 2.8.11.

 

It was a bit troublesome getting it all working initially, but once we got going it's been fine since.

 

First problem with WHMCS 4.0 on a new server was the PHP memory limit wasn't high enough for the NUSOAP extension that WHMCS uses.

 

Next problem was with the default permissions that DNP assigns web folders. In the DNP file manager, the web user had to be assigned read permissions to the parent web folder. This issue was preventing WHMCS connecting to the database, so we got a database connection failed error.

 

After that there was a problem with WHMCS not creating DNP accounts. There was a problem with some of the module options we had ticked. It now works with the two summary email options, the create mail account option and the HTML email option all removed. Can't remember which in particular was causing a problem, but one or more needed further configuration within DNP to work.

 

Last problem was after upgrading to WHMCS 4.1.1, there was also an issue with the NUSOAP extension and WHMCS provided an update for this file which sorted it.

[pod]

well we have two whmcs systems, one was already running on this IIS7 / 64bit using php 5.2.9 and fastcgi. This first whmcs site only provisions helm v3. so all was good.

 

then we migrated over our primary whmcs which provisions helm v3 and dnp. Well helm v3 works but we are getting this exception below whenever we do something with dnp or when the billing cron runs and it needs to do something with a dnp customer. We are running v4.0.2.

 

So did any of you run into this issue?

 

Faulting application php-cgi.exe, version 5.2.12.12, time stamp 0x4b291183, faulting module ioncube_loader_win_5.2.dll, version 0.0.0.0, time stamp 0x49ac1910, exception code 0xc0000005, fault offset 0x00004f84, process id 0xd3c, application start time 0x01ca9af22f5cd0c7.

[pod]

What memory limit had you been using. We use the recommended php 128m

[pod]

Guys - never mind..... Of course the docs for dnp and whmcs forget to tell you to turn off php_soap.dll in the extensions. Once we commented that out, its working like a charm.

 

I would like to know another question we just upgraded from v2.8.9 to 2.8.11 and we always had the whmcs option to create the email accounts.

That worked in v2.8.9, but with 2.8.11 when creating a new site from whmcs we get: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Exception: Could not create mail account ---> System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> Could not get mail domain ---> Unable to connect to the remote server ---> No connection could be made because the target machine actively refused it 127.0.0.1:9998 at

 

Note: If we uncheck the email option everything runs fine now. Also manually creating email accounts from within dnp works. Can anyone confirm?

Edited January 22, 2010 by pod

[ODH]

Our company is considering using WHMCS and from what I understand in this thread...

 

Its tough to configure and integrate but once that challenge is completed... it works well. Until the next patch/update is release?

[pod]

getting whmcs to run on iis7 was easy. its just that the docs in the wiki, forget to tell you to disable the php_soap.dll.