Office 2013 - Something went wrong (no kidding)

New x64 machine running Office Home & Business 2013 x86 OEM.
Originally, everything was running fine. Installed fine, set up fine, and ran fine. Inexplicibally, user calls stating when running ANY office app, it states "Something went wrong" and would not open (computer was only a few days old, no other
mods/installations).
Tried:
Online Quick Repair (same error)
Online Full Repar (same error)
Removal of product via KB2739501 (removed fine, now won't install)
Now product is removed. Ran FixIt KB2739501 twice and even removed Office folders in programs dir. When attempting to run ClickToRun installer, i get "Something went wrong". Really?
Tried x86 and x64 ClickToRun, no dice. Currently downloading the insanely massive offiline installer (because for some reason MS bundled x86 and x64 together... totally bright), but don't have any faith. User has been without Office apps for days. Scouring
net notes MS has a recognized issue with the installer process and licensing, but various fixes that worked for others, doesn't work here.
Any thoughts?
Thanks,
Jeremy

Hi,
The first step I suggest is to start Office Apps in Safe Mode, check if the crash will happen.
Let's take Outlook for example:
Press Win + R and type “outlook.exe /safe” in the blank box, then press Enter.
If there’s no problem in Safe Mode, disable the suspicious add-ins to verify which add-ins caused this issue.
If the issue persists in Safe Mode, please go to the Event Viewer, you may find out more information about why the Office apps crashed.
Press Win + R and type "eventvwr" in the blank box, then press Enter.
You may learn from http://www.msoutlook.info/question/317
If now you can't install Office properly, please refer to the KB below:
Office 2013 or Office 365 installation error "Something went wrong"
http://support.microsoft.com/kb/2827031/en-us
Try Fix it in the kb to try again.
Thanks,
Melon Chen
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Similar Messages

  • Outlook 2013 something went wrong sorry we ran into a problem

    my outlook started hanging and causing problems a few days ago where sent messages were sitting in outbox without sending. and when you closed and reopened outlook the messages has vanished completely without sending. I'm unable to get outlook
    to open.  I keep getting the message something went wrong sorry we ran into a problem. All other office 2013 programs will function correctly. I have also tried to open the control panel/mail (outlook 2013) (32 bit) icon, but this pauses
    for a while and then brings up no window to configure an account. I managed to get my exchange account set up in the mail app but I'm not interested in using the mail app when i should be able to utilize all the functionality of outlook.
    I have spent a couple days reading all the posts and tried uninstalling office 2013 pro and the mail app thinking i'd clean install the 64-bit version of office but to no avail. Looks like the preloaded office 13 cannot be uninstalled, so I then
    downloaded the O15CTRRemove tool which worked in removing office 2013, but did not fix the problem of outlook not opening. This is driving me crazy and I have tried many suggestions from the online forums, and have got outlook to open a couple of times where
    it was then asking for a product key, and when the key was entered outlook would close straight away and not allow it to open again. I have tried running the repair tool many times, and this does not work. Every other program I have had zero issues with; autocad, 
    adobe suite, everything runs perfect. I just want to get my outlook all set up.Please advise!

    Hi,
    Please check whether you can send message in OWA. If there is no issue in OWA, it should be an Outlook issue. It seems that there is just one user encontered this issue in your environment. If so, please start Outlook in safe mode by using "Outlook /safe"
    in Run windows to check whether the issue persists. If it fails, please change a computer to try again.
    Thanks,
    Winnie Liang
    TechNet Community Support

  • OWA Exchange 2013: Something went wrong error

    Getting this error on event log for owa. when we log in to owa, error shows :"something went wrong" 500
    tried to recreated owa virtua directories and webconfig file but same issue, please help.
    Event code: 3008
    Event message: A configuration error has occurred.
    Event time: 15/9/2014 11:05:36 PM
    Event time (UTC): 15/9/2014 3:05:36 PM
    Event ID: ec79c7b2c1ef4b95adbb445c80939fc4
    Event sequence: 1
    Event occurrence: 1
    Event detail code: 0
    Application information:
        Application domain: /LM/W3SVC/2/ROOT/owa-45-130552671349946251
        Trust level: Full
        Application Virtual Path: /owa
        Application Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\
        Machine name: LBVSMX01
    Process information:
        Process ID: 17484
        Process name: w3wp.exe
        Account name: NT AUTHORITY\SYSTEM
    Exception information:
        Exception type: ConfigurationErrorsException
        Exception message: Could not load file or assembly 'Microsoft.Exchange.Flighting, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. (C:\Program Files\Microsoft\Exchange
    Server\V15\ClientAccess\Owa\web.config line 117)
       at System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective)
       at System.Web.Configuration.AssemblyInfo.get_AssemblyInternal()
       at System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig)
       at System.Web.Compilation.BuildManager.CallPreStartInitMethods(String preStartInitListPath, Boolean& isRefAssemblyLoaded)
       at System.Web.Compilation.BuildManager.ExecutePreAppStart()
       at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException)
    Could not load file or assembly 'Microsoft.Exchange.Flighting, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
       at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection,
    Boolean suppressSecurityChecks)
       at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection,
    Boolean suppressSecurityChecks)
       at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection)
       at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
       at System.Reflection.Assembly.Load(String assemblyString)
       at System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective)
    Request information:
        Request URL: https://localhost:444/owa/exhealth.check
        Request path: /owa/exhealth.check
        User host address: ::1
        User:  
        Is authenticated: False
        Authentication Type:  
        Thread account name: NT AUTHORITY\SYSTEM
    Thread information:
        Thread ID: 42
        Thread account name: NT AUTHORITY\SYSTEM
        Is impersonating: False
        Stack trace:    at System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective)
       at System.Web.Configuration.AssemblyInfo.get_AssemblyInternal()
       at System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig)
       at System.Web.Compilation.BuildManager.CallPreStartInitMethods(String preStartInitListPath, Boolean& isRefAssemblyLoaded)
       at System.Web.Compilation.BuildManager.ExecutePreAppStart()
       at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException)
    Custom event details:
            

    no they are not shared mailboxes.
    here are the logs.
    Not sure if this will make any difference, but there are 2 domains on exchange one is mail.domain1.com and another is webmail.domain.com
    we have added another owa virtual directory for the second domain when we were having issues but i think since we are having a problem on the first domain owa, the second one will have the same.
    just wondering why ecp can still work when owa doesnt. outlook clients can connect and so are phones.
    #Software: Microsoft Internet Information Services 8.5
    #Version: 1.0
    #Date: 2014-09-15 10:10:56
    #Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) cs(Referer) sc-status sc-substatus sc-win32-status time-taken
    2014-09-15 10:10:56 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.75 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 2 1531
    2014-09-15 10:10:56 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.75 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 2 15
    2014-09-15 10:11:02 192.168.1.44 HEAD /OAB/391e4f87-9e04-4176-aa12-bb90e3d8596c/oab.xml - 443 - 172.17.0.70 Microsoft+BITS/7.5 - 404 0 2 249
    2014-09-15 10:11:15 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 62
    2014-09-15 10:11:15 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 15
    2014-09-15 10:11:15 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 15
    2014-09-15 10:11:15 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 0
    2014-09-15 10:11:26 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 14
    2014-09-15 10:11:26 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 15
    2014-09-15 10:11:26 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 15
    2014-09-15 10:11:26 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 0
    2014-09-15 10:11:51 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.70 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
    2014-09-15 10:11:51 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.70 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
    2014-09-15 10:11:51 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.70 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
    2014-09-15 10:11:51 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.70 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 0
    2014-09-15 10:11:51 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.75 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 2 15
    2014-09-15 10:11:51 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.75 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 2 15
    2014-09-15 10:11:51 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.80 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 0
    2014-09-15 10:11:51 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.80 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
    2014-09-15 10:11:51 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.80 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 0
    2014-09-15 10:11:51 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.80 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
    2014-09-15 10:11:53 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.84 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
    2014-09-15 10:11:53 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.84 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
    2014-09-15 10:11:53 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.84 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
    2014-09-15 10:11:53 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.84 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
    2014-09-15 10:12:31 192.168.1.44 GET /owa &ActID=d0e541bb-2726-473a-9891-74afd643bd53&CorrelationID=<empty> 443 - 192.168.1.17 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+rv:30.0)+Gecko/20100101+Firefox/30.0 - 401 2 5 22905
    2014-09-15 10:13:08 192.168.1.44 GET /ecp/ - 443 - 192.168.0.6 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko - 400 0 0 10240
    2014-09-15 10:13:28 192.168.1.44 POST /Microsoft-Server-ActiveSync User=andrew.solis2&DeviceId=ApplC38LTUR3FRC5&DeviceType=iPhone&Cmd=Ping 443 - 172.16.0.33 Apple-iPhone6C2/1102.55400001 - 404 0 2 0
    2014-09-15 10:13:31 192.168.1.44 GET /ecp/ - 443 - 192.168.0.6 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko - 400 0 0 15
    2014-09-15 10:13:38 192.168.1.44 GET /ecp/ - 443 - 192.168.0.6 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko - 400 0 0 15
    2014-09-15 10:13:40 192.168.1.44 GET /ecp/ - 443 - 192.168.0.6 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko - 400 0 0 15
    2014-09-15 10:13:40 192.168.1.44 GET /ecp/15.0.995.28/themes/default/clear1x1.gif - 443 - 192.168.0.6 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko https://webmail.domain.com.sg/ecp/ 400 0 0 78
    2014-09-15 10:13:40 192.168.1.44 GET /ecp/15.0.995.28/themes/default/main_default.css - 443 - 192.168.0.6 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko https://webmail.domain.com.sg/ecp/ 400 0 0 109
    2014-09-15 10:15:51 192.168.1.44 HEAD /OAB/391e4f87-9e04-4176-aa12-bb90e3d8596c/oab.xml - 443 - 172.17.0.76 Microsoft+BITS/7.5 - 404 0 2 218
    2014-09-15 10:15:55 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.76 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
    2014-09-15 10:15:55 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.76 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
    2014-09-15 10:15:55 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.76 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
    2014-09-15 10:15:55 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.76 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 0
    2014-09-15 10:16:26 192.168.1.44 HEAD /OAB/391e4f87-9e04-4176-aa12-bb90e3d8596c/oab.xml - 443 - 172.17.0.70 Microsoft+BITS/7.5 - 404 0 2 203
    2014-09-15 10:16:44 192.168.1.44 HEAD /OAB/391e4f87-9e04-4176-aa12-bb90e3d8596c/oab.xml - 443 - 172.17.0.70 Microsoft+BITS/7.5 - 404 0 2 218
    2014-09-15 10:16:56 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.75 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 2 15
    2014-09-15 10:16:56 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.75 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 2 15
    2014-09-15 10:17:07 192.168.1.44 HEAD /OAB/391e4f87-9e04-4176-aa12-bb90e3d8596c/oab.xml - 443 - 172.17.0.70 Microsoft+BITS/7.5 - 404 0 2 218
    2014-09-15 10:17:38 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.97 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6425;+Pro) - 404 0 2 0
    2014-09-15 10:17:38 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.97 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6425;+Pro) - 404 0 2 0
    2014-09-15 10:18:48 192.168.1.44 GET /owa &ActID=5c208db7-3a44-43d0-b5d8-24f107542a81&CorrelationID=<empty> 443 - 192.168.1.44 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko - 401 2 5 0
    2014-09-15 10:20:51 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.76 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 2 15
    2014-09-15 10:20:51 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.76 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 2 15
    2014-09-15 10:20:52 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 31
    2014-09-15 10:20:52 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 15
    2014-09-15 10:20:52 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 15
    2014-09-15 10:20:52 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 0
    2014-09-15 10:21:19 192.168.1.44 HEAD /OAB/391e4f87-9e04-4176-aa12-bb90e3d8596c/oab.xml - 443 - 172.17.0.107 Microsoft+BITS/7.5 - 404 0 2 218
    2014-09-15 10:25:04 192.168.1.44 HEAD /OAB/391e4f87-9e04-4176-aa12-bb90e3d8596c/oab.xml - 443 - 172.17.0.190 Microsoft+BITS/7.5 - 404 0 2 218
    2014-09-15 10:25:22 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.190 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
    2014-09-15 10:25:22 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.190 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
    2014-09-15 10:25:22 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.190 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 0
    2014-09-15 10:25:22 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.190 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
    2014-09-15 10:25:40 192.168.1.44 HEAD /OAB/391e4f87-9e04-4176-aa12-bb90e3d8596c/oab.xml - 443 - 172.17.0.190 Microsoft+BITS/7.5 - 404 0 2 203
    2014-09-15 10:25:54 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.76 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 2 0
    2014-09-15 10:25:54 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.76 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 2 15
    2014-09-15 10:27:16 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.65 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6213;+Pro) - 404 0 2 15
    2014-09-15 10:27:22 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.65 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6213;+Pro) - 404 0 2 15
    2014-09-15 10:27:25 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.65 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6213;+Pro) - 404 0 2 15
    2014-09-15 10:28:22 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.81 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.6023;+Pro) - 404 0 2 15
    2014-09-15 10:28:41 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.81 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.6023;+Pro) - 404 0 2 15
    2014-09-15 10:29:20 192.168.1.44 HEAD /OAB/391e4f87-9e04-4176-aa12-bb90e3d8596c/oab.xml - 443 - 172.17.0.107 Microsoft+BITS/7.5 - 404 0 2 203
    2014-09-15 10:29:45 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.107 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
    2014-09-15 10:29:45 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.107 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
    2014-09-15 10:29:45 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.107 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
    2014-09-15 10:29:45 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.107 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 0
    2014-09-15 10:31:40 192.168.1.44 GET /owa/ &ActID=cdc5aa77-7e17-4a56-83ed-2e7047c12c5b&CorrelationID=<empty> 443 - 172.17.0.198 Mozilla/5.0+(Windows+NT+6.1;+WOW64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/37.0.2062.120+Safari/537.36
    https://webmail.domain.com.sg/owa/auth/logon.aspx?replaceCurrent=1&url=https%3a%2f%2fwebmail.domain.com.sg%2fowa 401 2 5 16
    2014-09-15 10:32:00 192.168.1.44 GET / - 80 - 172.17.0.198 Mozilla/5.0+(Windows+NT+6.1;+WOW64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/37.0.2062.120+Safari/537.36 - 200 0 0 31
    2014-09-15 10:32:00 192.168.1.44 GET /iis-85.png - 80 - 172.17.0.198 Mozilla/5.0+(Windows+NT+6.1;+WOW64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/37.0.2062.120+Safari/537.36 http://webmail.domain.com/ 200 0 0 265

  • Help, I can't sign in to Visual Studio Community 2013 "Something went wrong and we can't sign you in right now. Please try again later."

    Hi, can anyone help me further diagnose?
    On Windows 7 64-bit, whenever I try to sign into Visual Studio Community 2013 I get a bunch of clicking sounds, and then  "Something went wrong and we can't sign you in right now. Please try again later."
    I installed the 2013 update 4 just recently (3/23)
    I was getting this error back in February

    Hi HuggyPaul,
    Thank you for posting in MSND forum.
    >>whenever I try to sign into Visual Studio Community 2013 I get a bunch of clicking sounds, and then  "Something went wrong and we can't sign you in right now. Please try again later."
    Based on your issue, I suggest you could try to use an another microsoft live-in user account to sign in the Visual Studio Community 2013 to check if you can sign in the VS2013 Community with update 4.
    Or you could try to use same user account to sing same version of VS2013 Communty with Update 4 on other machien and the check if you can sign in this VS 2013 Community with update 4.
    (1)If you could sign in the VS2013 Community update4 by the another user account on your machien, I think that the issue maybe related to your user account.
    (2)If you still could not sign in VS 2013 Community update 4, maybe you will need to repair or re-install this VS2013 Community with update 4.
    In addition, please tell me what browser you use on your machine.
    If your machien just insatall other browser such as chrome, please try to install the IE and then check this issue again.
    From this error message, i find a similar thread about your issue, maybe it can help you.
    Referenece:
    https://social.msdn.microsoft.com/Forums/vstudio/en-US/49a611c6-cf70-4756-932c-1e26edddd9a1/something-went-wrong-and-we-cant-sign-you-in-right-now?forum=reportabug
    Best Regards,
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Sorry, something went wrong and Word was unable to start (6) Office 2013

    Ok this is just so annoying.
    Whenever I try to open Word, it gives the error "Sorry, something went wrong and Word was unable to start.(6)". Other office applications either freeze or crash. Only Excel works fine. Running Win7 64 bit.
    Tried all possible ways of installation/reinstallation. Did repair, uninstalled and reinstalled manually, uninstalled with FixIt from Microsoft, removed every leftover thing from registry. Also removed some other applications that I thought could cause this
    problem for Office. 
    Uninstalled 64 bit Office, and installed 32 bit, same exact problems.
    !!!Don't suggest me to run as administrator please!!!

    Hi,
    According to your description, I suppose that Word 2013 was blocked by some other applications after you opening it.
    Which operation system do you use?  Have you installed the Office 2013 SP1?
    Then, we try to do some tests to narrow down the issue:
    1. Collect the Event log
    http://windows.microsoft.com/en-us/windows/what-information-event-logs-event-viewer#1TC=windows-7
    2. Use the
    Process Monitor to collect the detailed information.
    Open process monitor, and reproduce this issue, if there is any files or keys were blocked during the process.Please let me know,  and you could save as the file from process monitor, upload the file through One Drive and share the link to me. I'll
    analysis it.
    Regards,
    George Zhao
    TechNet Community Support

  • Exchange 2013 - OWA "Something Went Wrong", Out of office in Outlook "Server unavailable"

    Hi,
    We have a new deployment of Exchange 2013 CU2 V2 running on a Windows 2012 server.  Everything has been running without issues and then without any real clue to why, we are now getting an issue where OWA says "Something Went Wrong" after processing
    your login, (it appears to process the login as if I type in incorrect details it tells me the password/username is wrong).
    At the same time we have also lost the ability to run the Out Of Office in Outlook which comes back saying the server is not available and we can't seem to share calendars correctly either.  (Can set Out Of Office via the Management Shell without issues).
    When running a Get-Serverhealth on the OWA.Protocol it tells me the OWASelfTestMonitor is unhealthy.
    I've tried re-creating the OWA, EWS Virtual Directorys and also the autodiscover but with no effect.  I've also restarted the server. 
    Outlook 2013 and mobile phones are working fine on the server and the Exchange Admin Centre is also working without issues.
    I am getting tempted to apply CU2 again to see if this sorts it but don't really like doing this on a server with 50 live users on it...
    In the eventlog I can see lots of the 2 errors listed below which seems to line up.  (System Log and Application Log seem to be clear of other errors or warnings.)
    Event code: 3005
    Event message: An unhandled exception has occurred.
    Event time: 04/11/2013 11:25:00
    Event time (UTC): 04/11/2013 11:25:00
    Event ID: 2fcdb9112c794b63a9ea9577a23e4603
    Event sequence: 2
    Event occurrence: 1
    Event detail code: 0
    Application information:
        Application domain: /LM/W3SVC/2/ROOT/owa-411-130280378905273269
        Trust level: Full
        Application Virtual Path: /owa
        Application Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\
        Machine name: SERVERNAME (I altered this for post) 
    Process information:
        Process ID: 9648
        Process name: w3wp.exe
        Account name: NT AUTHORITY\SYSTEM
    Exception information:
        Exception type: HttpException
        Exception message: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.
    Lots more code.......
    AND
    Event code: 3005
    Event message: An unhandled exception has occurred.
    Event time: 04/11/2013 11:24:24
    Event time (UTC): 04/11/2013 11:24:24
    Event ID: 2586a044b2d74b97a1095aec478bf4ae
    Event sequence: 2
    Event occurrence: 1
    Event detail code: 0
    Application information:
        Application domain: /LM/W3SVC/2/ROOT/EWS-668-130280378564324526
        Trust level: Full
        Application Virtual Path: /EWS
        Application Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\exchweb\EWS\
        Machine name: SERVERNAME (I have changed this for post) 
    Process information:
        Process ID: 9840
        Process name: w3wp.exe
        Account name: NT AUTHORITY\SYSTEM
    Exception information:
        Exception type: HttpException
    Exception message: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.
    lots more data...

    Hi Angela,
    I can't see any re-directions on the website and have certainly not set any intentionally.  I did try installing the Remote Web Gateway on the server and then found that it doesn't work on an exchange box and removed it but the server was working after
    this.
    The HTTP Redirect in Default Web Site is not showing anything set and the same for the Back End.
    The bindings on the default site all look normal with;
    http     80   127.0.0.1
    https   443  127.0.0.1
    http     80    *
    http    443   *
    The same is mirrored in the Exchange Back End site but with ports 81 and 444.
    Running the Outlook auto configure just using Autodiscover all looks good with the URLs listed all pointing to (http)://mail.mydomain.co.uk/whatever...  and the log says Autodiscover to (https)://mail.mydomain.co.uk/Autodiscover/Autodiscover.xml Suceeded
    (0x00000000)
    But, if I type in the OOF address of (https)://mail.mydomain.co.uk/EWS/exchange.asmx I get a login prompt but once user details are entered I then get;
    '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.
      Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
     Exception Details: System.Xml.XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.
    Source Error:
     An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. 
    Stack Trace:
    [XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.]
       System.Xml.XmlTextReaderImpl.Throw(String res, String[] args) +163
       System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace() +7572550
       System.Xml.XmlTextReaderImpl.ParseDocumentContent() +62
       System.Xml.XmlReader.ReadToFollowing(String name) +112
       Microsoft.Exchange.Data.ApplicationLogic.Extension.KillBitHelper.ReadKillBitXmlContent(XmlReader reader, Int32& refreshRate) +185
       Microsoft.Exchange.Data.ApplicationLogic.Extension.KillBitHelper.TryReadKillBitFile(Int32& refreshRate, DateTime& lastModifiedTime) +710
       Microsoft.Exchange.Data.ApplicationLogic.Extension.KillBitTimer.Start() +202
       Microsoft.Exchange.Services.Global.Application_Start(Object sender, EventArgs e) +975
    [HttpException (0x80004005): '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.]
       System.Web.HttpApplicationFactory.EnsureAppStartCalledForIntegratedMode(HttpContext context, HttpApplication app) +12864205
       System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +175
       System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +304
       System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +404
       System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +475
    [HttpException (0x80004005): '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.]
       System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +12880948
       System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +159
       System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +12722137
    Really wishing I had installed Exchange 2010 at this point!!  Just can't see why its not working :(

  • Office Web Apps Issue - "Sorry, something went wrong" message when opening a document (any MS docx,ppt etc) in IE. With Chrome, it pops (Microsoft Office needs your permission) message and on RUN, it opens the document.

    When opening any Microsoft documents ( docx, ppt etc) in SharePoint 2013,
    Internet Explorer behavior : "Sorry, something went wrong" An unexpected error has occurred message and then nothing happens. 
    In Chrome : Pops (Microsoft Office needs your permission) message and on clicking RUN, it opens the document.
    In Firefox : the documents opens, after asking which application do you want to use to open it.
    The feature (Open Documents in Client Applications by Default) is not activate.
    Why the MS documents are not working in IE 10?

    Hi,
    According to your post, my understanding is that you failed to open Microsoft documents in SharePoint 2013.
    I recommend to Run the following PowerShell in OWA Server :
    Remove-OfficeWebAppsHost # To Remove any restriction
    Or
    New-OfficeWebAppsHost -Domain <String> # To allow specific domain Name
    In addition, you can allow OAuth via HTTP using the following commands:
    $config = (Get-SPSecurityTokenServiceConfig)
    $config.AllowOAuthOverHttp = $true
    $config.Update()
    Here are two similar articles for you to take a look at:
    http://blogs.msdn.com/b/fabdulwahab/archive/2013/10/30/office-web-apps-with-sharepoint-2013-issues.aspx
    http://stevemannspath.blogspot.in/2013/03/sharepoint-2013-office-web-apps-issue.html
    Best Regards,
    Linda Li
    Linda Li
    TechNet Community Support

  • PowerPoint 2013 - We're sorry something went wrong...

    We've recently upgraded to Office 2013 Professional Plus from Office 2010. Our Workstations are Windows
    7 x64 SP1 and this issue is happening on freshly built machines and established installs.
    When a limited user creates a new presentation, launches Slide Show, right clicks and tries to access the "Pointer
    Options" to annotate the slide with a pen or highlighter, they receive the following error and no annotations:
    "We're sorry something went wrong that might make PowerPoint unstable. Please save your presentations and restart PowerPoint"
    This error doesn't appear as an Administrator, so its probably a permissions issue . It also happens on existing opened presentations.
    Office 2013 has been repaired and re-installed without resolving the issue.
    I've tried troubleshooting with Process Monitor to see what files the user doesn't have access to but have come up a blank. There is nothing obvious in the Application or System event logs either. Any other ideas?
    I hope someone can help,
    Cheers
    Tom

    Hi Tom,
    Please try to right-click on Microsoft PowerPoint within your start menu and select "Properties" then navigate to the "Compatibility" tab. Tick the box before "Run this program in compatibility
    for:" and select "Windows 7" from the drop list. Restart PowerPoint to check the result.
    We can also try to open PowerPoint in safe mode to check if this issue is related to problematic add-in. To do this, hold
    Ctrl key when you double-click to open the presentation.
    In addition, some people report that they are able to work around this issue by opening the original presentation and then saving it as a .ppt file (not a .pptx), you may check if it works.
    Please let me know the result.
    Regards,
    Steve Fan
    Forum Support
    Come back and mark the replies as answers if they help and unmark them if they provide no help.
    If you have any feedback on our support, please click
    here

  • PowerPoint 2013 - We're sorry something went wrong that might make PowerPoint Unstable

    Windows 7 running Office 2013. Mature installation no recent changes.
    Simple update to ppt file created in 2003 ( using Compatibility mode). Single user edit saving to my documents 
    Error Message "We're sorry something went wrong that might make PowerPoint Unstable" / "Please save your presentations and restart PowerPoint"
    PowerPoint no longer allows me to save any file in any format without this message.
    Actions taken : Restart PowerPoint / Reboots / Deletion of temporary files from C:/Windows/Temp
    Problem persists

    I had this problem with Win81, PowerPoint 2013, pptx file, no system/software changes or updates that could be blamed. Out of the blue working on an existing document, messages as OP wrote started plaguing PPT. Brand new pptx files created with benign random
    text also suffered from this. A save or two within the first 30 seconds of opening or creating the file sometimes went ok, but problem appears inevitably - implicating file lock issue.
    There is remarkably little commonality in resolutions of this on the web, and no resolution from MS. 
    Tried many of the suggestions that can be found - no joy.
    Finally isolated this to the live sync on DropBox.  If DropBox is active (immediately syncing changes in the background), the problem persists. If DropBox is paused, the problem ceases. DropBox does not need to be removed or exited. If unpaused, problem
    immediately starts again. Have not been able to check if other syncing cloud drives have same effect.
    What's disturbing is that the DropBox/PowerPoint combination on this machine has been working fine for 1+ years. Turning off DropBox is not an acceptable solution. Perhaps a silent update of one or the other occurred to cause this. 

  • Project Server 2013 : Edit "In Browser" more than 500 line throws "An unexpected error occurred" Error, something went wrong.

    Dear Experts,
    I have got Project Server 2013. These projects are migrated from 2007 to 2010 and to 2013. All the functionality working fine as expected, But few schedule got more than 500 lines of Task, We are unable to "Edit" those projects "In Browser".
    We have tried in both IE and Chrome, When you try Edit it throws error "Something went wrong, I checked the co relation Id in the logs. I get the below,
    02/09/2015 15:08:32.84
    w3wp.exe (0x16D8)
    0x04EC 0xB217023
    ahjqp High
    [Forced due to logging gap, cached @ 02/09/2015 15:08:32.70, Original Level: Verbose] SQL connection time: 0.0809460420248942
    75f5e79c-783e-a090-5f32-f52e977a9b62
    [Forced due to logging gap, cached @ 02/09/2015 15:08:32.85, Original Level: Verbose] The SecurityTokenServiceHeaderInfo including the correlation ID was added.
    Batch request was created without a batch name, specify a batch name for better telemetry. 
        at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo) 
        at System.Environment.get_StackTrace() 
        at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal.GetSqlBatchRequest(String batchName) .....
    [Forced due to logging gap, cached @ 02/09/2015 15:08:33.89, Original Level: VerboseEx] PWA:, ServiceApp:Project Server Service Application... 
    the above error repeated more than 100 times
    Same thing goes to the below error also
    Entering Function=TTaskTable::GetElemProp   DynamicLogging triggered SessionID = {EE8AD295-E5AD-E411-943A-005056A95E5E}
    Leaving Function=TTaskTable::GetElemProp returning HRESULT:8C010003 SessionID = {EE8AD295-E5AD-E411-943A-005056A95E5E}I really appreciate and thank for
    the support. Thanks
    Jacob Michael

    Hi Jacob,
    Have you tried re-publishing the projects from MS Project and see if that helps?
    500 tasks are quite a lot for the browser to deal with; I usually recommend switching to MS Project when you have that number of tasks for a project
    Paul

  • MS Word 2013 unable to start. "Sorry, something went wrong and word was unable to start. (6)

    I am trying to open MS Word 2013. I have purchased the MS Office online and pay a subscription. When opening MS Word, it comes up with the error message "Sorry, something went wrong and word was unable to start. (6)" This appears to be happening
    with all MS office applications. Can someone please help? 

    I faced this same problem and reinstalled office several times but no luck, then followed below steps and got my issue resolved:
    Solution is that you run word in "Administrative" mode:
    To run the Word program in administrator mode, try the step below:
    · go to Computer, Programs files/Program files X (86).
    · Look for Microsoft Office ->Office 15.
    · Look for Winword.exe
    · Right click on it and click
    Properties
    · Click on the Compatibility tab
    and check the box forRun as admin.
    · Clickok.
    Ref: http://answers.microsoft.com/en-us/office/forum/office_2013_release-word/unable-to-open-word-sorry-something-went-wrong-and/aa080850-1fe3-46b5-8338-905633e8f9a0

  • Sorry, something went wrong - Open Office File from Search Results Page with Office Web Apps

    Hi,
    I'm getting "Sorry, something went wrong" error when I'm trying to open any office document from inside Search Results Page with Office Web Apps, the same error is appearing in the document preview as well.
    The error in SharePoint logs says that the file cannot be found.
    Please note that this error is coming only when the "Filename" of the document is not written in English (in my case its written with Arabic characters).
    If I try to open it from the document library, its opening properly with no errors.
    The only difference between two URLs (document URL in Search Results and in Document Library) is the value for "sourcedoc" attribute;
    In the case of Search Results page, the filename in "sourcedoc" attribute is kept as is with Arabic characters.
    While in the Document Library, the filename in "sourcedoc" attribute is converted into different characters (something like: "B9%D9%85%D9%8").
    Anybody have an idea on how to overcome this issue, implement a workaround or modify the "sourcedoc" behavior?
    Thanks in Advance.
    Hamza AlSughier

    Dear Wendy,
    Thanks for your efforts, I already tried your last suggestion before, but this didn't solve my problem.
    Actually my end users are accessing this portal using ADFS and HTTPS.
    Finally I got this solved, I have done below to get my overall solution working perfectly:
    - First I have configured Windows Authentication and ADFS Authentication on the same zone which is the default zone.
    - The issue when opening office documents with Arabic file name has disappeared as a result of first change.
    - Then I have faced an issue where we are not able to crawl content under Default zone, however we have to do so, after too many efforts, I found that its related to the Load-balancer/proxy, I have made the crawler server
    to crawl himself (http://CrawlServerName:PortNumber).
    - Also a change on Alternate Access Mapping was needed, I have set one of the extended zones (which is running Windows Authentication only) as Internal URL for the Default Zone, and this is was the URL I used for Crawling.
    I have configured Server Name Mappings to make sure we got proper URLs in Search Results.
    - Then we faced another issue, which is Authentication selection on login page (How to bypass this page, and authenticate using ADFS auto), I used this solution (Set Custom Sign In Page):
    http://0ut0ftheb0x.wordpress.com/2014/01/04/skip-the-authentication-selection-page-at-_logindefault-aspx-in-a-mixed-authentication-environment/.
    - I faced one more issue as a result of above workaround; Sign Out functionality wasn't working well; users get logged in automatically whenever I click on Sign Out. I solved this by modifying the "Sign Out" Control under _layouts;
    I made it to redirect users to ADFS Sign Out Page instead of SharePoint Sign Out Page (I know its not recommended, but I don't have any other option).
    Hamza AlSughier

  • Sharepoint 2013 foundation central admin "something went wrong"

    I recently installed SP1 (the bad version before it was pulled) on my SharePoint 2013 foundation server. I ran psconfig and made sure my databases were up to date after SP1. I checked central admin after psconfig and everything was working and good to
    go. I have little need to access it on a regular basis, so after the install I haven't attempted to access central admin for approximately a month. As the updated SP1 just hit a few days ago I attempted to pop into CA to does some work on the site in preparation,
    and I received the sorry something went wrong message. I thought it may be an issue due to the bad version of sp1 that was installed and/or high ram utilization. As this is a standalone box in production I could not reboot easily. I was finally able to do
    the install last night, and it appears the problem is still ongoing. The site has been in production for about 6 months now, I have never had any issues hitting CA previously. SharePoint is running as a VM, and we have decked the specs out for it. We are allocating
    4 cores and 24gb of ram to the site, and we are not seeing anything close to max resource utilization on the hypervisor or on SharePoint. I checked the correlation ID that SharePoint provides in the ULS logs and the only thing close to an error I get is a
    message "cannot find site lookup info for request uri
    http://localhost:<port binding>/." this is followed by "Application error when access /, Error=Exception of type 'System.ArgumentException' was thrown.". I'm exporting a copy of the vhd to experiment on in a test environment now, so
    I will update this if I get more info. I don't think this was caused by SP1 as I was able to hit the CA page after doing the upgrade, but other than standard users interacting with the site since SP1, there have been no changes from an administration perspective.
    I am the only one who touches the site here so I know changes weren't made without my knowledge. Anyone have a clue what could be causing this?

    I see, good to know. IT couldn't have been someone visiting the CA page turning it on, as its an IIS only setting. I cant say that no one ever would have changed the settings, but generally I am the administrator for this server and my colleagues don't touch
    it.
    When I say default content pages I mean my SharePoint site collection pages. The problem I was having when I started this thread was about CA, but I also noticed on my site collection that FBA is turned on as well. When I turn this off a few things
    happen, generally I get a message around authorization saying that the site collection admin or farm admin cannot view the page. On the few occasions I am able to login, the page content often renders without any css, so its just plain text on the page, or
    it places the text in random locations around the page. Generally when I try to navigate though I just get an access denied message shortly therafter. Keep in mind I have done absolutely no setup at all around FBA, so I'm not sure why turning off an authentication
    method that has not been configured at all would not allow me to access my site pages.

  • Exchange 2013 SP1 OWA something went wrong

    Hi,
    I have a three node exchange 2013 DAG cluster that I upgraded to SP1 three days ago.   All email flows currently work and ECP is available on all node on all browsers for all users.   OWA was working on 2013 CU3.   After 
    the upgrade to SP1  and I confirmed that all email flows were working,  I did change the administrators  username.  I noticed OWA problems after that, but they would have happened before the administrator rename.  I have confirmed 
    certificates and binding are correct on all three nodes.  I did rebuild the OWA directory on one node with no success.
    However OWA is only available using Firefox (tested on several users on several machines) .   Logging on to ECP using IE 11 works fine (multiple users) Logging on to OWA using  IE 11 give me the error.  This is happening on
    all three nodes using IE 11 but not Firefox 27
    something went wrong
    Sorry, we can't get that information right now. Please try again later. If the problem continues, contact your helpdesk.
    X-OWA-Error: ClientError;exMsg='_u' is undefined;file=ReferenceError: '_u' is undefined at $LE (https://exch02.loran3.net/owa/prem/15.0.847.32/scripts/boot.1.mouse.js:1:155) at Anonymous function (https://exch02.loran3.net/owa/prem/15.0.847.32/scripts/boot.1.mouse.js:1:305913) at $8J (https://exch02.loran3.net/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:60172) at $E (https://exch02.loran3.net/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:59789) at $4pj (https://exch02.loran3.net/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:57814) at $6JC (https://exch02.loran3.net/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:58302) at Anonymous function (https://exch02.loran3.net/owa/prem/15.0.847.32/scripts/boot.1.mouse.js:1:306768) at $8J (https://exch02.loran3.net/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:60172) at $E (https://exch02.loran3.net/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:59789) at $4pj (https://exch02.loran3.net/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:57814):406
    X-OWA-Version: 15.0.847.32
    X-FEServer: EXCH02
    X-BEServer: null
    Date: 1/2/1601 2:43:20 PM
      Log Name:      System
    Source:        Microsoft-Windows-DistributedCOM
    Date:          3/13/2014 11:45:50 PM
    Event ID:      10028
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          SYSTEM
    Computer:      exch01.loran3.net
    Description:
    DCOM was unable to communicate with the computer EXCH02.loran3.net using any of the configured protocols; requested by PID     115c (c:\windows\system32\inetsrv\w3wp.exe).
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
        <EventID Qualifiers="0">10028</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8080000000000000</Keywords>
        <TimeCreated SystemTime="2014-03-14T05:45:50.109325400Z" />
        <EventRecordID>12481</EventRecordID>
        <Correlation />
        <Execution ProcessID="596" ThreadID="1372" />
        <Channel>System</Channel>
        <Computer>exch01.loran3.net</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="param1">EXCH02.loran3.net</Data>
        <Data Name="param2">    115c</Data>
        <Data Name="param3">c:\windows\system32\inetsrv\w3wp.exe</Data>
        <Binary>3C5265636F726423313A20436F6D70757465723D286E756C6C293B5069643D3539363B332F31342F3230313420353A34353A35303A3130393B5374617475733D313832353B47656E636F6D703D323B4465746C6F633D313436313B466C6167733D303B506172616D733D303B3E3C5265636F726423323A20436F6D70757465723D286E756C6C293B5069643D3539363B332F31342F3230313420353A34353A35303A3130393B5374617475733D313832353B47656E636F6D703D323B4465746C6F633D3135333B466C6167733D303B506172616D733D343B7B506172616D23303A2D323134363839333030367D7B506172616D23313A347D7B506172616D23323A36383132367D7B506172616D23333A317D3E</Binary>
      </EventData>
    </Event>                   ---------------------                 I am also getting
    the following error
    Log Name:      Application
    Source:        ASP.NET 4.0.30319.0
    Date:          3/14/2014 12:46:26 AM
    Event ID:      1309
    Task Category: Web Event
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      exch01.loran3.net
    Description:
    Event code: 3005
    Event message: An unhandled exception has occurred.
    Event time: 3/14/2014 12:46:26 AM
    Event time (UTC): 3/14/2014 6:46:26 AM
    Event ID: 7741cd563e154a14a0ba52343b4e30ee
    Event sequence: 328
    Event occurrence: 87
    Event detail code: 0
    Application information:
        Application domain: /LM/W3SVC/2/ROOT/owa-1-130392504882416692
        Trust level: Full
        Application Virtual Path: /owa
        Application Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\
        Machine name: EXCH01
    Process information:
        Process ID: 8756
        Process name: w3wp.exe
        Account name: NT AUTHORITY\SYSTEM
    Exception information:
        Exception type: MapiExceptionIllegalCrossServerConnection
        Exception message: MapiExceptionIllegalCrossServerConnection: Monitoring mailbox [] with application ID [Client=OWA] is not allowed to make cross-server calls from [EXCH01.loran3.net] to [EXCH03.loran3.net]
       at Microsoft.Mapi.CrossServerDiagnostics.BlockCrossServerCall(ExRpcConnectionInfo connectionInfo, String mailboxDescription)
       at Microsoft.Mapi.CrossServerConnectionPolicy.CheckAndBlockMonitoringMailboxes(ExRpcConnectionInfo connectionInfo)
       at Microsoft.Mapi.CrossServerConnectionPolicy.Apply(ExRpcConnectionInfo connectionInfo)
       at Microsoft.Mapi.ExRpcConnectionFactory.Create(ExRpcConnectionInfo connectionInfo)
       at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag
    storeFlags, CultureInfo cultureInfo, Boolean wantRedirect, String& correctServerDN, ClientIdentityInfo clientIdentity, Boolean unifiedLogon, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout,
    TimeSpan callTimeout, Byte[] tenantHint)
       at Microsoft.Mapi.MapiStore.OpenMailbox(String serverDn, String userDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo, ClientIdentityInfo
    clientIdentity, String applicationId, Byte[] tenantPartitionHint, Boolean unifiedLogon)
       at Microsoft.Exchange.Data.Storage.MailboxSession.ForceOpen(MapiStore linkedStore, Boolean unifiedSession)
    Request information:
        Request URL:
    https://localhost:444/owa/proxylogon.owa
        Request path: /owa/proxylogon.owa
        User host address: 127.0.0.1
        User: LORAN3\SM_ae42d22c64ff48a5a
        Is authenticated: True
        Authentication Type: Kerberos
        Thread account name: NT AUTHORITY\SYSTEM
    Thread information:
        Thread ID: 39
        Thread account name: NT AUTHORITY\SYSTEM
        Is impersonating: False
        Stack trace:    at Microsoft.Mapi.CrossServerDiagnostics.BlockCrossServerCall(ExRpcConnectionInfo connectionInfo, String mailboxDescription)
       at Microsoft.Mapi.CrossServerConnectionPolicy.CheckAndBlockMonitoringMailboxes(ExRpcConnectionInfo connectionInfo)
       at Microsoft.Mapi.CrossServerConnectionPolicy.Apply(ExRpcConnectionInfo connectionInfo)
       at Microsoft.Mapi.ExRpcConnectionFactory.Create(ExRpcConnectionInfo connectionInfo)
       at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag
    storeFlags, CultureInfo cultureInfo, Boolean wantRedirect, String& correctServerDN, ClientIdentityInfo clientIdentity, Boolean unifiedLogon, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout,
    TimeSpan callTimeout, Byte[] tenantHint)
       at Microsoft.Mapi.MapiStore.OpenMailbox(String serverDn, String userDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo, ClientIdentityInfo
    clientIdentity, String applicationId, Byte[] tenantPartitionHint, Boolean unifiedLogon)
       at Microsoft.Exchange.Data.Storage.MailboxSession.ForceOpen(MapiStore linkedStore, Boolean unifiedSession)
    Custom event details:
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="ASP.NET 4.0.30319.0" />
        <EventID Qualifiers="32768">1309</EventID>
        <Level>3</Level>
        <Task>3</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-03-14T06:46:26.000000000Z" />
        <EventRecordID>115079</EventRecordID>
        <Channel>Application</Channel>
        <Computer>exch01.loran3.net</Computer>
        <Security />
      </System>
      <EventData>
        <Data>3005</Data>
        <Data>An unhandled exception has occurred.</Data>
        <Data>3/14/2014 12:46:26 AM</Data>
        <Data>3/14/2014 6:46:26 AM</Data>
        <Data>7741cd563e154a14a0ba52343b4e30ee</Data>
        <Data>328</Data>
        <Data>87</Data>
        <Data>0</Data>
        <Data>/LM/W3SVC/2/ROOT/owa-1-130392504882416692</Data>
        <Data>Full</Data>
        <Data>/owa</Data>
        <Data>C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\</Data>
        <Data>EXCH01</Data>
        <Data>
        </Data>
        <Data>8756</Data>
        <Data>w3wp.exe</Data>
        <Data>NT AUTHORITY\SYSTEM</Data>
        <Data>MapiExceptionIllegalCrossServerConnection</Data>
        <Data>MapiExceptionIllegalCrossServerConnection: Monitoring mailbox [] with application ID [Client=OWA] is not allowed to make cross-server calls from [EXCH01.loran3.net] to [EXCH03.loran3.net]
       at Microsoft.Mapi.CrossServerDiagnostics.BlockCrossServerCall(ExRpcConnectionInfo connectionInfo, String mailboxDescription)
       at Microsoft.Mapi.CrossServerConnectionPolicy.CheckAndBlockMonitoringMailboxes(ExRpcConnectionInfo connectionInfo)
       at Microsoft.Mapi.CrossServerConnectionPolicy.Apply(ExRpcConnectionInfo connectionInfo)
       at Microsoft.Mapi.ExRpcConnectionFactory.Create(ExRpcConnectionInfo connectionInfo)
       at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag
    storeFlags, CultureInfo cultureInfo, Boolean wantRedirect, String&amp; correctServerDN, ClientIdentityInfo clientIdentity, Boolean unifiedLogon, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout,
    TimeSpan callTimeout, Byte[] tenantHint)
       at Microsoft.Mapi.MapiStore.OpenMailbox(String serverDn, String userDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo, ClientIdentityInfo
    clientIdentity, String applicationId, Byte[] tenantPartitionHint, Boolean unifiedLogon)
       at Microsoft.Exchange.Data.Storage.MailboxSession.ForceOpen(MapiStore linkedStore, Boolean unifiedSession)
    </Data>
        <Data>https://localhost:444/owa/proxylogon.owa</Data>
        <Data>/owa/proxylogon.owa</Data>
        <Data>127.0.0.1</Data>
        <Data>LORAN3\SM_ae42d22c64ff48a5a</Data>
        <Data>True</Data>
        <Data>Kerberos</Data>
        <Data>NT AUTHORITY\SYSTEM</Data>
        <Data>39</Data>
        <Data>NT AUTHORITY\SYSTEM</Data>
        <Data>False</Data>
        <Data>   at Microsoft.Mapi.CrossServerDiagnostics.BlockCrossServerCall(ExRpcConnectionInfo connectionInfo, String mailboxDescription)
       at Microsoft.Mapi.CrossServerConnectionPolicy.CheckAndBlockMonitoringMailboxes(ExRpcConnectionInfo connectionInfo)
       at Microsoft.Mapi.CrossServerConnectionPolicy.Apply(ExRpcConnectionInfo connectionInfo)
       at Microsoft.Mapi.ExRpcConnectionFactory.Create(ExRpcConnectionInfo connectionInfo)
       at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag
    storeFlags, CultureInfo cultureInfo, Boolean wantRedirect, String&amp; correctServerDN, ClientIdentityInfo clientIdentity, Boolean unifiedLogon, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout,
    TimeSpan callTimeout, Byte[] tenantHint)
       at Microsoft.Mapi.MapiStore.OpenMailbox(String serverDn, String userDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo, ClientIdentityInfo
    clientIdentity, String applicationId, Byte[] tenantPartitionHint, Boolean unifiedLogon)
       at Microsoft.Exchange.Data.Storage.MailboxSession.ForceOpen(MapiStore linkedStore, Boolean unifiedSession)
    </Data>
      </EventData>
    </Event>

    Thanks
    I have three  servers exch01,exch02,and exch03.  All three have both CAS and mailbox server roles.   This problem  does not occur using firefox (OWA and ECP are available) but the problem occurs with IE 11  and safari (ECP
    work, OWA dos not)  I have tried this from different machines and different users.  I have cleared the browser's cache and have even reloaded the client machines.  The problem occurs across all three exchange servers. 
    I have used iis manager to confirm the binding are correct. (works on Firefox) 
    From the local server ,  If I browse to
    https://localhost/ecp  I get my ecp page.   If I browse to
    https://localhost/owaI get the something went wrong page (X-OWA-Error: ClientError;exMsg='_u' is undefined;file=ReferenceError: '_u' is undefined)
    If I try to browse to https://localhost:444/owa/proxylogon.owa  I get the error page "this page cannot be displayed"
    I confirmed port 444 bindings are correct

  • SharePoint 2013 - Refiners "Sorry, something went wrong."

    Good Afternoon,
    I have an issue that has had me stumped for a couple of days now. I have a number of search results pages and on one of them and only one of them I am getting an error.
    Whenever I add a refiners webpart and save the page everything works fine. However if I add or remove any refiners I get the infamous "Sorry, something went wrong." Whats causing my problems though is that when I click on Show Details there is
    no correlation ID and I cannot see any errors in the ULS logs that might be related to this.
    Using SharePoint Manager 2013 I opened the page properties and selected the webpart and I am getting the following message against "Effective Storage" and "Permissions" : Trying to use an SPWeb object that has been closed or disposed
    and is no longer valid.
    So in desperation I deleted the page and recreated it but the issue persists. The only thing different about this page and the other pages is that this page show people results. However if I change the query to use the "System Everything" results
    source I still get the error.
    edit:
    I have just tried to amend the refiners on an existing page and I can amend them with no issues. I then created a brand new page and I get the same error. On my new pages I changed nothing except adding the search box / search results and refiners web parts.
    So its an issue that does not affect existing pages only new ones..
    More info: I have just created a new site on the same same site collection and created a page on this new site and I get the same issue.
    Regards,
    Brian Jones

    Hello,
    Thanks for your interest.
    These are the steps:
    1. Create a new page
    2. Add the following web parts, Search Box, Search Results, Refiners. If I then just save and close the page everything works fine.
    3. Edit the page
    4. Edit the refiners web part.
    5. Click on change refiners* select any refiner that is already added and remove it (any it does not matter).
    6. Click OK on the web part properties. Immediately I get this issue. As you can see there is no correlation id in the error message.
    7. Edit the refiner web part again and re-add the refiner I removed. Click on OK on the web part edit pane. The issue persists.
    8. If I delete the refiner web part and re-add it the refiners web part works fine again unless I try and modify the selected refiners.
    Please note this issue occurs if I add refiners as well.
    Brian Jones

Maybe you are looking for