I'm getting an error when trying to install sharepoint 2010 on the server (windows server 2008 R2 64bit). The prerequisites installed fine, any ideas what this means?
BEX64 event means a problem with DEP, Data Execution Prevention, or buffer overflow.
It's surely a problem in the downloaded software. You can try to turn off DEP temporary.
I was having the same issue. I tried the install on 5 different servers and got the same result so it wasn't a problem on the server - it seems to be a corrupt download file on the MS Volume Licensing site. When I ran the download using the download manager instead of the web browser download, it kept saying the file was corrupted after the download finished (tried this a few times with the same result). My solution was to download the software from the Trial download site, then use the key I had from the VL download.
The URL for the trial is here
I spent weeks trying to get this to work. And it turned out to be group policy not allowing me to install. So in case that helps anyone else with the same issue.
Attempt the install, then check the windows event viewer and look for any software warnings.
Start -> Search for "Event Viewer" -> Windows Logs -> Application,
Look for an error with a yellow Esclamation mark in a triangle that occored around the same time as the install. And see why it didn't let you install.
Mine said this:
Access to C:\Users\[username]\AppData\Local\Temp\ose00020.exe has been restricted
by your Administrator by location with policy rule {34ae1087-c2cc-409f-a442-e48e70e62efb}
placed on path C:\Users\[username]\AppData\Local\*\*.exe.
I faced the same problem while installing office on my PC.
After all possibility I found that there is existing Microsoft Office folder inside Program files (C:\Program Files (x86)\Microsoft Office) I simply deleted that folder and tried to installed again its work for me.
Related
I got an issue with the tfs.
Firstly after my tfs server database got full.
So in order to solve it i cleared the table of logs from tfs server.
Now at time of clearing data one of my workspace had checkout of one file. As soon i finished my clearing data, it is giving me this error TF30063: You are not authorized to access Microsoft-IIS/8.5. at every time i try to get latest version.
Thats how i am unable to take latest.
Any help would be appritiable.
Right-click solution
Get Latest Version
Try commit again
Issue started for me when I upgraded to VS2017
For me it helps if i just click the Refresh button at the top of the Team Explorer.
After that, the message disappears and i can normally check in.
For me, it helped just to restart Visual Studio.
Clean the Cache folder on client computer. The folder path is: C:\Users\username\AppData\Local\Microsoft\Team Foundation\5.0\Cache.
Clean the Cache folder on Server machine. The folder path is: C:\Program Files\Microsoft Team Foundation Server 12.0\Application Tier\Web Services_tfs_data
After cleaned, on Server machine, click Start and select Run… to open the dialog box, then input iisreset.exe and click OK, wait it run completely.
I just reconnected to the team project in the Team Explorer and my commit went through, didn't have to restart anything.
I had the same issue. When I closed an open Source Control Explorer window and all the files in Visual Studio, I was able to check in.
I think i got solution, exactly got that how to do.
Do checkout that file and check in an old version of that file
and
than do take latest.
It will not generate this error again.
If you can get a copy of the file that is on TFS you can add it as a new file to TFS, and then do get latest version of the file, and then select keep local when you get the conflict error, and then you can check in the file. After that you can then get latest with no errors.
For me, Run as Administrator from Visual, It will never make this error again.
1 : Open TFS window.
2 : Click on Refresh(F5).
3: Try again to Check-in.
CLick here see Solution (Image):
I have faced same issue while check-in on TFS : You are not authorized to access Microsoft-IIS/10.0.
Using Visual Studio 2017 Enterprise with the latest update installed v15.2 (26430.4) on Windows 10 64-bit. The issue has been happening for awhile, it is not new with the latest VS update. We're using a TFS repository hosted on Visual Studio Online, i.e. our TFS repository is at COMPANY.visualstudio.com.
Frequently, when checking in, or attempting to shelve changes from the Team Explorer window in VS, I'll get an error message indicating I'm not authorized to access Microsoft-IIS/10.0. I've had reports of other developers experiencing this as well.
We've discovered the following workarounds.
Clicking the refresh button on the top of the Team Explorer window and then trying the operation again
If you have multiple workspaces, changing to a different one, then back to the original, then trying the operation again
It appears something is "stale" perhaps with the TFS connection and that refreshing it prevents the error message.
Hitting the refresh button over the Team explorer, resolved the issue.
I had a locked item. When I excluded/undo the locked item it went through.
Refresh TFS not worked for me
In my case the error disappear restarting Visual Studio
or me, it helped just to restart Visual Studio.
I am trying to re-install SSMS after my previous installation went corrupt due to one of my corrupt hard drives (E: in the image below). Trying to uninstall the previous version does not work as it tries to find the uninstaller from that drive.
Running the installer anyways gives me the following error with an un-editable location to point to a valid drive.
"Invalid location. Please enter a valid location to proceed."
I ma pretty sure that the remnants of the older installation must be in the registry somewhere. Any idea where to look for ? Or any alternate solution to solve this problem ?
It seems that you need to remove the following registry key and that gets the new setup going.
For x64 OS :
"HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Microsoft SQL Server Management Studio"
For x86 OS :
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server Management Studio"
Then try installing after a restart.
I recently had this issue and neither of the above reg keys existed.
To get past this I had to use Shift + Right click and select "Run as a different user". This allowed me to enter the appropriate admin credentials and continue with the install.
On Windows 10, I've uninstalled a corrupt installation of the above, but when I try to reinstall, I keep getting errors. The uninstall has left folders and files behind in both the Program Files and Program Files (x86) folders. I've used CCleaner to tidy up the registry, but still getting errors, the latest of which is:
Error code 0x800F081F
I also did a system restore, but the folders and files are still present.
I went to MS support and got the following suggestion:
"To fix the error codes for Windows 10, follow these steps:
Download the Windows Media Creation tool, and create an ISO image locally, or create an image for the version of Windows that you have installed."
Problem is, when I run this tool, it wants to completely reinstall Windows, instead of giving me the option to create a disc image.
Any ideas on how I can clean up the corrupt the SQL Server Express installation and start over?
Thanks in advance,
Allan
I have been using Visual Studio 2010 Pro for my vb.net desktop application development. I publish the apps via clickonce to a web server with ftp. My settings look like this:
Publishing folder location: ftp://www.webaddress.com/folder/
Installation folder : http://webaddress.com/folder/
This works perfect in VS2010.
I am now trying to upgrade to Visual Studio 2015 community edition. When I try to publish my app, I get the error "The components for communicating with FTP servers are not installed". I am getting this error on both computers I have installed VS2015 on.
Strangely enough, there isn't much info on this error. The only solution I've seen is to repair the installation. I did this but still a no go.. Another cause I read about is having Xamarin installed, but I have never had that installed.
Has anybody run into this and know what the fix is??
EDIT:
It appears to not actually have anything to do with installed components. After I posted this question, I realized the publish via FTP had worked earlier on a little sample Hello World project i made (brain fart). It was only once I loaded my existing project that this error started showing up.
I closed the solution, created another simple project, and still got the error. I closed visual studio, reopened the sample project, and ftp worked! I then opened my existing project and ftp worked there too?! So I don't know what the trigger is, and I haven't had it fail again yet, but maybe this info will help figure out what is causing the failure.
EDIT (3/30/2017)
Just an update - I am still having this issue. This issue happens on visual studio 2013, 2015, and 2017. I have tried reinstalling the c++ redistributable, still nothing. It seems others are having this issue with a web project but mine is a desktop app publishing with clickonce via FTP. It must be something to do with solution I am working on that was originally created in 2010, as the issue is not present in any other project.
I had the same issue with Visual Studio 2017. What fixed it for me was to start the Visual Studio Installer and install the ".NET Core cross-platform development" workload.
I had the same issue in Visual Studio 2015 / Update 3. It was resolved after installing the 32-bit version of Visual C++ Redistributable Packages for Visual Studio 2013 (https://www.microsoft.com/en-us/download/details.aspx?id=40784)
See also https://github.com/aspnet/Tooling/issues/748
I had the same problem with Visual Studio 2015. And Publish used to work fine so I went going crazy looking for and trying different solutions. Then I read on another thread of doing a Setup-> Repair (submitted by Erikest). I did a Setup->Repair and the publish process now works! I think it's also possible that the Repair not only did the trick on the FTP components but also replaced the C++ redistributable (often mentioned as a solution to this problem),
This is a total work around, but I've noticed I get this error every time I open my app (that originated in VS2010) and try to publish without first opening a sample app. I created a new project and published it to my FTP server. When I receive this error, I close Visual studio, reopen and the open the sample project, publish that app, then open my real app. The publish then works.
This works every time, and seems to be a bug in Visual studio, and probably has something to do with the fact that my app was originally built in 2010.
Maybe this will help somebody else with the same issue. It's a big pain so hopefully MS gets a fix in for this.
I have been banging my head against this problem for many months, re-installed VS over and over and just did a clean install of Windows 10 in the hope it would work but to no avail. By chance I cleaned some old .accdb files from the App_Data folder that I no longer need since I converted to SQL Server database and FTP publishing now works.
So it seems VS does not like the .accdb files but was happy with .mdb files when publishing with FTP.
As soon as I put the file back in App_Data the problem returns. Hope this is some help.
I had the same issue here, I was using the Publish right click option on the project, which had been working fine. What fixed it for me was going back through the publish options and re-testing the connection. Publish seemed to work after that. Maybe it forgot a password or settings?
I also installed the x86 C++ Redistribution Package.
Hope this helps someone who is in the same boat.
After many successful website publishes with Visual Studio 2015 Community Edition, we experienced the "components for communicating with ftp servers are not installed" issue. :(
First attempt at resolution was uninstalling VS Community 2015, then installing VS Community 2017. Received the same error: "components for communicating with ftp servers are not installed" when attempting to publish our business website.
With some work, we found that by uninstalling Microsoft Web Deploy and re-installing, this seemed to fix the problem. We can now use Visual Studio > Publish function to our ftp without problems.
See this link for download of Microsoft Web Deploy components.
https://www.microsoft.com/en-us/download/details.aspx?id=43717
Dont know what broke this VS IDE functionality, but hope this fix helps some.
I encountered the same error with Visual Studio 2019
I fixed it by using the Visual Studio Installer to install the Web Deploy (inc .netcore 2.1) under individual components
I just did a simple "repair installation" in the installer. Worked for me.
I am using Microsoft Visual Studio Community 2019 and had this problem for a while.
The problem went away after I updated about 10 NuGet updates that were over due.
I had the same problem, I closed all the open windows I closed Visual Studio and then I opened again and published and then it worked!
I'm encountering the following
System.Runtime.Remoting.RemotingException error when I create a blank
Windows 10 Universal Application...
Following are event viewer screens...
I have checked online for other solutions and have already done the
following...
Uninstall/Repair Visual Studio 2015 Update 1
Reset my Windows 10 PC 1511 update
Cleared the Designer/ShadowCache folder
Target environment has been set to x86/x64
Target framework set to 10240
Developer mode enabled
Updated graphic drivers
Have cleaned and rebuilt solution
Updated to VS15 Update 2
Please let me know if you have been able to find a solution to the above
UWP applications fail to launch from Visual Studio if project location and Windows Store apps installation path are on a non-default drive. Also, the XAML Designer will crash if you install Visual Studio and Windows Store apps to a non-default drive
Windows 10 allows users to change the default storage location of Windows Store applications. If you select a non-default drive for your apps, and if you install Visual Studio 2015 onto this drive, the XAML designer will not start and Windows Store app projects built on this drive cannot be run from Visual Studio.
Note: the workaround below will make any Store apps installed to the secondary drive inaccessible until next restart.
The file system driver can be temporarily disabled by running the following command from an admin command prompt:
fltmc detach filecrypt :
This will enable both running apps from this drive as well as usage of the XAML designer until the machine is restarted.
For a longer term fix, move your app or Visual Studio install to your system drive, or a secondary drive that has never been the storage location for Windows Store apps.
I had the same problem. I started visual studio as an administrator and the designer came back.
You might want to try to clear the XAML Designer Shadow Cache. I've fixed al sorts of ailments with this process.
Its been a few months but I have finally been able to get the XAML Designer to work.
As #peterfaraday mentioned, the XAML Designer only works if you install Visual Studio on the System Drive (C: in my case) instead of using any other drive.
After uninstalling Visual Studio keep the following things in mind...
If your system partition is small, look to increase the space as the installation can take a lot of space based on the components selected.
If you had already installed VS on any other drive, while reinstalling you will not be able to change the default installation directory.
This is because your initial path of installation was saved as in the registry. I tried solving this issue by following these steps. In my case I had found multiple keys in the registry and hence "Reset this PC" (Windows 10) by allowing only for my personal files to remain. This cleared out all the registry keys and I was able to install VS back on the C: drive, resulting in the XAML Designer finally working (Please note that resetting your pc will remove any applications installed on your machine)
I got the same problem months ago. I Cleared the cache and Rebuild the solution. I got success.