I believe the problem is related to the latest release of Office 365, or of WinX. For some reason the information needed by QuickBooks to find the application's certificate related information is not being passed along from the Office code.
I wrote a console application linked to the same libraries used for my AddIn and it was able to connect to QB. Other users of my AddIn are still able to use it. I found that they were running an older release of Office365, 16.0.8229.2091 or earlier. The desktop that is failing is running Office365, 16.0.9229.2103 (previously I had this as .2013 instead of the correct version .2103). When I look at the Properties for the Integrated Application, the console version correctly shows the Developed By: and Developer identity verified by: information. When I do the same for the AddIn, it shows Unknown for the Developed By: and it shows: This application does not have a certificate. QuickBooks cannot determine the developer's identity.
Users have been running my AddIn for about two years now. I'm using the latest version of the QBXMLRP along with Visual Studio 2015 and version 4.5.2 of the .NET Framework. I used the same process to generate the test certificate and both assemblies were signed with sha256.
To the best of my knowledge, the program broke when the latest version of Office365 was installed. That being said, it could be an issue related to the latest patch of Windows and that information I do not have. However, given that other workstations can run the AddIn and have earlier versions of Office365, I'm thinking that's a pretty good indicator. And that I was able to get a console app to run, but the AddIn fails to access QuickBooks. It does load in Excel just fine, but it is not able to connect with QB.
I posted this issue on the QB forum and received the answer. It appears that Microsoft released an update of its Office365 Business software that caused the problem. They have since released a subsequent update that should provide remedy.
I've included a link for your convenience.
Good news, the problem WAS resolved by installing the latest update for Office365! Whew!! That was a real pain in the butt. A special thank you to William Lorfing at the Intuit Developer Group for keeping tabs on this problem and alerting others to the solution.
I have been sent a working project from a coworker to start learning Visual Studio. The project is under version control, however I don't want to have access to final customer product. So when I try to open the solution file I first get a message that the project is under source control:
"Team Foundation Server Version Control
The solution you are opening is bound to source control on the following Team foundation Serer:
http:// . Would you like to contact this server to try to enable source control integration?"
[yes] [no] [help]
I press no, then I get an error:
"The solution appears to be under source control, but its binding information cannot be found. Because it is not possible to recover the missing information automatically, the projects whose bindings are missing will be treated as not under source control."
[ok] [help]
I proceed and press ok, and another message pops up:
"projectname\projectname.tsproj: The application which this project type is based on was not found. Please try this link for further information: http://go.microsoft.com/fwlink/?prd=12395&pver=11&sbp=ProjectTypeDeprecated&plcid=0x409&clcid=0x409&ar=MSDN&sar=ProjectCompatibility&o1=B1E792BE-AA5F-4E3C-8C82-674BF9C0715B"
My coworker tells me he sent the whole project, so I can't figure out why I cant get visual studio to open it. I am new to visual studio, but I have some programming experience.
Any help is much appreciated.
Thank you
It is doubtful that version control has something to do with your problem. There are two possibilities I could think of:
Your coworker uses full version of VS2012 and you are now having problems due to the fact that Visual Studio Express comes in two main flavours - Web and Desktop. It is unable to load Web(or Desktop) project because it just does not have any tools to work with it. Ask your coworker whether they mix web and desktop in their solutions. If it is so you should either use full VS or be given a reduced set of projects.
Nearly the same - your coworker uses some very old or very new version of particular project type (something like ASP.NET MVC that(as I remember) has different project type for each version). Again ask your coworker if it is so. In this case you will just have to install the needed templates and SDKs.
P.S. I was unable to open your link - it opens microsoft.com/default(maybe due to some regional problems). Search by key words brought to me similar problem for VS2010 http://connect.microsoft.com/VisualStudio/feedback/details/728847/could-not-open-vs2010-solution-with-mvc-project - may be it could help you more specifically.
I'm using TFS Preview (Team Foundation Service) with one of my projects with Visual Studio 2012. I'm also using an on-premises TFS server with most of my projects. When I use my on-premises TFS after using TFS preview and go back to using TFS preview, I get this error:
TF30063: You are not authorized to access MyProject\DefaultCollection.
If I go to Team → Disconnect TFS and then connect to TFS preview again, I'm able to see a "Loading identifiers" loading screen coming up, but in the end I don't get to enter my credentials to TFS preview (my Microsoft account) and as a result, the TF30063 error still occurs.
I suspect this has something to do with my Microsoft account (i.e. Live ID). I'm logged in to Windows with the same Microsoft account that I use at TFS preview. I have logged in to other sites (Windows Development Center, MSDN, etc.) with other Microsoft accounts, but I verified that if I log out of these services and re-login with the correct Microsoft account, I still get the TF30063 error when I try to log in to TFS preview from Visual Studio.
When I came accross this issue none of the provided answers solved this problem or if it did I didn't like recreating the project. The way I ended up solving the issue:
Clicking on the "Connect to Team Projects button" (The plug next to the home button in the Team Explorer tab)
Right click the project you are getting this issue on.
Click Connect.
I guess the "Remember me" cookie timed out but gave me a generic response for trying to push or pull any code.
I solved this issue by using the browser from within Visual Studio, View->Other Windows->Web Browser; Ctrl+Alt+R (or * Ctrl+W, W* in VS versions before VS2010) to navigate to the TFS page and log out of the wrong account and log back in.
For me, the issue was caused by using another live-id to unlock a windows phone for development. Somehow the credentials got cached, it seems.
For me the error came after changing my password for my AD account.
I had to remove the line from credential manager (which contained the previous password.)
Then it worked again.
I have upgraded TFS 2015 to TFS 2017, and then the TF30063 error occured on one of my client machines. None of the solutions here worked...
For me the only solution that worked was running the following command from the Developer Command Prompt:
tf workspaces /collection:https://tfs.xxxxx.com/tfs/DefaultCollection
Of course, you need to adjust the url to the valid one.
Source: https://www.visualstudio.com/en-us/docs/setup-admin/tfs/admin/backup/refresh-data-caches
The TFS Preview login apparently uses Internet Explorer and thus might conflict with other MS Accounts you are using. Fully clearing the IE cache seems to work for me. After the cache clearing, I get to the correct login screen and may enter my credentials as needed.
I tried all of the suggestions here. None worked. This could be my particular situation where I connect some VS instances to our company TFS and some instances to my private TFS.
The only way to solve it for me is to close all VS instances and start a new instance.
Oddly enough, connecting to the internal TFS is never a problem. Connecting to *.visualstudio.com sometimes raises this issue.
In VS 2015 it can be achieved by
Team Explorer > Connect > Manage Connections
and selecting the team project again. In case of there exist more than one account in VS, Team Explorer asks for which account to use to connect to the team project.
I tried the following to resolve this issue. Hopefully one of these will work for you
A - Close VS then start the VS Developer Command prompt as an administrator. Then enter: devenv /resetuserdata
B - Clear the cache in IE (apparently VS uses this to access your account mentioned here)
C - Click View -> Other Window -> Web browser (CTRL+ALT+r) sign in to your old account, log out and sign in to your new one
D - Open the folder containing you solution, delete (backup if you want) the Visual Studio Source Control Solution Metadata File delete the .suo file and open the .sln file in Notepad and delete the below section
GlobalSection(TeamFoundationVersionControl) = preSolution
SccNumberOfProjects = 6
SccEnterpriseProvider = {**********************}
SccTeamFoundationServer = theServer
SccLocalPath0 = .
SccProjectUniqueName1 = pro
SccProjectName1 = myProject.BL
SccLocalPath1 = myProject.BL
.....more stuff.....
EndGlobalSection
The last step was required because, while I had managed to disconnect VS my solution was still trying to connect to the old source control account.
Make sure that Windows Authentication hasn't been disabled for the Website / Application within IIS.
I'm not sure HOW this happened, but I did uninstall Hyper-V today to be able to install VMWare Player and then re-install Hyper-V
Reenabling this allowed everything to work again.
In team explorer I removed project... then in Manage Connections, clicked on 'Connect to a Project...'
In this screen choose your project then click on Connect... this solved my problem.
This happens to me regularly, and none of the solutions described above works every time.
Most of the times the solution where you use the "Connect to Team Projects button" works fine, but sometimes nothing happens when I do this.
Other times I simply have to re-login to http://tfs.visualstudio.com using the Visual Studio built-in browser (Ctrl+Alt+R) or via Internet Explorer.
(As suggested in some of the other answers, for my part this is not caused by multiple live-ids)
None of the current answers worked for me. I found a solution here.
The issue was that my previous credentials were cached by the Windows
OS for the TFS server. While some people might have had success wiping
out the AppData temp folders, that is not required.
You need to update the credentials through Control Panel on the
Windows OS.
For me on Windows 10: Close VS. Go to Control Panel (with small icon
view)-->User Accounts-->Manage your credentials (on the left
column)-->Select "Windows Credentials"-->Scroll down to the "Generic
Credentials" section and look for your TFS server connection. Expand
the pull down and click "Edit". Enter in new network password. Reopen
VS and everything should work again.
Just restarting the visual Studio would do the job. As I did this and it worked like a charm
I have just removed the server from Team Explorer, then added again, and it worked =).
When Visual Studio prompted me for Visual Studio Team Services credentials there are two options:
Use a "Work or School"
Use a "Personal" account
In my situation I was using a work email address, however, I had to select "Personal" in order to get connected. Selecting "Work or School" gave me the "tf30063 you are not authorized to access..." error.
For some reason my email address appears to be registered as "personal" even though everything is setup in Office 365 / Azure as a company. I believe the Microsoft account was created prior to our Silver Partnership status with Microsoft.
Disconnect from Team Fountation Server under Team Menu and reconnect it from Connect Tab under Team Explorer Window
I got this error, after all fiddling work I could do — the disk space was full!
Clearing it fixed my issue.
I was also facing the same issue as you did. Here is what I did to solve:
METHOD 1
Click the 'Connect' icon just next to Home icon in Solution Explorer.
Choose your project > Right Click > Connect.
Try Check-in the project and this time it will happily proceed.
This is what I tried, and I did not need to logout from any sessions from TFS or VS Account.
METHOD 2
Just press refresh on the top of Team Explorer.
Try to Check-in.
This is also easy method.
Hope this helps.
I had to "run as a different user" to get Visual Studio to connect using my TFS account. It seemed to be trying to use my Microsoft account instead.
Text and image from: https://www.visualstudio.com/en-us/docs/connect/connect-team-projects
To change accounts
To run Visual Studio under an account that is different from your logged on Windows account, open the context menu for devenv.exe to access your run as options.
You can locate the executable in the following folder: Drive:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE.
I've experienced this issue after an TFS upgrade, and somehow Visual Studio is caching invalid login credentials. I've found two ways to fix it, first, using this answer I completely reset Visual Studio, then reconnected:
Click on menu Tools → Import and Export Settings → Reset all settings → Next → "No, just reset settings, overwriting all current settings" → Next → Finish.
For some strange reason, after the reset it connected without issue (I didn't even have to re-enter my credentials or reconfigure TFS after the reset).
The second approach was easier. First close all instances of Internet Explorer and Visual Studio, then open Internet Explorer and browse to TFS, login, then open Visual Studio again and attempt to connect to TFS one more time.
I finally found the right answer for me on the web.
For me it happened after I changed my password and Windows cached the TFS password. It is require to be updated manually. This is one way to do it:
Solution found at: developercommunity.visualstudio.com
CREDIT: Lavente Nagy! Thanks so much!
Fix Summary:
I found a solution, and it works on Windows 7/Windows 10 too. The steps are the same:
Close Visual Studio. Go to Control Panel (with small icon view) → User
Accounts → Manage your credentials (on the left column) → Select
"Windows Credentials" → Scroll down to the "Generic Credentials"
section and look for your TFS server connection. Expand the pull down
and click "Edit". Enter in new network password. Reopen Visual Studio and
everything should work again.
Check the information in registry :
HKEY_CURRENT_USER\SOFTWARE\Microsoft\VSCommon\Keychain\Accounts and delete the related keys under Accounts section.
Clear the cache in these paths:
%localappdata%\Microsoft\TeamTest
%localappdata%\Microsoft\Team Foundation
%localappdata%\Microsoft\VisualStudio
%appdata%\Roaming\Microsoft\VisualStudio
Hope this will work.
Note: By doing this may clear all the cookies and caches and load the Visual Studio New.
What isn't officially an answer here, but worked for me (the other answers didn't help):
Click Team Explorer tab -> Connect hyperlink - connect\choose repository. And it works.
Make sure your password hasn't coincidentally expired exactly on the same day you decided to install a new dev machine.
If you can't even log into TFS using the web interface then this may be the case.
Now I got the solution to the problem which I have faced:
The TFS remembered the prior password when I got logged in by using my mobile VPN.
Solution:
Resetting the account that I used to connect using VPN
I get this problem when I am forced by our IT security policy to change my password. After a password change, when I connect to TFS using VS2017, I am no longer authorized to access our TFS server and get the TF30063: You are not authorised to access ...:8080/tfs error message.
However, if I connect using VS2013, I can connect to the server without problems and the access denied error with VS2017 goes away.
It would be a lot easier if the error message were to tell us the username it's trying to access TFS with.
I've been coping with this for a while, and usually logging back in only for the next day to stop again.
I found I had two accounts and removing the unwanted one fixed the issue.
This is under Help > Register Visual Studio
Try making Internet Explorer your default browser temporarily.
In my case I had a proxy. I had edited the devenv.exe.config and set the proxy there. But today I changed the proxy domain password and TFS failed (menu View → Windows → Browser also failed). I could of course have edited the devenv.exe again. But there was a solution to remove it altogether. A brilliant one. It is given here.
Open menu TOOLS* → Extensions & Updates.
Click on Updates... in the left-hand menu
Here it asks for password and restarting Visual Studio. All okay. For more info, look for the answer in the link.
press Win button, then type credential manager and open it .
Add generic credentials.
Go back to team explorer, add the server again.
I used the Apple MigrationAssistant to migrate to a new machine, and now MonoTouch won't launch my app in the simulator because it says my license is not valid. Following instructions in other posts here, I removed my license file and re-ran the setup, but that just told me that everything was installed and launched the app with the same problem. So, I completely removed MonoDevelop, and re-ran the setup. It dutifully downloaded MonoDevelop and installed it, but never gave me a chance to activate, so I'm still stuck.
http://support.xamarin.com/
Look at the box that says "Product Download and Activation Self Service" - login there to re-download the full licensed version of MT. There are also some tools to deal with reactivating licenses.
If all else fails, contact support directly.