Visio does not have an office dependency (at any version I have seen).
al
Hi,
As far as I know, you can work Visio 2013 with Office 2013.
Microsoft recommends using the same version of the work.
Regards,
George Zhao
TechNet Community Support
I don't know about Visio 2013, but Visio 2010 installed the 2010 version of the Access Database Engine (ACE 14.0).
So if you installed Visio 2010 together with another version of Office, all Access applications just crash as soon they use the DB engine.
Microsoft recommends never mix versions of Office (neither with 2007 - 2010 - 2013 - ... neither between 32 bits and 64 bits). Visio, Project, Lync, Outlook, InfoPath,... are all parts of the Office-family (even if they are not in any Office suite).
cfr. http://answers.microsoft.com/en-us/office/forum/office_2010-access/installed-visio-2010-with-access-2007-applications/c1fe7725-d2a5-4f60-b172-062a05210f88
Take a look at this Microsoft KB
It has one reference to Visio and the support / install order of Office.
Now with that said, regardless of 2010 vs. 2013, you can NOT mix 32-bit or 64-bit versions of Office.
For example, lets say I installed Office 2010 SP2 64-bit
(FYI... How to determine Office 2010 SP file version KB2121559)
I then want to install Visio 2013 32-bit, the install will not work.
You cant mix 32-bit and 64-bit versions of Office Products.
TechNet article explains more...TechNet
(FYI...A few more people are asking the same question...)
(How to determine which version 32-bit or 64-bit version of Office is installed Stackoverflow.com)
Above article is dependent on Full Office being installed... You can also query the DisplayName REG_SZ key as well, it will report back the Office version.
Registry Location:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
Look for the Office GUID in my example for 2010 64-bit SP2....
...................................................
...................................................
Now with the above said, below are notes from one of our desktop support techs in regards to issues we have seen internally running Office 2010 32-bit SP1 and SP2 on Win 7 x64 Enterprise with Visio 2013.....
Office interops. The ability for office and other applications to communicate with other office apps.
The first instance today: User sends corporate communications from word using the send to mail recipient feature. After visio 2013 installed, he received a message stating that word could not communicate with outlook, to either repair office or check the server. Office was repaired, new outlook profile created. After research, discovered the office is sensitive to various versions in regards to interops. Discovered that Visio 2013 was installed around the time user experienced issues. After uninstalling visio, when launching word it began to configure (like for a first time install), the send mail to recipient feature began working. This probably will affect anyone with visio 2013. Visio 2010 was not reinstalled afterwards, as user barely uses it and was hesitant. Installation files are still on his machine in the event that he does need it reinstalled. Office version is 14.0.7109.5000 User is on Office 2010 SP2
The second instance today: Teammate stopped working 3 weeks ago according to user. After working through several support groups here and working with the vendor support, the vendor noted that some dlls from the application were not registered. If that didnt fix it they suggested a reimage. After registering the dlls, issue persisted. After further troubleshooting, determine that the feature that did not work for user consisted of teammate downloading information from a system, parsing it, then outputting it to a word document. The application provided no error of any sort, it just would never get to the word document portion. Discovered that Visio 2013 was installed around the time that the issue occurred, and that the issue appeared to be related to office interops. I uninstalled Visio 2013 and it began working as designed. In both cases Visio 2013 had been installed on 11/25/2014 (I didnt see any corporate communication about an upgrade, but maybe one took place?). Office version is 14.0.7109.5000 User is on Office 2010 SP2
Im not sure if you have much experience with interops, but pretty much anytime you want to communicate with a different office application, that is how it is done. Per my reading through various Microsoft KBs and support forums, different version interops do not play well together always. It appears that these applications are trying to communicate to office 2010 (v 14) using 2013 (v15) interops, only after installing visio 2013 professional. Users were both Windows 7 x64. We also had a group of several users who also ran into issues with sharepoint not working in any browser, turned out the problem was Visio 2013 was well....
Feel free to research more, but my own research comes down with having both 2010 and 2013 interops on the machine. To simplify it, the applications and office apps are being told to communicate using office 2013, and but only listen in 2010, causing problems. Its not causing problems with every simple interop, or we would see it far more widespread, but we are going to continue to see the ghost issues where Visio 2013 is the root cause, but nothing is really going to scream it.
- Edited by Win7 Guru Wednesday, January 07, 2015 2:21 PM edit
Take a look at this Microsoft KB
It has one reference to Visio and the support / install order of Office.
Now with that said, regardless of 2010 vs. 2013, you can NOT mix 32-bit or 64-bit versions of Office.
For example, lets say I installed Office 2010 SP2 64-bit
(FYI... How to determine Office 2010 SP file version KB2121559)
I then want to install Visio 2013 32-bit, the install will not work.
You cant mix 32-bit and 64-bit versions of Office Products.
TechNet article explains more...TechNet
(FYI...A few more people are asking the same question...)
(How to determine which version 32-bit or 64-bit version of Office is installed Stackoverflow.com)
Above article is dependent on Full Office being installed... You can also query the DisplayName REG_SZ key as well, it will report back the Office version.
Registry Location:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
Look for the Office GUID in my example for 2010 64-bit SP2....
...................................................
...................................................
Now with the above said, below are notes from one of our desktop support techs in regards to issues we have seen internally running Office 2010 32-bit SP1 and SP2 on Win 7 x64 Enterprise with Visio 2013.....
Office interops. The ability for office and other applications to communicate with other office apps.
The first instance today: User sends corporate communications from word using the send to mail recipient feature. After visio 2013 installed, he received a message stating that word could not communicate with outlook, to either repair office or check the server. Office was repaired, new outlook profile created. After research, discovered the office is sensitive to various versions in regards to interops. Discovered that Visio 2013 was installed around the time user experienced issues. After uninstalling visio, when launching word it began to configure (like for a first time install), the send mail to recipient feature began working. This probably will affect anyone with visio 2013. Visio 2010 was not reinstalled afterwards, as user barely uses it and was hesitant. Installation files are still on his machine in the event that he does need it reinstalled. Office version is 14.0.7109.5000 User is on Office 2010 SP2
The second instance today: Teammate stopped working 3 weeks ago according to user. After working through several support groups here and working with the vendor support, the vendor noted that some dlls from the application were not registered. If that didnt fix it they suggested a reimage. After registering the dlls, issue persisted. After further troubleshooting, determine that the feature that did not work for user consisted of teammate downloading information from a system, parsing it, then outputting it to a word document. The application provided no error of any sort, it just would never get to the word document portion. Discovered that Visio 2013 was installed around the time that the issue occurred, and that the issue appeared to be related to office interops. I uninstalled Visio 2013 and it began working as designed. In both cases Visio 2013 had been installed on 11/25/2014 (I didnt see any corporate communication about an upgrade, but maybe one took place?). Office version is 14.0.7109.5000 User is on Office 2010 SP2
Im not sure if you have much experience with interops, but pretty much anytime you want to communicate with a different office application, that is how it is done. Per my reading through various Microsoft KBs and support forums, different version interops do not play well together always. It appears that these applications are trying to communicate to office 2010 (v 14) using 2013 (v15) interops, only after installing visio 2013 professional. Users were both Windows 7 x64. We also had a group of several users who also ran into issues with sharepoint not working in any browser, turned out the problem was Visio 2013 was well....
Feel free to research more, but my own research comes down with having both 2010 and 2013 interops on the machine. To simplify it, the applications and office apps are being told to communicate using office 2013, and but only listen in 2010, causing problems. Its not causing problems with every simple interop, or we would see it far more widespread, but we are going to continue to see the ghost issues where Visio 2013 is the root cause, but nothing is really going to scream it.
- Edited by Win7 Guru Wednesday, January 07, 2015 2:21 PM edit
Take a look at this Microsoft KB
It has one reference to Visio and the support / install order of Office.
Now with that said, regardless of 2010 vs. 2013, you can NOT mix 32-bit or 64-bit versions of Office.
For example, lets say I installed Office 2010 SP2 64-bit
(FYI... How to determine Office 2010 SP file version KB2121559)
I then want to install Visio 2013 32-bit, the install will not work.
You cant mix 32-bit and 64-bit versions of Office Products.
TechNet article explains more...TechNet
(FYI...A few more people are asking the same question...)
(How to determine which version 32-bit or 64-bit version of Office is installed Stackoverflow.com)
Above article is dependent on Full Office being installed... You can also query the DisplayName REG_SZ key as well, it will report back the Office version.
Registry Location:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
Look for the Office GUID in my example for 2010 64-bit SP2....
...................................................
...................................................
Now with the above said, below are notes from one of our desktop support techs in regards to issues we have seen internally running Office 2010 32-bit SP1 and SP2 on Win 7 x64 Enterprise with Visio 2013.....
Office interops. The ability for office and other applications to communicate with other office apps.
The first instance today: User sends corporate communications from word using the send to mail recipient feature. After visio 2013 installed, he received a message stating that word could not communicate with outlook, to either repair office or check the server. Office was repaired, new outlook profile created. After research, discovered the office is sensitive to various versions in regards to interops. Discovered that Visio 2013 was installed around the time user experienced issues. After uninstalling visio, when launching word it began to configure (like for a first time install), the send mail to recipient feature began working. This probably will affect anyone with visio 2013. Visio 2010 was not reinstalled afterwards, as user barely uses it and was hesitant. Installation files are still on his machine in the event that he does need it reinstalled. Office version is 14.0.7109.5000 User is on Office 2010 SP2
The second instance today: Teammate stopped working 3 weeks ago according to user. After working through several support groups here and working with the vendor support, the vendor noted that some dlls from the application were not registered. If that didnt fix it they suggested a reimage. After registering the dlls, issue persisted. After further troubleshooting, determine that the feature that did not work for user consisted of teammate downloading information from a system, parsing it, then outputting it to a word document. The application provided no error of any sort, it just would never get to the word document portion. Discovered that Visio 2013 was installed around the time that the issue occurred, and that the issue appeared to be related to office interops. I uninstalled Visio 2013 and it began working as designed. In both cases Visio 2013 had been installed on 11/25/2014 (I didnt see any corporate communication about an upgrade, but maybe one took place?). Office version is 14.0.7109.5000 User is on Office 2010 SP2
Im not sure if you have much experience with interops, but pretty much anytime you want to communicate with a different office application, that is how it is done. Per my reading through various Microsoft KBs and support forums, different version interops do not play well together always. It appears that these applications are trying to communicate to office 2010 (v 14) using 2013 (v15) interops, only after installing visio 2013 professional. Users were both Windows 7 x64. We also had a group of several users who also ran into issues with sharepoint not working in any browser, turned out the problem was Visio 2013 was well....
Feel free to research more, but my own research comes down with having both 2010 and 2013 interops on the machine. To simplify it, the applications and office apps are being told to communicate using office 2013, and but only listen in 2010, causing problems. Its not causing problems with every simple interop, or we would see it far more widespread, but we are going to continue to see the ghost issues where Visio 2013 is the root cause, but nothing is really going to scream it.
- Edited by Win7 Guru Wednesday, January 07, 2015 2:21 PM edit
Take a look at this Microsoft KB
It has one reference to Visio and the support / install order of Office.
Now with that said, regardless of 2010 vs. 2013, you can NOT mix 32-bit or 64-bit versions of Office.
For example, lets say I installed Office 2010 SP2 64-bit
(FYI... How to determine Office 2010 SP file version KB2121559)
I then want to install Visio 2013 32-bit, the install will not work.
You cant mix 32-bit and 64-bit versions of Office Products.
TechNet article explains more...TechNet
(FYI...A few more people are asking the same question...)
(How to determine which version 32-bit or 64-bit version of Office is installed Stackoverflow.com)
Above article is dependent on Full Office being installed... You can also query the DisplayName REG_SZ key as well, it will report back the Office version.
Registry Location:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
Look for the Office GUID in my example for 2010 64-bit SP2....
...................................................
...................................................
Now with the above said, below are notes from one of our desktop support techs in regards to issues we have seen internally running Office 2010 32-bit SP1 and SP2 on Win 7 x64 Enterprise with Visio 2013.....
Office interops. The ability for office and other applications to communicate with other office apps.
The first instance today: User sends corporate communications from word using the send to mail recipient feature. After visio 2013 installed, he received a message stating that word could not communicate with outlook, to either repair office or check the server. Office was repaired, new outlook profile created. After research, discovered the office is sensitive to various versions in regards to interops. Discovered that Visio 2013 was installed around the time user experienced issues. After uninstalling visio, when launching word it began to configure (like for a first time install), the send mail to recipient feature began working. This probably will affect anyone with visio 2013. Visio 2010 was not reinstalled afterwards, as user barely uses it and was hesitant. Installation files are still on his machine in the event that he does need it reinstalled. Office version is 14.0.7109.5000 User is on Office 2010 SP2
The second instance today: Teammate stopped working 3 weeks ago according to user. After working through several support groups here and working with the vendor support, the vendor noted that some dlls from the application were not registered. If that didnt fix it they suggested a reimage. After registering the dlls, issue persisted. After further troubleshooting, determine that the feature that did not work for user consisted of teammate downloading information from a system, parsing it, then outputting it to a word document. The application provided no error of any sort, it just would never get to the word document portion. Discovered that Visio 2013 was installed around the time that the issue occurred, and that the issue appeared to be related to office interops. I uninstalled Visio 2013 and it began working as designed. In both cases Visio 2013 had been installed on 11/25/2014 (I didnt see any corporate communication about an upgrade, but maybe one took place?). Office version is 14.0.7109.5000 User is on Office 2010 SP2
Im not sure if you have much experience with interops, but pretty much anytime you want to communicate with a different office application, that is how it is done. Per my reading through various Microsoft KBs and support forums, different version interops do not play well together always. It appears that these applications are trying to communicate to office 2010 (v 14) using 2013 (v15) interops, only after installing visio 2013 professional. Users were both Windows 7 x64. We also had a group of several users who also ran into issues with sharepoint not working in any browser, turned out the problem was Visio 2013 was well....
Feel free to research more, but my own research comes down with having both 2010 and 2013 interops on the machine. To simplify it, the applications and office apps are being told to communicate using office 2013, and but only listen in 2010, causing problems. Its not causing problems with every simple interop, or we would see it far more widespread, but we are going to continue to see the ghost issues where Visio 2013 is the root cause, but nothing is really going to scream it.
- Edited by Win7 Guru Wednesday, January 07, 2015 2:21 PM edit
Take a look at this Microsoft KB
It has one reference to Visio and the support / install order of Office.
Now with that said, regardless of 2010 vs. 2013, you can NOT mix 32-bit or 64-bit versions of Office.
For example, lets say I installed Office 2010 SP2 64-bit
(FYI... How to determine Office 2010 SP file version KB2121559)
I then want to install Visio 2013 32-bit, the install will not work.
You cant mix 32-bit and 64-bit versions of Office Products.
TechNet article explains more...TechNet
(FYI...A few more people are asking the same question...)
(How to determine which version 32-bit or 64-bit version of Office is installed Stackoverflow.com)
Above article is dependent on Full Office being installed... You can also query the DisplayName REG_SZ key as well, it will report back the Office version.
Registry Location:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
Look for the Office GUID in my example for 2010 64-bit SP2....
...................................................
...................................................
Now with the above said, below are notes from one of our desktop support techs in regards to issues we have seen internally running Office 2010 32-bit SP1 and SP2 on Win 7 x64 Enterprise with Visio 2013.....
Office interops. The ability for office and other applications to communicate with other office apps.
The first instance today: User sends corporate communications from word using the send to mail recipient feature. After visio 2013 installed, he received a message stating that word could not communicate with outlook, to either repair office or check the server. Office was repaired, new outlook profile created. After research, discovered the office is sensitive to various versions in regards to interops. Discovered that Visio 2013 was installed around the time user experienced issues. After uninstalling visio, when launching word it began to configure (like for a first time install), the send mail to recipient feature began working. This probably will affect anyone with visio 2013. Visio 2010 was not reinstalled afterwards, as user barely uses it and was hesitant. Installation files are still on his machine in the event that he does need it reinstalled. Office version is 14.0.7109.5000 User is on Office 2010 SP2
The second instance today: Teammate stopped working 3 weeks ago according to user. After working through several support groups here and working with the vendor support, the vendor noted that some dlls from the application were not registered. If that didnt fix it they suggested a reimage. After registering the dlls, issue persisted. After further troubleshooting, determine that the feature that did not work for user consisted of teammate downloading information from a system, parsing it, then outputting it to a word document. The application provided no error of any sort, it just would never get to the word document portion. Discovered that Visio 2013 was installed around the time that the issue occurred, and that the issue appeared to be related to office interops. I uninstalled Visio 2013 and it began working as designed. In both cases Visio 2013 had been installed on 11/25/2014 (I didnt see any corporate communication about an upgrade, but maybe one took place?). Office version is 14.0.7109.5000 User is on Office 2010 SP2
Im not sure if you have much experience with interops, but pretty much anytime you want to communicate with a different office application, that is how it is done. Per my reading through various Microsoft KBs and support forums, different version interops do not play well together always. It appears that these applications are trying to communicate to office 2010 (v 14) using 2013 (v15) interops, only after installing visio 2013 professional. Users were both Windows 7 x64. We also had a group of several users who also ran into issues with sharepoint not working in any browser, turned out the problem was Visio 2013 was well....
Feel free to research more, but my own research comes down with having both 2010 and 2013 interops on the machine. To simplify it, the applications and office apps are being told to communicate using office 2013, and but only listen in 2010, causing problems. Its not causing problems with every simple interop, or we would see it far more widespread, but we are going to continue to see the ghost issues where Visio 2013 is the root cause, but nothing is really going to scream it.
- Edited by Win7 Guru Wednesday, January 07, 2015 2:21 PM edit
Take a look at this Microsoft KB
It has one reference to Visio and the support / install order of Office.
Now with that said, regardless of 2010 vs. 2013, you can NOT mix 32-bit or 64-bit versions of Office.
For example, lets say I installed Office 2010 SP2 64-bit
(FYI... How to determine Office 2010 SP file version KB2121559)
I then want to install Visio 2013 32-bit, the install will not work.
You cant mix 32-bit and 64-bit versions of Office Products.
TechNet article explains more...TechNet
(FYI...A few more people are asking the same question...)
(How to determine which version 32-bit or 64-bit version of Office is installed Stackoverflow.com)
Above article is dependent on Full Office being installed... You can also query the DisplayName REG_SZ key as well, it will report back the Office version.
Registry Location:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
Look for the Office GUID in my example for 2010 64-bit SP2....
...................................................
...................................................
Now with the above said, below are notes from one of our desktop support techs in regards to issues we have seen internally running Office 2010 32-bit SP1 and SP2 on Win 7 x64 Enterprise with Visio 2013.....
Office interops. The ability for office and other applications to communicate with other office apps.
The first instance today: User sends corporate communications from word using the send to mail recipient feature. After visio 2013 installed, he received a message stating that word could not communicate with outlook, to either repair office or check the server. Office was repaired, new outlook profile created. After research, discovered the office is sensitive to various versions in regards to interops. Discovered that Visio 2013 was installed around the time user experienced issues. After uninstalling visio, when launching word it began to configure (like for a first time install), the send mail to recipient feature began working. This probably will affect anyone with visio 2013. Visio 2010 was not reinstalled afterwards, as user barely uses it and was hesitant. Installation files are still on his machine in the event that he does need it reinstalled. Office version is 14.0.7109.5000 User is on Office 2010 SP2
The second instance today: Teammate stopped working 3 weeks ago according to user. After working through several support groups here and working with the vendor support, the vendor noted that some dlls from the application were not registered. If that didnt fix it they suggested a reimage. After registering the dlls, issue persisted. After further troubleshooting, determine that the feature that did not work for user consisted of teammate downloading information from a system, parsing it, then outputting it to a word document. The application provided no error of any sort, it just would never get to the word document portion. Discovered that Visio 2013 was installed around the time that the issue occurred, and that the issue appeared to be related to office interops. I uninstalled Visio 2013 and it began working as designed. In both cases Visio 2013 had been installed on 11/25/2014 (I didnt see any corporate communication about an upgrade, but maybe one took place?). Office version is 14.0.7109.5000 User is on Office 2010 SP2
Im not sure if you have much experience with interops, but pretty much anytime you want to communicate with a different office application, that is how it is done. Per my reading through various Microsoft KBs and support forums, different version interops do not play well together always. It appears that these applications are trying to communicate to office 2010 (v 14) using 2013 (v15) interops, only after installing visio 2013 professional. Users were both Windows 7 x64. We also had a group of several users who also ran into issues with sharepoint not working in any browser, turned out the problem was Visio 2013 was well....
Feel free to research more, but my own research comes down with having both 2010 and 2013 interops on the machine. To simplify it, the applications and office apps are being told to communicate using office 2013, and but only listen in 2010, causing problems. Its not causing problems with every simple interop, or we would see it far more widespread, but we are going to continue to see the ghost issues where Visio 2013 is the root cause, but nothing is really going to scream it.
- Edited by Win7 Guru Wednesday, January 07, 2015 2:21 PM edit
This topic is archived. No further replies will be accepted.
Other recent topics
