Office Add-Ins : Langauge mismatch

Hello
I installed on Wondows XP
OBI EE 10.1.3.4.1
and
Ms Office 2007 (english)
After installing and configuring Oracle BI Office
(like explain in OBE : Using OBI Office Add-Ins with OBI EE ...)
I tried to insert data in Excell from Oracle BI Catalog
I received this error message "Langauge mismatch"
For loging I used English or French language with the same result.
Have you got an idea ?

FYI
The error occurs due to a mismatch between the Regional Settings between the client PC and OBIEE Server.
I don't know how to change the Regional Setting for OBIEE.
For this reason I changed the Regional Settings on the windows client machine from the Language French to English (US).
After restart It works

Similar Messages

  • Office Add-Ins using both CLR4/CLR2 Components

    We have an existing Office add-in built on .NET 3.5 (SP1) that we are migrating to .NET 4.5.2 that will also support Office (64-bit).  We use a WinForms component from TX Text Control that is built on CLR2.  Their control should and does work on
    .NET 4.x applications but when we use it in the Office context, we were getting error.
    When we added the following to the winword.exe.config and outlook.exe.config (C:\Program Files\Microsoft Office\Office15), the add-in worked OK.
    <?xml version="1.0" encoding="utf-8" ?>
    <configuration>
    <startup useLegacyV2RuntimeActivationPolicy="true">
    <supportedRuntime version="v4.0" />
    </startup>
    </configuration>
    My concern/questions are:
    Should we adding or modifying this file (*.exe.config) in the Microsoft Office directory?  Is this something that third-parties are expected to do?
    Is there a way to modify this file (*.exe.config) that does not affect other applications?
    Do we need to be worried about conflicts with other add-ons from other companies that users could be using?
    Is there a way to scope the useLegacyV2RuntimeActivationPolicy="true" tag to just our add-on or just one component?Why do we have this issue if we are compiling everything to CLR4 even though we are using a CLR2 component that works under CLR4?
    Thanks
    Scott

    Hello Scott,
    There is no need to post your message on
    multiple forums.
    There are two ways to go:
    1. Edit the Office application *.exe.config file. This is a workaround if you can't or don't want to rebuild controls/components against a new CLR version.
    2. Rebuild controls against the new CLR version - 4.0.
    As you understand it is better to choose #2 way.
    Here is the answers:
    > Should we adding or modifying this file (*.exe.config) in the Microsoft Office directory?  Is this something
    that third-parties are expected to do?
    Nope. You can edit it programmatically. But typically you shouldn't do so because it
    affects other add-ins as well.
    > Is
    there a way to modify this file (*.exe.config) that does not affect other applications?
    Nope, because you develop an add-in, not a standalone application. All add-ins will be affected.
    > Do we need to be worried about conflicts with other add-ons from other companies
    that users could be using?
    Nobody can be sure that other add-ins are well-writer doesn't
    contains bugs :)
    > Is
    there a way to scope the useLegacyV2RuntimeActivationPolicy="true" tag to just our add-on or just one component?Why do we have this issue if we are compiling everything to CLR4 even though we are using a CLR2 component that works under CLR4?
    No, there is no way because add-ins are not standalone applications. 

  • How to silently install office add-ins and bypass the microsoft office customization installer popup

    Hello all,
    I want to install an office add-in for all the computers in my company silently. But when I use the commands "%~dp0\test.exe" /S. I receive the following popup.
    Is there a way to bypass this to install the add-in silently?
    Thank you very much for the help.

    probably, this file was downloaded via Internet Explorer, from the IE "Internet" zone?
    If so, the Alternate Data Stream, on the file, will have the Zone.Identifier populated.
    If you right-click the file in Windows Explorer, do you get the "Unblock" button offered?
    If so, click Unblock, and then try your script again.
    more on ADS:
    http://blogs.technet.com/b/askcore/archive/2013/03/24/alternate-data-streams-in-ntfs.aspx
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

  • How to add MS Office add-in from inside a Thinapp 5 virtual application to a MS Office 2013 suite that is installed on a base image

    Hi,
    We have the following solution:
    VMware Horizon View 5.3.1
    Non-persistent Linked-clone pool with delete VM after logoff
    Windows 8.1 Update 1 Enterprise 64 bit
    MS Office 2013 32-bit installed on image
    Thinapps registered for each user from logonscript with thinreg.exe command. Thinapps is located on a network share
    Native Windows roaming profiles with appdata/roaming, appdata/local without appdata/locallow(persona management does not support Windows 8.1 in View 5.3.1)
    This is our issue:
    We have a 3rd party application with a couple Thinapp entrypoints(exe files) and in the Thinapp package process we also installed Office addins. We tested that the Add-ins was opened inside Outlook, Word and Powerpoint before post installation scan.
    The problem is that the add-ins is not added to Office 2013 before or after the Thinapp is started on a test client.
    I have tried several changes in the package.ini and virtual filesystem attributes(no registry changes yet):
    Package.ini:
    ChildProcessEnvironmentExceptions=WINWORD.EXE;EXCEL.EXE;POWERPNT.EXE;OUTLOOK.EXE;
    ChildProcessEnvironmentDefault=External
    ChildProcessEnvironmentExceptions=excel.exe;outlook.exe;powerpnt.exe;winword.exe
    ChildProcessEnvironmentDefault=Virtual
    VirtualizeExternalOutOfProcessCOM=0
    DirectoryIsolationMode=Merged
    RegistryIsolationMode=Merged
    I have also read that you could make entrypoints to the locally installed Office 2013, but I get errors on the build process. ref. link: http://edwinfriesen.nl/content/?p=105#comments
    The best thing would be if the add-ins were added in the logon process together with thinreg.exe, but if that is not supported, the add-ins must be added to Office either in a custom Office shortcut/entry point or after starting the Thinapp virtual application.
    Remember that the application needs to registered every times the user logon, because we use a non-persistent View pool.
    I would really appreciate if somebody could tell me how to add Office add-ins from inside a Thinapp virtual application/package to a locally installed MS Office 2013 suite on a Windows "base" image?
    We do not want to add the whole Office suite to the Thinapp virtual package and not add the add-ins trough GPO,SCCM etc.

    What about the COM object parameters in package.ini ?
    We can live with scripting in logon or changed logon scripts etc.
    And you don't no need to lock in the project files.
    From package.ini documentation:
    ObjectTypes Parameter
    The ObjectTypes parameter specifies a list of virtual COM object types that are visible to other applications in
    the physical environment. You can use scripts, such as VBScripts, to call objects that start captured applications.
    An object type is registered to only one native or virtual application at a time. If you install Office 2003 on the
    native machine and want to use a virtual Office 2007 package, you must determine whether to have the virtual
    or native application handle the object types.
    If you want the virtual Office 2007 to handle the object types, you can leave the ObjectTypes setting in the
    Package.ini file, build the package, and register it using the thinreg.exe utility. If you want the native Office
    2003 to handle the object types, you must remove the ObjectTypes setting from the Package.ini file before
    building and registering the package.
    You cannot add random entries to the ObjectTypes parameter.
    You can only remove entries that were generated by the capture process.
    Example: Starting a Virtual Application When a COM Object is Created
    If a script or a native application creates an Excel.Application COM object or other COM objects listed in the
    ObjectTypes parameter, ThinApp starts the virtual package.
    [Microsoft Office Excel 2007.exe]
    ObjectTypes=Excel.Application;Excel.Application.12;Excel.Chart;
    Excel.Macrosheet;Excel.Sheet; Excel.Workspace

  • Icloud outlook, inactive application add-ins?

    In Outlook 2013, Microsoft Office Add-Ins, I keep having problems with icloud outlook switching back to an inactive application.  I keep having to go back in and switch it back to an active add-in.  I hadn't had this problem until 3 weeks ago.  I'm not sure what was changed.  Is there a fix to this problem?

    go to
    control panel
    internet connections
    click on icloud
    check boxes wanted to update and go

  • Office 2007 add-ins will not load on Windows 7 x64

    Hi there,
    I have a brand new built Windows 7 x64 desktop with Office 2007 32 bit installed. When I install Oracle BI Publisher Desktop 11.1.1.7.0 it loads without errors. Except none of the add-ins will load. I have done the usual Add-ins / Com Add-in / Tick box but nothing.
    After further investigation it appears there is a VSTO 4.0 error on the machine when I run the C:\Program Files (x86)\Oracle\BI Publisher\BI Publisher Desktop\DotNet2007\TBAddin.vsto. The error itself is only failed when it tries to download savexmldata.png from C:/Program Files (x86)/Oracle/BI Publisher/BI Publisher Desktop/DotNet2007/Resources. The fact is there isn't a folder called Resources nor a file called savexmldata.png.
    I thought it may be an assemblies error and tried installing the newest versions of Microsoft Office 2007 Primary Interop Assemblies and Microsoft Visual Studio 2010 Tools Office Runtime (x64) but all are up to date.
    See below for the error:-
    Customization URI: file:///C:/Program Files (x86)/Oracle/BI Publisher/BI Publisher Desktop/DotNet2007_2/ETBAddIn.vsto
    Exception: Downloading file:///C:/Program Files (x86)/Oracle/BI Publisher/BI Publisher Desktop/DotNet2007_2/Resources/field.png did not succeed.
    ************** Exception Text **************
    System.Deployment.Application.DeploymentDownloadException: Downloading file:///C:/Program Files (x86)/Oracle/BI Publisher/BI Publisher Desktop/DotNet2007_2/Resources/field.png did not succeed. ---> System.Net.WebException: Could not find a part of the path 'C:\Program Files (x86)\Oracle\BI Publisher\BI Publisher Desktop\DotNet2007_2\Resources\field.png'. ---> System.Net.WebException: Could not find a part of the path 'C:\Program Files (x86)\Oracle\BI Publisher\BI Publisher Desktop\DotNet2007_2\Resources\field.png'. ---> System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Program Files (x86)\Oracle\BI Publisher\BI Publisher Desktop\DotNet2007_2\Resources\field.png'.
    at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
    at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
    at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
    at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, Boolean useAsync)
    at System.Net.FileWebStream..ctor(FileWebRequest request, String path, FileMode mode, FileAccess access, FileShare sharing, Int32 length, Boolean async)
    at System.Net.FileWebResponse..ctor(FileWebRequest request, Uri uri, FileAccess access, Boolean asyncHint)
    --- End of inner exception stack trace ---
    at System.Net.FileWebResponse..ctor(FileWebRequest request, Uri uri, FileAccess access, Boolean asyncHint)
    at System.Net.FileWebRequest.GetResponseCallback(Object state)
    --- End of inner exception stack trace ---
    at System.Net.FileWebRequest.EndGetResponse(IAsyncResult asyncResult)
    at System.Net.FileWebRequest.GetResponse()
    at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
    --- End of inner exception stack trace ---
    at Microsoft.VisualStudio.Tools.Applications.Deployment.ClickOnceAddInDeploymentManager.DownloadAddIn(TimeSpan timeout)
    at Microsoft.VisualStudio.Tools.Applications.Deployment.ClickOnceAddInDeploymentManager.InstallAddIn()
    ************** Loaded Assemblies **************
    mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
    Microsoft.VisualStudio.Tools.Office.Runtime
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.31119.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualStudio.Tools.Office.Runtime/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Tools.Office.Runtime.dll
    System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
    System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
    System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    Microsoft.VisualStudio.Tools.Applications.Hosting
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.31119.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualStudio.Tools.Applications.Hosting/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Tools.Applications.Hosting.dll
    Microsoft.VisualStudio.Tools.Applications.ServerDocument
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.31119.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualStudio.Tools.Applications.ServerDocument/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Tools.Applications.ServerDocument.dll
    System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
    Microsoft.VisualStudio.Tools.Applications.Runtime
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.31119.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualStudio.Tools.Applications.Runtime/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Tools.Applications.Runtime.dll
    System.Deployment
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Deployment/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Deployment.dll
    System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
    System.Security
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Security/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Security.dll
    System.Xml.Linq
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.Linq.dll
    Any help would be appreciated as I am not a developer just an Application Delivery person.
    Thanks

    copy disc to your computer and try to run setup file from there.
    also, make sure your office dvd is working,

  • Acrobat XI PDF Add-ins do not appear in Office 2013

    I just installed Acrobat XI on a computer with Win7 and Office 2013. The program works fine but I have been unable to get the add-ins to appear in the apps. I had previously done  the  same installation on another computer of mine and all works fine. I have spent at least 10 hours trying everything I could find online and in the forums with no success.
    I have unistalled and reinstalled Acrobat. I have done a total repair on Office. The results are always the same.
    In Outlook, the pdf maker is shown as disabled. I click to enable it and then restart. It still does not appear and the pdf add-in is again shown as disabled. I removed the add in and then manually added it back. Same results.
    In other apps (e.g. Word), the pdf maker is shown as enabled but it does not appear on the toolbar. Again, on these apps, I've tried unchecking and checking (restarting in between) with no luck. And have also deleted the add in and then manually put it back in. No success.
    I also repeated all of the above by starting applications as adminstrator thinking that would make a difference. No success.
    I've tried using the registry editor regsrv32 to install the .dll file but I only get errors.
    I suppose there could be some registry entries that need to be deleted, but I don't have a clue which ones or where to look.
    I can't find anything else to try! Any suggestions will be helpful!

    I suspect you have AA 11.0.0. Update the product. OFFICE 2013 came out after AA XI and you need an update for opertion. I understand that AA XI has beeen updated to work with OFFICE 2013. In the meantime, just print to the Adobe PDF printer.

  • The Adobe add-ins appear in MS Word (Office 2010) but not in MS publisher

    The Adobe add-ins appear in MS Word (Office 2010) but not in MS publisher (Quick link from Ribbon) No add-ins show in settings in Publisher although they show in Word.
    Have tried re-loading MS Office 2010
    Acrobat X standard

    Yes - it shows on a friend's computer (Windows 7) I am running Windows 8
    64bit.
    According to the tutorial it should also work in Publisher.
    It shows and works perfectly in MS Word

  • GUI Patch 7 & 8 breaks MS office excel 2010 via add ins on Win 7

    We are experiencing the following problems with SAP GUI 8 (and SAP GUI 7)
    Config of device :
    Windows 7
    MS Office 2010 - excel specifically with 2 add ins for another application
    SAP GUI patch 0
    When the SAP GUI is then patched to 7 or 8 excel crashes with the following error :
    MS Visual Basic for Applications : License information for this components not found. You do not have an appropriate license to use this functionalty in design environment. > select OK and the following error appears -
    MS Visual Basic for Applications : Compile error in hidden module: ThisWorkbook. This error commonly occurs when code is incompatible with the verion, platform or architecture of this application. Click "Help: for information on how to correct this error.
    Excel then stops working. We have managed to disable the add ins and then excel works. Uninstalling the SAP GUI still leaves a broken excel. Any assistance in the resolution of this matter would be greatly appreciated. We have spent more than a week running various scenarios and patched windows and office to the latest patches with no success.
    Regards
    Anette

    Problem still exists after applying patch-10!!!!
    This way we can not use the 720-GUI.
    After installing GUI and latest patch, we still get following error starting Word2003:
    MS Visual Basic for Applications : License information for this components not found. You do not have an appropriate license to use this functionalty in design environment. > select OK and the following error appears -
    And.......
    Microsoft Visual Basic
    ActiveX-component cannot be created.

  • Will a Microsoft Office Add-In developed in Visual Studio work for both a Windows and Mac ( osx ) versions of Ms Office?

    I want to develop a Microsoft Office Word Add-In for Mac Users. I would like to know if we create it using Visual Studios in windows will it be compatible with the Mac version of office or is there a whole another way to develop for Mac?
    Please provide links so that I could follow some guidelines. The http://msdn.microsoft.com/site
    doesn't exactly speak of the platform compatibility of the Add-In.
    Thank You very Much in Advance.

    Office:Mac 2011 only supports add-ins that were developed in VBA. Office:Mac 2008 does not support add-ins at all. A
    new version of Office:Mac is slated for release in 2015, there have been no announcements as of this writing (December 2014) whether Microsoft will support additional methods of developing add-ins in the new version of Office:Mac.
    For further information, check out
    Getting Started with VBA in Office for Mac 2011 from the Office:Mac 2011 help files. You might find more assistance in developing Office:Mac add-ins in the
    Office:Mac help forums hosted by Microsoft.

  • Virtualizing an Office add-in with Office 365 installed - possible?

    I've just attempted to virtualise an Excel add-in by sequencing the add-in and providing a special shortcut to launch Excel in the bubble with the add-ins enabled.
    This normally works fine when Office is locally installed, but in this case my client has deployed the Office 365 click-to-run package, and when Excel is launched it cannot see any of my virtualised files.
    When I run listdlls.exe on Excel.exe, I see:
    C:\Program Files\Microsoft Application Virtualization\Client\Subsystems\AppVEntSubsystems32.dll
    C:\Program Files\Microsoft Office 15\root\office15\AppVIsvSubsystems32.dll
    Since Office 365 is based on App-V technology, I assume these two dlls are conflicting, and my solution going forward is to either get them to put Office down locally or convert it to a full App-V package.
    Before I do this though, does anybody know of any tricks to get it to work with the basic Office 365 package?
    Dan Gough - packageology.com
    Twitter (@packageologist) LinkedIn

    Our story is if you want to combine virtual Office 2013 with virtualized plug-ins, flatten the package into the full App-V format and use Connection Groups.
    Steve Thomas, Senior Consultant, Microsoft
    App-V/MED-V/SCVMM/Server App-V/MDOP/AppCompat
    http://blogs.technet.com/gladiatormsft/
    The App-V Team blog: http://blogs.technet.com/appv/
    The MED-V Team Blog: http://blogs.technet.com/medv
    The SCVMM Team blog: http://blogs.technet.com/scvmm/
    “This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.”

  • Add-ins that are being set to Inactive

    This pertains to Outlook 2013 in this particular case, but may apply to other 2013 products.
    It's not just one add-in, but we have seen a few add-ins that go from a happy, Active add-in to a sad, unused Inactive add-in.
    If I have a user who's add-in is getting disabled and they get prompted in their client with the "Add-in problem:  A problem was detected with an add-in and it has been disabled.  [View disabled add-ins...]" the solution is simple enough,
    view those add-ins and if the one you are having trouble with is there, click the option to "Always enable this add-in"
    The trouble I'm having is that not every user gets that prompt for some reason.  And we're seeing a few users who are losing their room finder because the Microsoft Exchange Add-in is being disabled. 
    So.. if I have a "good" user who gets the warning, it's a matter of enabling their add-in and restarting the client, when it disables it again they get the prompt and we just tell it not to disable.  The "bad" users however we enable
    and restart and they never see the warning/option to always enable.  We can enable the add-in again, but for these select few, it keeps disabling them without saying a word.
    I guess my 2 big questions are:
    1- Why doesn't that option show up for everybody?  I'd like to be able to tell our support teams here to cue in on that prompt after enabling, but when it isn't there consistently it is not an effective solution.
    2 - Where or how could I manually have that on the list of add-ins we never disable?  I have found a few mentions of the registry settings, but nothing I see in my registry leads me to believe it will be a simple "find the Microsoft Exchange Add-in"
    setting and change the value X to Y and you are done.  
    I'd like to figure out where to point the user / support to toggle it on their own and I have seen mention of a button under File - that lets you see disabled add-ins, but I don't see that in my client (Outlook 2013 and I'm on the latest) and while a registry
    fix might work, it's not very end user driven or ideal.. but I'd take that over nothing.

    Hi,
    I'm not sure why the option doesn't show up for everybody, however, if you want to specify which add-ins are always enabled, we can use the Outlook Group Policy template (Outlk15.admx) to set the Group Policy option:
    List of managed add-ins.
    The policy is under:
    User Configuration\Administrative Templates\Microsoft Outlook 2013\Miscellaneous
    You will need to find the programmatic identifier (ProgID) for COM add-ins. To obtain the ProgID for an add-in, use Registry Editor on the client computer where the add-in is installed to locate key names under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Outlook\Addins
    or HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\Outlook\Addins.
    For more information, please refer:
    Plan feature customizations in Outlook 2013
    http://technet.microsoft.com/en-us/library/ff631135.aspx
    Use Group Policy to enforce Office 2010 settings
    http://technet.microsoft.com/en-us/library/cc179081(v=office.14).aspx
    Note: This link is for Office 2010, but it also applies to Office 2013.
    Hope this helps.
    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

  • How to install 3 Excel Add-Ins in one deployment ?

    I have 3 excel add-ins which work in conjunction with each other. I want the user to install all 3 at the same time, from one install package. How to do that?
    I am following the steps in "Deploying an Office Solution by Using Windows Installer". 
    This is a single user install.
    Just guessing, I have created a visual studio solution containing the 3 add-in projects as "existing projects".  And the 4th project in this solution is a "setup and deployment" project type. InstallShield Limited Edition Project.
    I am not clear if there should be a different destination folder for the .vsto and .dll.manifest files for each add-in.
    thanks,

    Hi Steve Richter,
    Here is a MSDN article about how to Deploy Multiple Office Solutions in a Single ClickOnce Installer.
    https://msdn.microsoft.com/en-us/library/vstudio/dd465290(v=vs.100).aspx
    The article will tell you the following three points.
    Creating two Office solutions to deploy, and one Office solution as the installer project.
    Modifying the application manifest of the installer project to install two Office solutions.
    Re-signing the application and deployment manifests.
    If you have any other concern regarding this issue, please feel free to let me know.
    Best regards,
    Youjun Tang
    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.

  • On Excel 2013 (64 bit), I can't use the Analysis ToolPack add-ins without a problem and plot the residuals.

    On Excel 2013 (64 bit), I can't use the Analysis ToolPack add-ins without a problem and plot the residuals. It went crash.

    Hi,
    In regarding of the issue, please provide us more information to assist you better.
    Do you mind telling us the Excel version number? Like 15.0.XXXX.1000
    Would you like to collect the Event Log and App Crash dump file to do further troubleshooting?
    As far as I know, if Excel crashes when using Analysis ToolPack add-ins, it usually causes by the >>Faulting module name: mso.dll<<, Please try the following method and check if it is helpful:
    1.Copy/paste the Mso.dll from another PC.
    2.Click "Start" and "Computer."
    3.Double-click "C: Drive," "Windows" and "System32." The System32 folder opens.
    4.Drag the Mso.dll file on your desktop into the System32 folder.
    5.Click "Start," type "cmd" into the search field and press "Enter" to open the Command Prompt.
    6.Type "regsvr32 mso.dll" (without the quotation marks) into the Command Prompt and press "Enter."
    7.Close the Command Prompt and restart your computer.
    Then, if the Faulting module name is not MSO.Dll, you also can upload(Or send to us via email
    [email protected])  the Event Log/App Crash dump file. We'd like to do further troubleshooting.
    Regards,
    George Zhao
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.

  • VSTO add-ins not loading

    We are in the process of moving from 2010 to 2013. There have been a couple VSTO add-ins for Office that used to work fine with 2010 but no longer work in 2013. Trying to enable them through the Add-ins menu does not work, and it says "Not loaded. A
    runtime error occurred during the loading of the COM add-in."

    Hi,
    This issue may be caused by the development environment changed, please see the below articles to troubleshoot this issue. 
    Troubleshooting COM Add-In load failures
    My Office Addin does not Load!
    If you want to do further troubleshooting, such as debug code, I recommend you post the question to VSTO forum:
    https://social.msdn.microsoft.com/Forums/vstudio/en-US/home?forum=vsto
    The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
    George Zhao
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.

Maybe you are looking for