Forum Discussion

cmarkovits's avatar
cmarkovits
Level 4
14 years ago

Searcho2k.asp Page malformed

Hello,

We just completed a disaster recovery test using the Symantec 'Building Blocks' method, and are currently running our Enterprise Vault Services out of our respective DR centers.  Most issues are ironed out, however the Searcho2k.asp page on our DR / standby servers appears to be malformed.  More specifically, when a customer loads the https://<Server_Alias>/EnterpriseVault/Searcho2k.asp page, normally it would display just the Find dialog box.  Ours shows the Advanced Find (along with a bunch of misplaced buttons and text on the screen) at the top, and the normal Find dialog box at the bottom.  Obviously it doesn't look good, but more importantly it is confusing the users.  Any ideas???  Very odd behavior....  Thanks!

-Corey

  • I think the reason is because your working server is EV9 SP1, your fail over server is EV9 base


    Working
    /EnterpriseVault/V9.0.1.1073/en/Dialog.css

    Not Working
    /EnterpriseVault/V9.0.0.1193/en/Dialog.css

     

    Reinstall the EV9 SP1 binaries

    Edit: pipped to the post by 38 seconds :)

  • Tony, thanks for the response!  Actually, this issue is for Outlook, not the Web Browser (even though the Searcho2k.asp page is really a web browser window inside Outlook).  So just to be clear, customers using Outlook are clicking on the Search Archive button on the EV Toolbar in Outlook, and getting this malformed Searcho2k.asp page...

    I did some further checking.  Turns out that the Searcho2k.asp page is working just fine on all of the origional servers (Tested by copying the URL out and just replacing the server name to point back to the old / origional servers from before the failover).  The servers that we failed over too however all display this malformed page.  So it's not clear to me why this is the case.  They are all running 9.0 SP1.  Any ideas?

    For what it's worth, the Search.asp page (The one you were referring too) does come up correctly on all the servers...

    Thanks!

  • Have you compared the files between your working and DR sites?

    Have you compared the IIS logs (particularly around the number of bytes returned, etc) ?

  • How about copying over a good search.asp file to a server that shows the wrong page, and try that?

  • Rob,

       I compared the searcho2k.asp files both in size, as well as in content.  Both were 58 KB, and I used TexpPad to compare the actuall contents to confirm that they were exactly the same, which they were. I didn't think to look at the IIS logs (as obvious as that is!) since the files checked out.  So in looking at the IIS Logs now, I do see some differences in the IIS Logs. Here is a copy of the sanitized logs...

     /// Logs from Searcho2k.asp that DOES work! ///
    #Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status time-taken
    2011-02-01 14:38:59 <PRODUCTION_IP_ADDRESS> GET /EnterpriseVault/Searcho2k.asp - 443 - <CLIENT_IP_ADDRESS> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+InfoPath.2;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+MS-RTC+LM+8) 401 2 5 0
    2011-02-01 14:38:59 <PRODUCTION_IP_ADDRESS> GET /EnterpriseVault/Searcho2k.asp - 443 <COMAIN\USER_Name> <CLIENT_IP_ADDRESS> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+InfoPath.2;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+MS-RTC+LM+8) 200 0 0 62
    2011-02-01 14:38:59 <PRODUCTION_IP_ADDRESS> GET /EnterpriseVault/V9.0.1.1073/en/Dialog.css - 443 - <CLIENT_IP_ADDRESS> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+InfoPath.2;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+MS-RTC+LM+8) 200 0 0 0
    2011-02-01 14:38:59 <PRODUCTION_IP_ADDRESS> GET /EnterpriseVault/dialog.js - 443 - <CLIENT_IP_ADDRESS> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+InfoPath.2;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+MS-RTC+LM+8) 200 0 0 0
    2011-02-01 14:38:59 <PRODUCTION_IP_ADDRESS> GET /EnterpriseVault/V9.0.1.1073/en/images/AdvancedSearchIcon.gif - 443 - <CLIENT_IP_ADDRESS> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+InfoPath.2;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+MS-RTC+LM+8) 200 0 0 93
    2011-02-01 14:38:59 <PRODUCTION_IP_ADDRESS> GET /EnterpriseVault/V9.0.1.1073/en/images/glass.gif - 443 - <CLIENT_IP_ADDRESS> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+InfoPath.2;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+MS-RTC+LM+8) 200 0 0 109
    2011-02-01 14:38:59 <PRODUCTION_IP_ADDRESS> GET /EnterpriseVault/V9.0.1.1073/en/images/powered_by.gif - 443 - <CLIENT_IP_ADDRESS> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+InfoPath.2;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+MS-RTC+LM+8) 200 0 0 187
    
    /// Logs from Searcho2k.asp that is MALFORMED ///
    #Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status time-taken
    2011-02-01 14:31:02 <RECOVERY_IP_ADDRESS> GET /EnterpriseVault/searcho2k.asp - 443 - <CLIENT_IP_ADDRESS> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+InfoPath.2;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+MS-RTC+LM+8) 401 2 5 0
    2011-02-01 14:31:02 <RECOVERY_IP_ADDRESS> GET /EnterpriseVault/searcho2k.asp - 443 <COMAIN\USER_Name> <CLIENT_IP_ADDRESS> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+InfoPath.2;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+MS-RTC+LM+8) 200 0 0 218
    2011-02-01 14:31:02 <RECOVERY_IP_ADDRESS> GET /EnterpriseVault/V9.0.0.1193/en/Dialog.css - 443 - <CLIENT_IP_ADDRESS> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+InfoPath.2;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+MS-RTC+LM+8) 404 0 2 0
    2011-02-01 14:31:03 <RECOVERY_IP_ADDRESS> GET /EnterpriseVault/V9.0.0.1193/en/images/AdvancedSearchIcon.gif - 443 - <CLIENT_IP_ADDRESS> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+InfoPath.2;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+MS-RTC+LM+8) 404 0 2 0
    2011-02-01 14:31:03 <RECOVERY_IP_ADDRESS> GET /EnterpriseVault/V9.0.0.1193/en/images/powered_by.gif - 443 - <CLIENT_IP_ADDRESS> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+InfoPath.2;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+MS-RTC+LM+8) 404 0 2 15 

    So, if I'm not mistaken, it looks like it might be having problems with the "/EnterpriseVault/V9.0.0.1193/en/Dialog.css" file???

  • GertjanA,

    Thanks for the suggestion.  See my response to Tony's comments above (just posted).  I did try copying the file over even though it was identical.  I think Tony is on to something.  The IIS logs show that there might be an issue with the Dialog.css files maybe?  Not sure...  Thanks.

    Corey

  • I just realized that it looks like we have some sort of version mis-match.  We did install EV 9.0 SP1 on everything, but it apepars that in looking at the IIS logs a little closer that they are not exactly at the same build level, which obviously is an issue, and very well could be the cause of this problem (not sure yet).  Just throwing that out.  It _looks_ like we aren't running SP1 on our DR servers like we _thought_ we were.  Guessing that a re-install of SP1 might do the trick?  Any thoughts?

  • I think the reason is because your working server is EV9 SP1, your fail over server is EV9 base


    Working
    /EnterpriseVault/V9.0.1.1073/en/Dialog.css

    Not Working
    /EnterpriseVault/V9.0.0.1193/en/Dialog.css

     

    Reinstall the EV9 SP1 binaries

    Edit: pipped to the post by 38 seconds :)

  • All, So it was the version mis-match after all.  We are still not sure how we wound up with this, but obviously something slipped throught he cracks in the last upgrade.  Regardless reinstalling the 9.0.1 binnaries resolved the issue.  Clients needed to have thier cache cleared and Outlook restarted.  Thanks!