Technology News, Tips & Tricks Blog

The Internet is an amazing resource for when obscure software error messages or technology problems come up and IT admins are ready to yank their hair out. We've decided to give back by sharing some of the issues that we've run into and steps that we took to correct them. Perhaps some of our experiences will help others. If you'd like our engineers to work directly with you to solve your IT problems, please don't hesitate to contact us today!

Office 365 Excel VSTO "downloading file visualstudio.tools.applications.runtime.dll did not succeed" Quickbooks Enterprise Solutions 2016 Statement Writer

You just installed a fresh copy of Windows 10, Microsoft Office 365 and Quickbooks Enterprise Solutions 2016; however you are unable to open Quickbooks Statement Writer reports. You followed all KB articles to register all pre-requisites and set your ISW extension defaults to open with Excel 2016; however you still get an error message "downloading file visualstudio.tools.applications.runtime.dll did not succeed". 

The fix? After hours with Intuit support who have not seen this error before and claimed it's a Windows or Office issue -- I had a hunch to try and install an earlier version of Quickbooks.

Download and install Quickbooks Enterprise Solutions 2013 and open or create at least one ISW report using QES 2013 first. Then, your QB Enterprise Solutions 2016 Statement Writer will work in Excel 2016 without any further errors!

If you need further assistance with Quickbooks Statement Writer 2016 and Office 365 Excel 2016, contact us and we'll be happy to assist.

"SBS 2011 Exchange 2010 Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again Later."

Environment: Small Business Server 2013 with Exchange 2010 SP3 migrated from Small Business Server 2003. Clients using Windows 7 and a mix of Outlook 2010 and Outlook 2013. 

Out of office, when launched in Outlook stopped working with a generic "Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later."

When a domain admin logged in and tested his account in Outlook, it seems only administrators were allowed access to Out of Office.

After fruitlessly searching the Internet, checking permissions and SSL settings on the IIS EWS virtual directory, recreating the user's Outlook profile, checking autodiscover and reviewing logs, I remembered that right before Out of Office stopped working, a user's account had been disabled in Exchange 2010. 

When a mailbox is disabled in Exchange 2010 Console, it gets moved to the Disconnected Mailbox state and container, where it stays there for as long as the retention period is defined, usually 30 days. 

In this case, the user whose mailbox was disabled (or disconnected) had been delegated rights over Out of Office replies. 

The fix was to run "Remove-StoreMailbox -Database databasename -Identity "First LastName" -MailboxState Disabled to delete the disconnected mailbox. After running this command, Out of Office in Outlook started working again for everyone.

For more assistance with proper syntax for removing deleted or disconnected mailboxes in Exchange 2010, see this Microsoft Technet Article: http://technet.microsoft.com/en-us/library/gg181092(v=exchg.141).aspx.

Happy Days! :)


Write a comment

Comments: 0

2008 R2 Backup failing after RAID clone

net stop "System Event Notification Service"

net stop "Background Intelligent Transfer Service"

net stop "COM+ Event System"

net stop "Microsoft Software Shadow Copy Provider"

net stop "Volume Shadow Copy"

cd /d %windir%\system32

net stop vss

net stop swprv

regsvr32 /s ATL.DLL

regsvr32 /s comsvcs.DLL

regsvr32 /s credui.DLLa

regsvr32 /s CRYPTNET.DLL

regsvr32 /s CRYPTUI.DLL

regsvr32 /s dhcpqec.DLL

regsvr32 /s dssenh.DLL

regsvr32 /s eapqec.DLL

regsvr32 /s esscli.DLL

regsvr32 /s FastProx.DLL

regsvr32 /s FirewallAPI.DLL

regsvr32 /s kmsvc.DLL

regsvr32 /s lsmproxy.DLL

regsvr32 /s MSCTF.DLL

regsvr32 /s msi.DLL

regsvr32 /s msxml3.DLL

regsvr32 /s ncprov.DLL

regsvr32 /s ole32.DLL

regsvr32 /s OLEACC.DLL

regsvr32 /s OLEAUT32.DLL

regsvr32 /s PROPSYS.DLL

regsvr32 /s QAgent.DLL

regsvr32 /s qagentrt.DLL

regsvr32 /s QUtil.DLL

regsvr32 /s raschap.DLL

regsvr32 /s RASQEC.DLL

regsvr32 /s rastls.DLL

regsvr32 /s repdrvfs.DLL

regsvr32 /s RPCRT4.DLL

regsvr32 /s rsaenh.DLL

regsvr32 /s SHELL32.DLL

regsvr32 /s shsvcs.DLL

regsvr32 /s /i swprv.DLL

regsvr32 /s tschannel.DLL

regsvr32 /s USERENV.DLL

regsvr32 /s vss_ps.DLL

regsvr32 /s wbemcons.DLL

regsvr32 /s wbemcore.DLL

regsvr32 /s wbemess.DLL

regsvr32 /s wbemsvc.DLL

regsvr32 /s WINHTTP.DLL

regsvr32 /s WINTRUST.DLL

regsvr32 /s wmiprvsd.DLL

regsvr32 /s wmisvc.DLL

regsvr32 /s wmiutils.DLL

regsvr32 /s wuaueng.DLL

sfc /SCANFILE=%windir%\system32\catsrv.DLL

sfc /SCANFILE=%windir%\system32\catsrvut.DLL

sfc /SCANFILE=%windir%\system32\CLBCatQ.DLL

net start "COM+ Event System"

 

The backup operation that started at '‎2014‎-‎07‎-‎11T21:07:19.795000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348075'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

 

Volume Shadow Copy Service error: Volume/disk not connected or not found. Error context: CreateFileW(\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy370,0xc0000000,0x00000003,...). 

 

Operation:

   Processing PostFinalCommitSnapshots

 

Context:

   Execution Context: System Provider

 

HKLM / System / MountedDevices

Tip to prevent Windows spyware from doing serious damage to your computer

by Paul Morrison
 

Did you know that if you simply change your user account privilege on your Windows XP and Windows 7 computers to a limited user account, any viruses that you may accidentally catch will be restricted from doing serious system-wide damage? 

 

This is because Windows doesn't allow non-administrator accounts access to sensitive areas of your computer's registry and system files locations. For example, there are viruses, which disable your ability to run any programs, so you can't run or open any shortcuts, or even your registry.  This can only be done if the virus or rogue security program makes changes in your Windows registry.  Some of these registry areas and keys cannot be changed or modified unless an administrator-level user changes them. 

 

Of course nothing beats a good antivirus program along with up-to-date Windows  and third-party security updates, but user education, combined with running your computer in a defensive manner with a restricted user account is a step in the right direction to ensure a productive, error-free workstation.

 

To have us check and implement corrective measures so that you can take a more proactive and preventive stance against these types of computer infections that cause pop-ups and warnings, and unnecessary computer headaches, please contact us today.  

 

 

 

 

 

 

 

 

pmIT Consulting
Focus on your Business,
not Technology


CALL TOLL FREE
(888) 770-3339


RI/MA (401) 284-7648

NY/CT (212) 945-8461

 

vmware esxi virtualization
Cloud Server Virtualization

Project Financing Available