Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I am getting this error everytime I open MS Excel / Word. I tried unchecking the checkbox "Ignore other applications that use Dynamic Data Exchange (DDE)" in Advanced options, but still I'm getting this error. Any suggestions?
i just feel like to share what worked for me as this thing really annoyed me for several months.
i researched on several websites/sources and all the solutions i have come across do not work. such solutions include but are not limited to:
1) clearing of the checkbox of that DDE thing.
2) registry edit (too risky for non-savvy PC users like me)
3) unchecking of "run as administrator"
but just recently, i uninstalled a program called Tune Up utilities and then the annoying error was gone. so what i would suggest for others is to check which programs do you think are incompatible with your MS Office. then uninstall that (those) program (s).
hope that helps.
best,
filousophe
Hey,
You need to deactivate all add-ins
http://office.microsoft.com/en-us/excel-help/enable-or-disable-add-ins-in-office-programs-HA010034127.aspx
one of them seems to be having an issue.
I solved it by right-clicking the document and choosing Open With... and noticed there were two Microsoft Word choices. I chose the second choice. And it worked and fixed the issue in the future.
If anyone can explain this in more detail, please do!
(I was using Windows 7 and Microsoft Word 2002.)
I came across this issue today. An update to the Office Compatibility Pack that was still on a computer caused the default program for .docx and .xlsx files to be the Microsoft Open XML Converter program and make the "Default Programs" in Control Panel think that Excel and Word were actually the Microsoft Open XML Converter program as well.
Uninstalling the Office Compatibility Pack in Programs and Features and then a simple reboot fixed the issue.
"There was a problem sending the command to the program" has appeared on my Windows 7 machine in the first week of September, 2013. I tried to repair MS Office 2003 from within the Program and Features, but repair and re-installation have failed due to "unspecified error". Windows application logs showed that the repair has failed due to "protected keys" in the Registry. Windows Installer was blocked from writing to MS Office keys. My antivirus and firewall were turned off. On the Uninstall or Change programs list I noticed September 6, 2013 entry "Microsoft Office 2003 Interoperative Assembly" from Microsoft. I didn't install this, so I uninstalled that item. Afterwards, both Excel and Word no longer showed an error, and files are opening normally.
KrysK
Uninstalling the Office Compatibility Pack in Programs and Features and then a simple reboot fixed the issue.
I am running Office 2013 - Win 7. Un-istalling the Compatibility pack for Windows 2007 AND rebooting, took care of my issue. After the reboot the .xlsx extension default is changed form XML converter to EXCEL. If you need the compatibility pack you may be able to just change the "Default Program" through Control Panel associated with the xlsx extension.
Related
When I am trying do deploy/debug etc. my hosted app :
I am writing good credenials, and then something strange happen what happen only on one machine (sad to say it's only mine).
After putting sign in button (keep me signed checked/uncheced 100 times) it's would not login, but open sharepoint 2013 site in this window:
What I did:
reinstall visual studio
update visual studio
restart computers
clear cookies/catche etc.
Solved accidentally by installing CKSdev tools but only for one run...
It once happened to me that while it was a debug version all credentials were always rejected. I still don't really know why (it was a big project, not fully made by myself), but as a temporary solution you may try hardcoding your credentials. It's not perfect, but it may be working ;)
The one and only solution was reinstaling the windows, i didn find any other solution
edit:
After the newest updates this problem is solved
I've been working intermittently on an Excel spreadsheet for a customer that does some pretty intense calculations. We implemented a security procedure using VBA... At first the requirements were relatively simple, and the overall lack of security in a spreadsheet was discussed and well understood.
Since then the customer has decided that he would like to have the sheet a bit more secure. Under normal circumstances I would simply disable the developer menu via code. Unfortunately I just recently found out that the customer, and many of his customers, are using Mac Office. (There are some customers that are even using 2008 and they found out the hard way that 2008 stopped supporting VBA)
My question is; is it possible to disable access to the Visual Basic editor in Mac Office in versions Pre 2008, and versions 2011 and after since from the research I've done so far points to a return of VBA support in Mac Office in 2011.
Unfortunately I do not have access to a Mac Office version to even really look through the application and or/test different solutions. In Windows it is possible to right click the VBA project and choose protection from the VBAProject Properties and choose "Lock project for viewing". Does this option exist and is it effective in Mac Office?
Any help/suggestions would be greatly appreciated.
I'm pretty sure you can lock projects in Mac Office the same way you can in Windows. Keep in mind that a project that has been locked in one version of Excel cannot be unlocked with a different version. So, if your customer needs to be able to unlock, they will need to use the same version of Excel you used to lock it.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I am getting this error everytime I open MS Excel / Word. I tried unchecking the checkbox "Ignore other applications that use Dynamic Data Exchange (DDE)" in Advanced options, but still I'm getting this error. Any suggestions?
i just feel like to share what worked for me as this thing really annoyed me for several months.
i researched on several websites/sources and all the solutions i have come across do not work. such solutions include but are not limited to:
1) clearing of the checkbox of that DDE thing.
2) registry edit (too risky for non-savvy PC users like me)
3) unchecking of "run as administrator"
but just recently, i uninstalled a program called Tune Up utilities and then the annoying error was gone. so what i would suggest for others is to check which programs do you think are incompatible with your MS Office. then uninstall that (those) program (s).
hope that helps.
best,
filousophe
Hey,
You need to deactivate all add-ins
http://office.microsoft.com/en-us/excel-help/enable-or-disable-add-ins-in-office-programs-HA010034127.aspx
one of them seems to be having an issue.
I solved it by right-clicking the document and choosing Open With... and noticed there were two Microsoft Word choices. I chose the second choice. And it worked and fixed the issue in the future.
If anyone can explain this in more detail, please do!
(I was using Windows 7 and Microsoft Word 2002.)
I came across this issue today. An update to the Office Compatibility Pack that was still on a computer caused the default program for .docx and .xlsx files to be the Microsoft Open XML Converter program and make the "Default Programs" in Control Panel think that Excel and Word were actually the Microsoft Open XML Converter program as well.
Uninstalling the Office Compatibility Pack in Programs and Features and then a simple reboot fixed the issue.
"There was a problem sending the command to the program" has appeared on my Windows 7 machine in the first week of September, 2013. I tried to repair MS Office 2003 from within the Program and Features, but repair and re-installation have failed due to "unspecified error". Windows application logs showed that the repair has failed due to "protected keys" in the Registry. Windows Installer was blocked from writing to MS Office keys. My antivirus and firewall were turned off. On the Uninstall or Change programs list I noticed September 6, 2013 entry "Microsoft Office 2003 Interoperative Assembly" from Microsoft. I didn't install this, so I uninstalled that item. Afterwards, both Excel and Word no longer showed an error, and files are opening normally.
KrysK
Uninstalling the Office Compatibility Pack in Programs and Features and then a simple reboot fixed the issue.
I am running Office 2013 - Win 7. Un-istalling the Compatibility pack for Windows 2007 AND rebooting, took care of my issue. After the reboot the .xlsx extension default is changed form XML converter to EXCEL. If you need the compatibility pack you may be able to just change the "Default Program" through Control Panel associated with the xlsx extension.
I am trying to setup Subsonic ActiveRecord in a web application in Visual Studio 2010 beta 2. In any scenario I get the same error:
Warning 1 The path 'D:\Work\Project\tt\SQLServer.ttinclude' must be either local to this computer or part of your trusted zone.
Everything works just fine on the same machine with VS 2008.
Does anyone else have this problem? Is it supposed to work with VS 2010 and .net 4.0 or I should stick with vs 2008 for the time beeing?
Ok, figured out one solution. I'm sure there could be others out there. I got around this issue by opening VS.NET 2010 and selecting 'Tools | Extenstion Manager' and clicking on the "Online Gallery" option. I selected the Tangible T4 Template Editor and installed the plugin/extension. If you don't see the extension then try sorting by highest rated or perform a search for it.
I closed VS and re-opened the tt file after closing it and voila! No more compile errors ;)
HTH
I had this exact same error "must be either local to this computer or part of your trusted zone", I did get it to work without adding anything to the Trusted Zone, the only thing I did was remove the "language" setting in the SQLServer.ttinclude file, and then edit the files a little (add a space, remove it, save etc.) not sure if this was enough to convince it to build properly the next time I did "Run Custom Tool" on each of the T4 files, but it worked, phew!
I recently hit this on a new Windows 7 (64 bit) install. Once you download the archive, right click on the file and select Unblock before you extract it and all is well. Note that this applies to the VS 2010 release as well.
Add the network share to Trusted sites. First uncheck the Require server verification (https:) for all sites in this zone checkbox.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I'm curious to know how other SharePoint developers setup their dev workstations.
My current setup:
Desktop with Server 2008 (only for Hyper-V, was using Vista before)
Use Visual Studio 2008 on local machine for dev work
Keep a local copy of SharePoint DLLs for referencing, no local SharePoint install
Run SharePoint in a Server 2003 VM hosted on my local machine
I develop all my SharePoint changes as a WSP and install them into the VM for testing. I don't run code in debug mode, but do write lots of trace statements to watch what my code is doing.
Also, when I'm making quick changes, I normally don't reinstall the entire WSP. I just recompile whatever DLL I changed and copy it into the GAC in my SharePoint VM, then reset IIS (normally writing Web Parts).
I know things would be easier if I ran SharePoint locally, but I'm normally working on more than one project at a time and don't want things to interfere.
Definitely prefer working in VM with SharePoint directly as I can debug into processes correctly, also I have a build script that will either redeploy my entire solution or let me just refresh the GAC.
I do all my development work on one of my VMware images. Since I try to do my SharePoint work in a TDD style I run a lot of tests and then the remote stuff just don't make sense to me.
The single item that have helped me the most is the post build event in visual studio, it is really amazing all the things you can do with a bit of scripting.
Running SharePoint/VS on the same server (either physical or virtual) will get you up and running quickly, but personally I don't think its the way to go.
In addition to what you describe (local VS/SharePoint running in VM's) then a few tips that may make your life easier.
1) Deploy to the bin directory rather than the GAC, then to update all you have to do is copy over your dll/pdb's in a post build batch file - don't think you can do that automatically if they are in the GAC on a remote machine can you?
2) Look at remote debugging - it can be a little bit of a pain to get working first but the effort is worth it! key tip is you need to use the same username/password on both the local and remote machine.
This page is related -
Debugging SharePoint 2007 Code