ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Fresh Install on Windows Server - php errors galore!

September 15, 2011 5:08pm

Subscribe [4]
  • #1 / Sep 15, 2011 5:08pm

    Stephen Callender

    148 posts

    Hello,

    So, I’ve read just about every post on here having to do with EE installs on Windows Servers. I’m experienced with EE on Linux. I have direct access to the server and the permissions are all set properly (I’ve been able to upload photos and completed the install properly, etc).

    I have one permanent php error that shows on every CP page.

    A PHP Error was encountered
    Severity: Notice
    Message: Undefined offset: 1
    Filename: accessories/acc.expressionengine_info.php
    Line Number: 113

    Plus a laundry list of php errors appearing on the CP homepage. (I’ll put the first 4 of out 71. No lie.)

    A PHP Error was encountered
    Severity: Notice
    Message: Undefined offset: 2
    Filename: cp/homepage.php
    Line Number: 279
    
    A PHP Error was encountered
    Severity: Notice
    Message: Undefined offset: 1
    Filename: cp/homepage.php
    Line Number: 290
    
    A PHP Error was encountered
    Severity: Notice
    Message: Undefined offset: 2
    Filename: cp/homepage.php
    Line Number: 279
    
    A PHP Error was encountered
    Severity: Notice
    Message: Undefined offset: 1
    Filename: cp/homepage.php
    Line Number: 290

    The last error shows on the CP homepage, as well.

    A PHP Error was encountered
    Severity: Warning
    Message: Cannot modify header information - headers already sent by (output started at D:\Web Sites\...\...\system\codeigniter\system\core\Exceptions.php:170)
    Filename: core/Common.php
    Line Number: 405

    I wish I could go to a Linux server, but the client owns this Windows server and wants to build on it. *Sigh*

    I am building on EE 2.1.3. However, the same errors showed when I tested with EE 2.2.2, so that’s not the issue.

    Help is much appreciated!

  • #2 / Sep 16, 2011 2:48am

    John Henry Donovan

    12339 posts

    sjc80,

    Can you give our Server Wizard a go and make sure the Windows server meets all these requirements please

  • #3 / Sep 16, 2011 9:37am

    Stephen Callender

    148 posts

    Hi John,
    I have done that. It meets all the requirements. The only thing it doesn’t meet is the URL Segment Support.

    I removed the EE accessory and that took away the first error. I redirected log in page to Structure, so that took away the next two, but I’d still like to be error-less when the client stumbles upon the CP homepage at some point.

  • #4 / Sep 16, 2011 9:46am

    Sue Crocker

    26054 posts

    Hmmm… if you take Structure out of the equation entirely, does that make a difference?

  • #5 / Sep 16, 2011 9:48am

    Stephen Callender

    148 posts

    Hi Sue,
    I added Structure after the errors so I could redirect the log in to it. So, unfortunately no. The issue pre-existed Structure. Do I still get coverage? 😊

  • #6 / Sep 16, 2011 10:09am

    Sue Crocker

    26054 posts

    Well, I don’t have a Windows install to test against with the Agile theme to see if I see the same errors you do.

    Who are you hosting with?

  • #7 / Sep 16, 2011 10:11am

    Stephen Callender

    148 posts

    The company who I’m building the site for has their own Windows 2003 RD server. It’s been a pain (10 hours of troubleshooting for permissions). This is now my only problem.

  • #8 / Sep 16, 2011 10:12am

    Stephen Callender

    148 posts

    You think it’s a theme issue?

  • #9 / Sep 16, 2011 10:20am

    Sue Crocker

    26054 posts

    No real idea.. can you create a new 2.2.2 install on that box with the Agile Records and see if that has problems?

  • #10 / Sep 16, 2011 10:44am

    Stephen Callender

    148 posts

    Just installed EE 2.2.2 with Agile Records and the exact same errors appear on the CP Home.

  • #11 / Sep 19, 2011 6:05pm

    Kevin Smith

    4784 posts

    Hi sjc80,

    Be on the lookout for an email from me. Since I don’t have a Windows server to test against, I’d like to get a first-hand look at the issues you’re experiencing.

  • #12 / Sep 21, 2011 4:18pm

    Kevin Smith

    4784 posts

    Hi sjc80,

    Is there any change your host is using a proxy server to route traffic from the web server to another website? The reason EE is having offset issues is because it can’t parse the response it gets when trying to check with expressionengine.com to find out the latest version of EE. It gets this response:

    Redirect (authentication_redirect_to_virtual_host)

    You are being redirected to the authentication virtual host.

    For assistance, contact your network support team.

    In searching this error message on Google, the results I got all seemed to point to the use of a proxy server causing a blockage between the two sites.

    Could you check with your host to see if this is the case?

  • #13 / Sep 21, 2011 5:22pm

    Stephen Callender

    148 posts

    Hi Kevin,
    That makes a lot of sense. I have direct access to the virtual server, because it’s a small business that owns it. They don’t have a clue how to operate it. I’d probably have to be the one to figure it out, which probably won’t happen soon.

    Is there a way to turn off version checking? Or some other fix from within EE?

  • #14 / Sep 21, 2011 5:41pm

    Stephen Callender

    148 posts

    Hi Kevin,

    If the client is assigned as an editor or to some other member group, the version checking won’t process/appear for them, so the errors don’t show to non-SuperAdmins. I’m cool with that. The client won’t be a SuperAdmin and they won’t know the difference!

    The issue is still there, but that’s okay since I know the work around. Consider this closed unless you want to resolve it from an EE perspective.

    Thanks.

  • #15 / Sep 22, 2011 12:52pm

    Kevin Smith

    4784 posts

    Thanks for the update. The error response on EE’s side could fail more gracefully, so I’ll make sure the devs are aware of that. Other than that, there’s not much we can do on the EE side. I’ll consider this resolved as well. Thanks for bringing it to our attention!

    If you do end up coming up with something, feel free to open up a new related thread to share it with us and the community!

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases