There is some very strange behavior occuring with protocol handlers and taskpane addins from newer office versions.
I've done extensive testing and found that if I have a protocol url such as
"ms-excel:nft|u|https://office.iwriter365.com/api/getFile/test.xltx"
This protocol works perfectly fine until the moment I start a taskpane with the taskpane url "https://office.iwriter365.com". After this Excel will display the error "Microsoft Excel can not access the file...." every time I launch the protocol url.
The only way to make the protocol url function again is by closing all instances of Excel.
This has started happening somewhere around Office version 1802 or 1803.
Related
We have implemented an Outlook Add in that uses the SupportsPinning option from Req Set 1.5 and the SupportsSharedFolders option from Req Set 1.8. Both options are working fine in Windows Outlook Native client but malfunction in Outlook.com, outlook.office365.com, OWA (tested in latest Chrome, IE and Edge).
These are the steps and the outcome:
Open Shared Inbox in web outlook
Select email
Open Add-in
Pin Add-in
Select another email
OUTCOME: Add-in window closes, EXPECTED: Add-in window remains open
The other strange thing is that if you then select another message, the add-in remains closed BUT if you select an email that you previously opened the add-in on, in the shared inbox, the add-in reopens.
Does anyone know why this behaviour is occurring? Is there a way around it??
I've also faced the problems too.
Outlook OWA still doesn't fully provide that feature.
You can check here
Docs say that this feature is not supported on outlook.com.
So, we have no choice.
Trying to work on this training kit to get educated with SQL Server 2014.
As seen here:
https://www.microsoft.com/en-ca/download/details.aspx?id=41700
I can't get it to work. It seems to come with a pdf explaining how to get it to work on your browser. Apparently by default the browser (chrome) won't run "application that use XML configuration files when they are run from a local computer" The only way to get it to work is by placing "--allow-file-access-from-files" to the google chrome shortcut properties window in the "target" location.
Even after doing all this I still get a message saying "network error" and the message on the top of the screen on the browser saying "To run this page in google chrome, close Chrome then create a shortcut with the --allow-file-access-from-files" property on..." (basically telling me to do the thing I just did following pdf instructions the kit came with)
Does anyone know what is going on?
Thanks in advance.
Background
We currently have a SilverLight form that posts data to a second common form that multiple applications use, which then runs the need business logic to place the data into a database.
We have several national and international offices where this form is used.
There is one office location (CO) where this form is consistently producing intermittent error messages and based off log data, it is only happening in this office.
Error Symptoms
Initially users will typically report that there is an error and when I log into their machine using MS Communicator, 80% of the time it would start working.
I started installing Fiddler on their machines to try and capture more information but 100% of the time I did that, the form started posting successfully. The users being resourceful, simply start Fiddler anytime the form doesn't post and it works fine.
I also asked users to go through Citrix which is hosted in the TX office and the form posts fine.
Error Details
I used OPNET to better monitor the traffic and I found that when user's simply open IE the authentication handshake fails.
Client => Server = 401
Client <= Server = Authentication Token
Client does not respond
When we use fiddler, the handshake is successful.
The error returned by SilverLight was a very generic [HttpWebRequest_WebException_RemoteServer] message.
Question
What would cause the handshake to work sometimes by itself, always with fiddler and CITRIX, and sometimes it doesn't.
I have a SL navigation application, that currently runs on a shared hosting package with a 3rd party ISP. I can login, and register using the ASP.NET membership and role providers.
I have now setup a dedicated server, on which only my app will run. It does not yet have a domain name that points to it... I access it via an IP address.
I've copied the entire site (including the ClientBin and all the XAP's) to the new server, but the Authentication and Registration services don't work... they just return NotFound.
When I check Fiddler on the working site, this service is called :
www.myaddress.com/ClientBin/MyApp-Web-AuthenticationService.svc/binary/Login
which of course succeeds. However, on the other site, the fiddler trace looks the same (because I just copied the site) :
123.123.123.123/ClientBin/MyApp-Web-AuthenticationService.svc/binary/Login
but, the call fails with NotFound. Fiddler reports it as HTTP/1.1 500 Internal Server Error. When I open
http://localhost/ClientBin/MyApp-Web-AuthenticationService.svc/binary/Login
on the server, I get the HTTP/1.1 500, as well as this description :
Handler "svc-Integrated" has a bad module "ManagedPipelineHandler" in its module list
Which leads me to believe that there is something wrong with my IIS config, as the exact same code is working on another system.
What is a "bad module"? How do I fix it?
Normally this type of error is that ASP.Net is not activated or that a handler for svc is not registered or registered correctly.
In your case is looks a bit different. It could be that you have .net framework 4.0 code that you are trying to run in a .net framework 2.0 application pool.
IIS 500 errors often show up with more information in the Windows Event log - if you can somehow get access to that?
Also I've noticed that often the server will actually send debugging output back to the client that everything seems to ignore. Have you checked the entire raw response that is coming back from the server to see if there are any clues there?
I have a client who installed our silverlight app recently. it works fine from their server itself. but when they try to run it from a client, they can log in through the aspx login page, but on the main page, which hosts the tag and the .xap file, they see absolutely nothing!
I cannot see their screens, just get occasional screenshots via email and cross my fingers that they are typing the URL I tell them to. Even Shareview is not working for them - they can see my screen but I cannot see theirs.
So I am pleading - help! Please throw out some wacky ideas. I just learned an hour or so ago that they did not even have silverlight installed, so the mornings debugging effort was a waste of time. So who knows what the next fascinating source of problems is?
Here is the user-agent info. Oor app is .net 4.0 could that be the problem? It does noty look to my untrained eye that the client supports 4.0 (from the web server log):
Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.30;+.NET+CLR+3.0.04506.648;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) 401 3 5 0
Getting closer - I see that the GET request for the XAP is returning 401 - not found! What would do that?
It's very possible that they are blocking XAP files either directly or indirectly at the firewall. XAP files are simply ZIP files and inspection-based firewalls tend to look at these as a security risk. You may want to see if they can setup an exception in their rules.
Hmm..
1) check if your client access the good url. Request their IP address, then check the web server logs. ie: are they requesting the good url, are they downloading the xap? (check if they use a proxy, too?)
2) check that they restarted their browser after installing the Silverlight runtime.
3) Do you handle the UnhandledException event for your Application class? If no, use it to send detailed exception logs to your server on application crash.
4) Use javascriptto initialize your Silverlight application. This way, you can be notified if the runtime fail to start, (for example if it failed to load the xap file) You can use ajax to report the issue to the webserver.