So, after using the new quote "Free" version of Visual Studio 2013 -- ie Visual Studio Community 2013 -- for a time, I have gotten the message that my "30 day trial" has expired...
License: 30 day trial (for evaluation purposes only)
This license has expired.
! Your trial has expired. Sign in to acquire a license using an online account
Ok...so I tried to click the "Sign On" option I was given. The result? I get this message in the window that comes up:
Sorry, we ran into a problem
SP324099: Could not complete the operation
This also happens when I try the Check for an updated license option.
According to the answers I saw
here
and
here
the fix was to update Internet Explorer to version 11. The only problem? I have IE11 already. I can't really find any way to fix this for Visual Studio Community 2013, and I'm not sure what to do with this. Any help is greatly appreciated. Thank you!
EDIT: I am not sure if this is relevant information but I will include it in the event that it is. When the error comes up, I get an IE browser window that pops up as well. This IE browser takes me to a site with an invalid/expired certificate (that appears to still be MSDN...I hope). I continue and log in to MSDN, but it just gives me this dictionary with {"securityToken": ["..."]}
Is the certificate problem related to this somehow? Does this information provide a clue as to what the answer is? Thanks.
After you have attempted to refresh the "free" license, if this popup window with the error message appears, just simply click on the X in the upper right-hand corner of the window to close the popup. (Instead of attempting to sign in again.)
Related
I have installed the copilot on my VS 2022 successfully (My work laptop). I also have paid an annual fee. but when I log in and activate it (paste the code and the message 'Congratulations, you're all set! Your device is now connected.' shown on the browser ) I only can see the below message in VS, copilot output tab
'14:14:36:648 Please open https://github.com/login/device and enter the device activation code AD05-A79D that has been copied to the clipboard.'
It seems to be stopped in this step and I can't activate it! any log to check? Any advice to fix it
Note: I have installed it on the same version of VS on my personal laptop.
Note: No filter from the IT side on the GitHub connection
Thanks for your advice :)
Hi everyone this is my first post. I am having a major problem with visual studio I cannot log in to extend my 30 day trial period and have no access to using visual studio. So here is what is happening exactly I have been using visual studio 2017 community version for 30 days as a trial, they want me to log in to extend the use of visual studio but I get an error for almost everything. I will show some screenshots as to what specific errors.
Specific error with vs
So those are my errors and like anyone else here would do I have tried multiple ways to fix this myself. Here is what I have done.
I have gone into .Identityservice and cleared the cache that was there(there are multiple different forums and such detailing which cache to delete I only had one in the appdata/local/.identityservice which was IdentityServiceAdalCache.cache)
I have tried to go around going into the visual studio installer then to report a problem to sign into the developer community, it will let me sign in however as soon as I am done signing it is says that I have logged out and need to refresh my credentials which is why I cannot post on the developer community directly as well.
three clean reinstalls
repair option in installer
tried to see if updating would help
One more thing is that since visual studio provides error logs I have one here(or most of it anyway)
error log
I would really appreciate any help I can get, I have scoured the internet looking for answers but haven't been able to find much. Hopefully I have provided enough information. Thank you.
I am using Visual Studio 2013. It keeps crashing under certain circumstances, so I'm trying to submit a bug report.
I have tried HELP > Feedback > Report a Bug, but after logging in at connect.microsoft.com/VisualStudio it either has a message saying that I am not authorized to submit feedback for this connection (whatever that means), or the page is blank under the top banner. In either case, I can click the "Feedback" link on the banner, which takes me to a list of the most recently submitted items. From that list, there is no direct way to add an item, but the instructions say "After searching, the option to submit new feedback will be enabled." If I search (which takes literally minutes), I then get a "Submit Feedback" button at the top of the list. If I click this, it goes back to the blank page I saw before I clicked "Feedback" on the banner.
How am I supposed to submit my bug? How can I report this failure of the bug reporting service?
If you are having troubles submitting with the built in tools you can go to https://connect.microsoft.com/VisualStudio and manually submit a bug report there.
Using the built in tools are preferred because you can record a ETL trace and steps showing how to recreate the bug. When you post to connect they may ask you to do those things manually.
However, it is unlikely any bug in Visual Studio 2013 will be fixed. They only release updates for the current publicly released version of Visual Studio which is Visual Studio 2015 currently.
Whenever I open Visual Studio Community 2015, it asks me to update my license. It won't let me download an updated license, as every time I try, it tells me to check my network or proxy. I do not have a proxy, and my network is just fine.
In addition, when I click the "Add Account" button, which is supposed to let me add an account, it has a message box pop up saying "Configuration system failed to initialize.".
When I click the sign in button, the sign in window pops up, but it disappears immediately, then the program crashes.
Here are a few pictures:
Visual Studio Community 2015
How do I fix this?
I'm afraid it's something with your specific machine. Given that you've cleaned out the computer and made a full reinstall of the OS and tried with a new account at Microsoft, there's no rational reason why it's not working in a general case.
I've tried those steps and it worked out. You might want to retry the clean-reinstall-reregister steps again, in case something went missing the last time.
As a personal side note I can safely point out that this shouldn't happen. Definitely not to good people like us. :)
EDIT #3 : Microsoft has released a 'fix' to this problem which is available here. I haven't had the time to test it, but I those who want to are welcome to leave their feedback here !
Sometimes when I run an application from Visual Studio and it crashes or I stop it using the stop button in the debug menu (Debug->Stop Debugging (Shift-F5)), the console of said application stays open... and never closes. I cannot close it by clicking the 'x' button in the top right corner. I cannot kill the process as it is not even listed in taskmgr.
I have seen this problem documented in different places on the web, but no solution so far.
I am running on windows XP SP3, using visual studio 2008 w/ SP1.
1- What could be causing this ?
2- Is there a fix ?
thanks alot.
JC
EDIT: There is no MyApp.vshost.exe process to close, and closing visual studio does not close the console either. Worse even, if I try to restart my computer windows will hang and never close, I need to do a forced shut down.
EDIT #2 : (from Brad Sullivan, Program Manager - Visual Studio Debugger on March 2nd)
[...] this issue is likely not in Visual Studio since it also occurs in scenarios where Visual Studio is not present. We are in the process of handing over our investigation to the Windows Servicing team.
But for now, removing the KB978037 update and it's related files seems to work.
This is a bug introduced in security update KB978037. Back out this update and you'll be back to normal.
Also see here:
http://social.msdn.microsoft.com/Forums/en-US/vsdebug/thread/e6d4a4f5-7002-401a-90e1-6174d7f9e3ca
Microsoft has released a 'fix' to this problem which is available here. I haven't had the time to test it, but I those who want to are welcome to leave their feedback here !
There are a couple of things that could be happening here. Try closing down the following process and see which one, if any close down the Console application as well.
The Hosting Process: Typically named YourExecutable.vshost.exe
Visual Studio
If closing the hosting process fixes the issue then one quick work around is to disable the hosting process itself.
Right Click on Project -> Properties -> Debug -> Uncheck the hosting process
If closing down Visual Studio fixes the problem then it's potentially a bug in Visual Studio. Please file a bug on connect.
http://connect.microsoft.com
Visual Studio Debugger Team has already acknowledge this issues on their blog. check the below url for more information.
http://blogs.msdn.com/debugger/archive/2010/03/11/help-my-console-windows-won-t-go-away.aspx