We have developed outlook Addins and hosted on Apache Server with SSL certicate installed with it. Some days back it was working absolutely fine on both web as well office outlook client, after windows update and client update it returns Empty blank screen?
Till the Outlook Client version 1808 all looks good in client. After the Update to outlook client 1902 Addin Stopped working on outlook client.
The error message in F12 Debugger is thrown is :
Everything was working fine before update,
Note that this addin is build on Angular version 5 frame work using routes.
Update: I was loading office.js locally from the project not from the CDN, Now when I changes the office.js path in index.html to the cdn link "https://appsforoffice.microsoft.com/lib/1/hosted/office.js" Addins started working back.
But I need something not from CDN because one of our customer has on-primises server and not the office365 .So the problem I found is the office.js loading the outlook-win32.02.js but saying permision denied if loaded from the project and not from the CDN link.
Hope to get some suggestions from the outlook web addin Team....
After lots of reasearch I decided to use CDN link "https://appsforoffice.microsoft.com/lib/1/hosted/Office.js", and every thing started work as like before,
Then I decided compare my office.js inside the library with the CDN link javascript then I came to know that office script library is updated and I m having an old package, after reseach I found the github project updated recently , the below link will directly takes to the updated libraby , one can download with your existing one,
"https://github.com/OfficeDev/office-js/tree/release/dist" .
Hope this works for all having this issue.
Related
We have a Custom Outlook Addin. Which is frequently giving
"Add-in error: This add-in may not load properly, but you can still try to start it."
After couple of retries it started working and it is happening on every first load when I click the add-in.
What could cause this issue ?
Our manifest file is fine and the site is also working fine in browsers.
Make sure add-in's pages reference the office.js library and include an Office.initialize handler.
Take a look at the Understanding the JavaScript API for Office section for more information.
I install prestashop 1.7.5.1 (the final version) in my local server (in wamp server - Apache 2.4.37 - PHP 7.2.14 - MySQL 5.7.24). My front office is ok, but all pages in my back office have problems. For example, in the picture below, My computer is not connected to the Internet.
but when I connect my computer to the internet my back office all is ok as shown in the picture below:
as if jquery or css is not loaded properly in my back office (when My computer is not connected to the Internet).I want work offline on my shop.
Please help me, many thanks.
Remember Prestashop use Bootstrap Framework, if you are offline the CDN wont receive the correct communication, you can see the result
You can try to use the Maintenance mode, to work offline.
This comes because of Prestashop backoffice use some external files of css and images.
To work offline you installed it in your website admin directory.
You can find those external link in your css admin file your_directory/admin_folder/themes/default/css/admin-theme.css
I created an Outlook add-in using Office developer tools for Visual Studio 2015.
The project is correctly generated, and I deployed it to an azure app service.
When I try to add the add the manifest to my Office 365 dev subscription, I get the following error : "Something went wrong, and we couldn't install your add-in. Please try again later"
This manifest is the exact manifest generated by VS, the only modification was to replace the place holder for the Web URL by the one of the Azure app service.
Has anyone encountered this issue before ?
Thanks.
Can you upload or copy/paste the manifest you are trying?
If you are installing via URL. This is also a common error that is given when OWA cannot download the Manifest from the URL. There could be permissions/something wrong with the URL.
Otherwise, you may also get more detailed information on why the install is failing if you install from the Manage App page instead of the In Client Store Page. (Detailed errors on the In Client Store Page will be added soon)
I installed Microsoft SharePoint and Project PWA on Windows Server 2008 R2.
When I want to open Library in Windows Explorer, I randomly get an error:
Your client does not support opening this list with Windows Explorer
When I open IE it's working for 1st and 2nd time, but after some clicks it's not working anymore and I need to restart IE and then it normally works for couple of times.
When it not working through Sharepoint it also not works via \server\DavWWWRoot\PWA and oposite.
I'm searching through the web for weeks and didn't find any solution.
Do you have any idea what should be wrong here. Any suggestion is welcome :)
I had the same exact issue with Windows 7 and explorer view. The following steps resolved the issue for me:
First - be sure that the Web Client service is running (run>services.msc).
Next - In I.E. check Tools>Internet Options>Security>Local Intranet>Sites>Advanced and add the site that you want to use explorer view with.
This finally fixed it for me. I hope that you have already found a solution to this issue! I was surprised at how difficult it was to find a solution to this problem!
This error message is a symptom to a billion different problems.
I solved this problem when I realized my XP32 box could do this just fine with IE8. So I reverted to IE8 in 7x64 (you have to do it by uninstalling updates for IE until you're back at 8) and it didn't work. The build versions were different and on the 7x64 "about" box it said IE8 was using 256-bit cipher while in XP32 it had 128-bit. That to me was a hint that there may be 64-bit issues even when you run the 32-bit executable.
Then I found this hotfix so I reinstalled the windows update for IE10 and then installed this hotfix. Now I'm able to open the TeamCenter site in question in windows Explorer. IE10 reports it's version 10.0.9200.16686. I cannot guarantee that it was the hotfix alone (and not also the reinstallation of IE10) which fixed it. But I'm willing to bet it was the hotfix alone.
In XP I found it impossible to then map this network location to a drive letter, as mapping doesn't like URL's. However in Windows 7 you can transform the URL so that it is interpreted as a Windows share. If the URL of a given folder is of this form:
https://somesharepoint.com/folder1/folder2/folder3
you can also access it as
\\somesharepoint.com#SSL\DavWWWRoot\folder1\folder2\folder3
and, in this form, it can be mapped to a drive letter.
I do have issues at that point that even with IE10 open and logged in to the site I see some random time-out like problems and I get kicked off (and prompted to log in again in IE10). My situation is complicated because the site I'm accessing requires an Exostar token to log in, so I have to log in via website no matter what.
If it helps any one do the steps suggested above:
Make sure to use 32 bit internet explorer (program files (x86)/internet explorer).
Like was mentioned above Web client must be started.
You may also need to add your site to trusted sites in internet explorer.
Make sure enabled protected mode in internet options is disabled.
This is what finally fixed it for me: Check "Keep me signed in" on the login page. This was the key for me. Will not work without it checked in my case.
I had the same symptoms, and it turned out I don't have a root site collection. Creating one solved this for me.
Summarized the troubleshooting steps here:
http://letitknow.wordpress.com/2012/07/22/your-client-does-not-support-opening-this-list-with-windows-explorer-error/
There can be multiple reasons for it.
One could be using IE x64 version. It won't work there.
Secondly, check out this blog:
http://blogs.technet.com/b/asiasupp/archive/2011/06/13/error-message-quot-your-client-does-not-support-opening-this-list-with-windows-explorer-quot-when-you-try-to-quot-open-with-explorer-quot-on-a-sharepoint-document-library-in-office-365-site.aspx
I experienced the same problem as well.
And I found out that if none of the above options are working, and if you work in an organisation, maybe the proxy is blocking the "Open with Explorer" option.
I did the same, and removed the proxy and it worked just fine.
this fixed it for me ( however in windows server 2008 you may need to install desktop experience i think its called)
After you log into windows go into services then restart the WebClient then see if you can use explorer view without the error " your client does not support. blah blah blah" if it does work then. make a batch file that says:
net stop webclient
net start webclient
then make a scheduled tasks that runs that batch file at start up. Have it run as a user with administrative rights, make sure you tell it to run even if user is not logged in. it should prompt you for the password of the admin account you selected. this worked for me with windows 7.
I found online where the error can occur intermittently with SharePoint 2010, however I think the SharePoint version is irrelevant. They said the client polls for a SharePoint root site and that the error occurs if one isn't found.
We have not seen the error since I created a root site even though we’re only using WSS3. Our errors began when we changed clients to Windows 7. So in our case it sounds like the issue could be the root site polling due to an IE8 security change in Windows 7.
SOLUTION:
*you on x64 bit machine* so solution is that there is no problem but you are using the wrong IE shortcut.
There are different IE types you can use (just type Internet Explorer in start search bar) and you will see..
Internet Explorer (64-bit) - won't show any sharepoint add-ons
Internet Explorer (No Add-ons) - won't show any sharepoint add-ons
Internet Explorer - only this will show sharepoint add-ons and will
work so basically make sure you always use this version of IE
We have customized ribbon(js scripts) that loads properly in IE and firefox but in google chrome(which is a requirement to use it due to its high response time) it does not load the ribbon at the first instance. However, it loads after several page load refreshes(Ctrl + F5). If anyone come across this issue, provide your inputs. Appreciate your help. Thanks
SharePoint and IIS are always trying to cache resource, to ensure application performace. When you're doing SharePoint Development you've always to ensure that cache is cleared.
Especially when you're working with the SharePoint ribbon it's required to clear the cache before accessing the website after deployment.
When you're using CKS tools for deployment from VS2010 you have to ensure that files are copied to the SharePoint Root. Sometimes I get an exception when they try to overwrite JS files in the SharePoint root, because sharepoint has a handle on them.
When doing SharePoint development I always copy *.resx and *.js by hand.
The issue appears to be with the rendering of the search box control in Google Chrome. Try adding 'Visible="false"' to the 'SharePoint:DelegateControl runat="server" ControlId="SmallSearchInputBox" Version="4"' control on the master page. This corrects the rendering issue for us.
SharePoint is officially not built to work in Google Chrome
I just fixed my webkit (chrome and safari) browser issues such as scrolling and the ribbon loading with this nice script http://goo.gl/1OUlI. Ended up being a timing issue. Hope it helps you out. I see this is a bit old but no best answer.