We have an Excel workbook which has c# VSTO code in it and two .NET DLLs that sit behind it. The spreadsheet used to work for all users in the organisation.
Recently our IT department had a problem with the OU which deleted all user accounts. The accounts were restored but since then users in our London office have not had the added functionality when they load the spreadsheet. Only users in the New York office and one developer (who has compiled the solution since) can use the functionality.
The files are all held in one directory on a shared network drive.
We have adjusted the manifest to reflect this location.
We have added the directory as a trusted site for code access security on the machine.
The office 2003 PIAs are installed and working as we have another application level extension installed on the machines and this is working correctly.
The .NET framework 3.5 is installed on all machines - as evidenced by the application extension.
VSTO 2005 SE Runtime is installed.
We've followed several how-to's from the internet to no avail, including:
http://msdn.microsoft.com/en-us/library/bb332051.aspx#8
We have a suspicion that there is a security problem as the first line of our code is a logging message and this is not being hit.
No error message is given by excel, the spreadsheet opens and is usable but there is no access to any code and all buttons are disabled.
Any help would be massively appreciated as we've spent many hours trying to figure this out!
Thanks
***************EDIT******************************
Here's the actual cause of the problem from my IT Dept:
...was caused by the Organisational Unit container they were held in being
deleted. This was restored and group memberships and distribution lists access
for individual accounts were then added manually
Turns out the problem was that over the weekend IT had downgraded all our versions of Excel from Professional to Standard. Not all VSTO works in Excel Standard, but it doesn't tell you this, it just doesn't work.
After upgrading we're all happy again!
Cheers
Related
I have an Outlook Add-in(under development) which was working fine on my old system. I decided to migrate to a new system(for better performance), when I have done so(IN DEBUG MODE), I saw that after some time the Add-in is not visible in Outlook(neither in COM AND disabled window).
Specifications I am using:
System type is 64-bit OS, x64-based processor
Microsoft Visual Studio Community 2019 Version 16.5 with .NET framework 4.7.2
Microsoft Office 365(16.012730.20144) 32-bit
Troubleshoots I tried:
1) Checked Build Office solutions, for verifying all items are generating and working properly.
Registry entry is generating correctly.
VSTO file(bin/debug) is getting installed successfully(when I manually double click that)
2) Troubleshooting by Event Viewer:
No error's related to Outlook(as a source).
Possibly related error's:
i) Source - DistributedCOM : The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
and APPID
{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
ii) Other Errors are from source PerfNet and NDIS(Which I suppose is not related to this topic)
3) Troubleshooting by Process Explorer:
Their is no outlook Add-in DLL present in process explorer.
4) Troubleshooting by Process Monitor:
I am new with procmon, so just used some basics like, applied a filter with Outlook process name(including registry, file system, Network, process and thread activities).
And the results were SUCCESS, BUFFER TOO SMALL, NAME NOT FOUND, NO MORE ENTERIES other. Their was nothing I can relate with my issue.
Other Information
After this issue, I made a same new project and it worked fine, but the same happened(Add-in not visible) after some time. And I have done this(Created new project) four times till now. What I observed is, when I create a new Add-in with same name, the issue is same, so I have to choose different name every-time.
I am not able to find any error description for this. So can anybody please tell me what is the issue here OR how I can troubleshoot more(with above tools or new one).
Thanks in advance.
If you don't see your add-in listed in the COM add-ins dialog of Office applications, the problem is related to Windows registry keys required. Read more about them in the Registry entries for VSTO Add-ins article.
It seems something is wrong with your add-in registry entries (maybe permissions). And the issue can be related to Windows/Office bitness. Most probably you had another Office edition (bitness) installed on the old system (or Windows).
I'm creating a WinForm application that needs to get data from an excel spreadsheet. Do I need to install Office 2007 on my DEV PC? What about the PC that will run the WinForm application? Also, can I use Office PIA without installing office on both my DEV and target PC?
Thanks.
first step implement method to get data from excel files
These Question
after implement you dosent need to install excel if u need add dll you most create embed resource your dll with your executable file
this answer help
Code project Example
For development
Configuring a Computer to Develop Office Solutions
And for end users:
Office Solution Prerequisites for Deployment
How to: Install Prerequisites on End User Computers to Run Office Solutions
I have a PowerPoint 2010 application-level add-in developed using VS2012 and VSTO. It works with PowerPoint 2007 too. I built an installer for it using the (terrible) InstallShield LE crippleware provided with VS2012. I've been able to install it on various test machines, but now that I'm trying to deploy it to a client, they can't install it on some machines.
One user at the client's site can install it, but that user works in IT and has admin rights on his machine. However, when the IT admins try to install it on a "normal" user's machine, the install seems to go OK but the add-in is not loaded by PowerPoint.
The "COM add-ins" dialog shows the message:
Load behavior: Not loaded. The Managed Add-in Loader failed to initialize.
[In case it's relevant, this client uses Office 2007. Note however that it works OK on Office 2007 both on my test hardware and for that one user at the client.]
Is there anything I can do to figure out why? Is there anything obvious that I should be doing as part of the installation? Clearly the registry entries are being set, because the add-in is listed in the COM Add-ins dialog. And I assume that all the required files are installed, because the installer works fine on other machines.
I guess it may be a security-related issue. I should note that I'm not doing anything security-wise, and I don't think the InstallShield thing is doing anything helpful in this regard. I don't know whether it's necessary to digitally sign my code (I haven't), or somehow set some security policy stuff (I wouldn't know how). I've seen some stuff on-line about using CasPol (?) to apply security settings to add-ins, but that applied to older versions of VS and/or ClickOnce, and I wasn't sure whether I needed any of that.
It turns out that the VSTO runtime is not installed with Office 2007 (it is installed with Office 2010). The IT user who could load the add-in already had it because he'd installed something else that included it (I guess). The other users did not have it.
So, I updated my installer to include it, and it now works.
I have a Problem with an very old ASP.NET 1.1 application. I cannot open (load) it in Visual Studio 2003 (on a Win 2003 server) any more. I get an error message,that the component for the communication with the "Front Page - Server Extensions" cannot be found (I use a german VS 2003, so I have not the exact English message). The extensions are installed. That can be the reason for that respectively how can I solve this problem.
Another Question: Is there a possibility to open an ASP.NET 1.1 application in VS 2010? Tthe upgrade wizard tries to convert it, but the conversion results in errors.
If I remember correctly you need to create a virtual directory in IIS that maps to the directory containing the ASP.NET project - you may need to tweak the solution file in the process so the ASP.NET project path matches your IIS virtual directory path(e.g. http://localhost/VIRTUALDIRECTORY/ASP.NETProject.csproj).
Ensure any .suo and .webinfo files within the solution and project folders are deleted before opening the "tweaked" solution file.
"Cannot find the components for communicating with FrontPage server exstensions". I believe this might be the error message.
Logon as another user and see if 'they' get the same problem. If the problem goes away as a different user. Destroying your local profile and then rebuilding it. Remember to back it up first as you will lose everything associated with this profile.
If that doesn't work then you should try the following (It concerns removing Beta 2 of VS 2002/2003, but the line that interested me was): http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q312383
Hope that helps.
An add-in we make is causing the above problem on a Windows 2003 server, without any obvious cause. Both Word and the add-in appear to work correctly yet the message comes up and Word wants to disable the add-in. I have run with VSTO_SUPPRESSDISPLAYALERTS=0 and no messages come up. On my machine (XP) the problem does not occur.
Any suggestions as to what is going on?
Since you say that it's working fine on your WinXP machine, I advise you to download and install the VSTO Power Tools and run the installed VSTO Troubleshooter application to assert if any dependency is missing on the Windows 2003 Server machine. If no errors are found by the troubleshooter check any third-parties dependencies that may exist.
By the way, welcome to SO.