Cproxy patch 3 6 5

Comment 1 arhak Credit Attribution: arhak commented March 8, 2010 at 1:48am subscribing Log in or register to post comments Comment 2 roball Credit Attribution: roball commented March 9, 2010 at 9:18am Category:bug» feature File Size drupal-6.15+16_proxy_server_support.patch6.47 KB FAILED: [ Simple Test]: [ My SQL] Unable to apply patch drupal-6.15+16_proxy_server_support.patch. View I am sorry, but I just found that the patch posted above does NOT apply cleanly to D6.16. Thus, I am re-posting the original patch for D6.15 which works fine for both 6.15 + 6.16. Use this one instead! Log in or register to post comments Comment 3 dswan Credit Attribution: dswan commented March 8, 2010 at 5:41pm Category:feature» bug This does not seem to work for me on a freshly patched 6.15 install - no additional site configuration options become available using patch from 2 patch [ New] 198 L, 6625 C writtenuser@host:~/public_html$ patch -p0 < patch patching file includes/common.inc patching file modules/system/system.admin.inc patching file modules/system/system.module So the patch was applied just fine. no joy. Tried a couple of times on a couple of installations - I really need this feature. Log in or register to post comments Comment 4 arhak Credit Attribution: arhak commented March 8, 2010 at 6:18pm @ 3 did you cleared the cache? I think it might need a menu rebuild Log in or register to post comments Comment 5 Slim Pickens Credit Attribution: Slim Pickens commented March 9, 2010 at 12:41am subscribe Log in or register to post comments Comment 6 mmilo Credit Attribution: mmilo commented March 10, 2010 at 11:53pm Category:feature» bug subscribing Log in or register to post comments Comment 7 jjkd Credit Attribution: jjkd commented March 12, 2010 at 7:38pm I successfully installed this patch on Drupal 6.14 (with no patch issues). Cleared cache, I was then able to configure the proxy server.
In our previous blog post, we provided you with advice for troubleshooting Microsoft Office 365 Pro Plus login and activation issues. We wanted to share some advanced troubleshooting techniques from Microsoft Support Engineer Keith Cronsell. If you turn on logging while troubleshooting as issue, don’t forget to turn it off after you have resolved the problem. Troubleshooting Authentication/ Sign-in/ Activation Errors The following steps will enable logging.  Once you have logging enabled, you should try to compare a “working” attempt against a “non-working” attempt to compare the results. Set the following regkey to enable TCOTrace logs. To do this, launch cmd as administrator and run the following command: reg add HKCU\ SOFTWARE\ Microsoft\ Office.0\ Common\ Debug /v TCOTrace /t REG_ DWORD /d 1 /f Then try the activation process again from the Sign- In screen. Once the error occurs collect the following: Collect logs from %temp% Office.log .exe.log (where is the name of the application used for the Sign- In attempt, for example, Excel.exe.log or Winword.exe.log) Remove the regkey added.  To do this, launch cmd as administrator and run the following command: reg delete HKCU\ SOFTWARE\ Microsoft\ Office.0\ Common\ Debug /v TCOTrace /f Troubleshooting Office 365 Install/ Update Failures The following steps show you how to enable verbose logging to help you troubleshooting Office 365 install/update failures. To enable verbose logging, launch cmd as administrator and run the following command: reg add HKLM\ SOFTWARE\ Microsoft\ Click To Run\ Over Ride /v Log Level /t REG_ DWORD /d 3 ULS log file is created both in the %temp% folder and the %windir%\temp folder.  The file name is of the following format: --.log For example Keith.log.  Once these logs have been retrieved and analyzed, verbose logging should be disabled by running.
BACKGROUND AND PURPOSE Running Office 365 together with web proxy is supported and also the reality for many (or most) global Enterprise customers. Moving to Office 365 with web proxy present in your landscape is related to a number of considerations and possible configuration steps in order to ensure the best possible performance and functionality. Guidelines for customers using web proxy do exist in the Office 365 Service Description and Deployment Guide. However, the information is scattered between different articles, why it can be unclear for the solution architect or network administrator to get a clear view on the considerations and principles that apply when using web proxy with Office 365. The purpose of this article is to collect the available information (plus some notes from the field) in one place to form an assembly on the given topic. THE CLOUD AND WEB PROXY – WHAT COULD POSSIBLY GO WRONG? Having a web proxy and running cloud based services might seem like the perfect fit. “ The service is on the Internet, and our web proxy accelerates the Internet traffic to our end users web browsers – what could possibly go wrong?”. There is no general answer to what could go wrong - it depends on what Office 365 services you plan to enable, and also what type of web proxy you are using. But, to give an idea, here are five examples of things that might break when deploying Office 365 behind web proxy without first taking the right precautions:  Office Pro Plus Click-2- Run installation fails with the reason: “ Something went wrong – Sorry, we ran into a problem.” ( Explained here). Outlook might lose it’s Connection to the Exchange server intermittently. A “balloon message” in the lower right explains “ The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.” Downloading files from Share Point Online takes an.