I am using the virtual machine downloaded from Microsoft's PartnerSource.
I have been successfully developing on it for the past few months, but now I am getting the "Insufficient rights" message when I try to open the development workspace.
Is there something that needs to be renewed (it's being used for development of a plugin only).
The Demo license most likely expired on December 31, 2012.
Go to PartnerSource, where you downloaded the virtual machine application, and near the bottom of the page should be a download for Demo Virtual Machine Licenses. The new license says it expires on December 31, 2013.
Related
I checked to install the BizTalk SDK during my setup, and this is what I now see in the SDK folder:
I don't see the old SDK that came in some prior releases (link). I searched my entire disk for *.odx looking for SDK and didn't find any (other than the VS orchestration Template).
I did a Google search for download BizTalk 2020 SDK and nothing of interest showed up.
BizTalk 2020 Deprecated & Removed List
Samples: Removed from BizTalk Server installation.
So they just aren't available I would say.
'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine. I am getting this in visual studio only after upgrading from 32bit office 2013 to 64bit office 16. I have already installed the 64bit database engine and my published project from IIS is working with the existing access database. I switched debug mode to x64 and remove the references to the old office and replaced them with the new office access. How can I get Visual Studio 2010 to recognize my access database created in access 2013?
Things I have tried:
Installing Microsoft Access Database Engine 2010 Redistributable 64bit version.
Updating the office references in the project.
Debugging in x64 mode
This is a little outside of my normal area of database application design;
it's unclear - you state 2016 Office 64 bit installed but then Access 2010 Redistributable/Runtime 64bit - - so do you have a full license of Access installed?
if you do have the full Access license - try something that is quick: create a brand new database and import that table. Then try the link to this new db.
I had that issue in the past.
install 2007 Office System Driver and restart visual studio.
I've dealt many time with this problem, the solution was ever install one of these:
AccessDatabaseEngine 2007.exe
AccessDatabaseEngine_2010.exe
AccessDatabaseEngine_2016.exe
AccessDatabaseEngine_X64_2010.exe
AccessDatabaseEngine_X64_2016.exe
Most of the time I've solved installing the 2007 one even using 2016 version.
To run 32-bit applications on IIS, you will get the same error. So, from the IIS 7, right-click on the applications' application pool and go to "advanced settings" and change "Enable 32-Bit Applications" to "TRUE".
Restart your website and it should work.
My company has an older, Sharepoint-based website hosted on our development environment (Windows Server 2008), managed by IIS 7. Most of the devs in my environment work on these sites by logging into the environment via Remote Desktop, then using the remote Visual Studio 2012 installation.
I don't love using a remote installation of VS for development work, so for the past several weeks, I've been using the following workaround:
I added the drives of our remote environment as network locations on my local machine.
From there, I gave my local Visual Studio 2015 installation the paths as \\{remote_machine_name}\c$\inetpub... etc.
Visual Studio gave me no complaints, and everything went quite smoothly. Today, I had to work with an IIS installation on my local machine. Our company is preparing to switch from Sharepoint to DNN, so I'm doing some preliminary porting and testing on a local installation of DNN using IIS 10. That's when the error started up.
During the configuration process of DNN, I had to change a few lines in the config file at %systemroot%\System32\inetsrv\config\applicationHost.xml. This was because DNN was giving me 500.19 errors after installation. IIS's support said this was likely related to locking of permission regions in this file, and directed me to change the behavior of any locks that gave errors from "Deny" to "Allow".
I can still work via Remote Desktop, but it would be nice to fix this.
I solved the issue by installing IIS 10 using the downloadable installer. I realized I would have to do this when Visual Studio 2015 would not allow me to create any web projects.
I'm working on a project on my home computer which has Visual Studio 2010 Ultimate on it. I saved the project to a flash drive and did some work on it in the office where Visual Web Developer 2010 is installed.
The project so far just has the login screen which uses a .net login control. It was working on my home computer, and worked on my work computer. But after I brought it back home and tried to run it I get an error saying:
"The database '(my flash drive path)/ASPNETDB.MDF' cannot be opened because it is version 661. This server supports version 655 and earlier. A downgrade path is not supported."
So apparently when I ran it on my work computer it set the database to version 661. What can I do now so I can run it on my home computer? What changes do I need to make to make sure I can work on this project in both places going forward?
Thanks for any help!
The easiest solution would be to update SQL Server (or SQL Server Express, as appropriate) on your home computer to the currently released version.
We recently upgraded our biztalk server 2006R2 to SP1. The problem is that we're having some small issues now, for example the administration console crashes when I browse for a folder if I want to make a file send/receive port.
Any idea what might cause this problem?
I'm having no problems when I browse for a folder with our normal explorer and then copy paste its address into the biztalk folder browser.
Make sure you update towards the latest CU for your service pack.
For BizTalk 2006 R2 with SP1, this is CU4.
See http://support.microsoft.com/kb/2682056 for more information on CU4 for BizTalk 2006 SP1.
If this still does not help, there is a temporary workaround to export/import bindings of existing receive locations/send ports with a FILE adapter. This allows you to still create the ports/locations you need and unblocks the situation.
In any case, if the problem persists, you might want to check with Microsoft about the issue.
That is in case your license includes the extended support option which lasts until 12 July 2016.
If you don't have extended support, the support ended on July 11th 2011 I'm afraid...