I have 5.0.44.598 - Mahon version of Plastic SCM, the latest one by today(25 Aug,2014)
This is the first time I will be using Plastic SCM.
I keep getting "An error occured processing your request" error message when I click on branch explorer. Also whenever client software is opening first time.
I have win7 machine and also a win server 2012 on azure; have the same problem in both systems.
Does any one have the same problem, or any resolution?
I think it is a bug.
Could you enable the Plastic client log? (http://www.plasticscm.com/infocenter/technical-articles/kb-enabling-logging-for-plastic-scm-part-i.aspx), and send the stack trace to: support#codicesoftware.com
I´ve tested the same version in my local Win7 machine and the branch explorer is properly working.
Could you delete the file: "C:\Users\xxx\AppData\Local\plastic4\guivisualstate.xml" and restart the Plastic client.
If you create a new workspace, does the issue persist?
Do you have enabled any external extension (issue tracker...)?
UPDATE: Reviewed the logs and sent a solution to #freewill. If a similar issue happens again please contact to: support#codicesoftware.com
Regards.
Related
Trying to upgrade our on-premise server from 2015 to 2018. For some reason I get this message in the error log:
Team Foundation Server could not connect to the database. Verify that
the instance is specified correctly, that the server that is hosting
the database is operational, and that network problems are not
blocking communication with the server.
Why would this happen on step 909 only? Previous steps were already manipulating database so if access is the problem why would it error out on this specific step only?
Tried to re-rerun patch again but giving me the same error log.
I opened the Windows Event Viewer and got multiple errors on this event:
A timeout occurred while waiting for memory resources to execute the
query in resource pool 'internal'
For anyone having the same issue. Base on the Windows Event error I considered maybe the RAM was the problem. Checked and the server only had 2 GIG RAM.
Pretty weird since TFS alone was saying it was a database server issue. Anyway, upgrading the ram to 4 GIG solved the issue.
Hopefully this can help someone having the same issue.
I have installed and configured Team Foundation Server 2015 Update 3 in one of our server a few weeks ago.
All was going well until the pc unexpectedly was shut down due to electrical problem. After turning on again we now get:
Error 500 internal server error.
Tried to access the web server and got the HTTP Error
403.14 - Forbidden.
TFS administration console seems fine. I'm not sure where to look next. Help would be greatly appreciated.
First, please check your Event View on your TFS server machine to see if there are more detail info or error message for trouble shooting.
For Error 500 internal server error. There's no much value for now.
For 403.14-Forbidden error, this may related to IIS server. Suggest you try to restart the TFS applicaton on IIS. And also clean all cache of TFS server, located at%LOCALAPPDATA%\Microsoft\Team Foundation\7.0\Cache
To narrow down the issue, you could also use Visual Studio to connect TFS server. If this works, suggest you to clear IE cache and try again.
Besides, since the PC unexpectedly shut down, please also check if the related TFS service started properly, if not manually start them.
In case someone else runs across this issue, we had the same problem and it turned out to be the system time on our TFS SQL Server had gotten out of sync. It was off by a number of hours. When I reset the time to be correct, I was able to connect to the TFS instance again without issue.
I got this error when I was migrating from TFS 2013 to AzureDevops Server 2020 using XAML Build. The error on Event Viewer from Application Tier Server was "Exception Message: The protocol binding ':443:.domain.com.br' is not valid for 'https'. This might be because the port number is out of range. (type UriFormatException)". I adjusted on IIS the https bindings to accept requests from IP Server.
enter image description here
I am using WebConnector version -2.1.0.30 with QuickBooks 2015 Enterprise.
WebConnector was working fine but all of a sudden when I run WebConnector and click on "Update Selected" button then it came up with this error (Note: by that time no one was logged on to QuickBooks).
Then as a quick fix I have deleted that QWC file and added a New one, that works fine.
Can any one please come up with a better solution and the reason behind this error.
Thanks in advance.
Chances are you're running QuickBooks on a shared Windows Server, or in a hosted scenario with someone like Right Networks, Intuit Cloud, Cloud9, etc.
If so, this error means that Windows Server auto-logged-out some user and closed QuickBooks for them, but is still holding the file lock on the QuickBooks company file. Windows will automatically release the file lock after a short amount of time (usually 30 minutes to an hour).
There is no "fix" outside of waiting for a while, and then trying again.
I have been working on restoring a build server (tfs 2012) from a backup and all manner of things got messed up (the tfsservice account password had been altered and I had to go to every service and app pool on the box and update it). Once sql was backup I was able to update the password via the TFS admin console app. Then I was able to re-register the build service and add a controller and a build agent. It starts briefly and shows green for a few seconds before stopping and a "details ..." button appears next to the Build Service. If I click the details button I see the following
"Please contact your administrator. There was an error contacting the server. Technical information (for administrator): HTTP code 500: System.ServiceModel.ServiceActivationException"
I have checked the http bindings in iis for the tfs site and there is only the one "*:8080"
I tried hardcoding it to the ip on the box and I still get the same error. If I go to one of the client machines and try and queue a build it shows the build server as being offline.
I have also checked for multiple host headers and the memory utilization which are the most common responses to this particular issue. Neither of them seem to be the cause or the solution.
Any ideas or suggestions are welcome I have run out of ideas to try here. Thanks in advance for any help you have to offer.
EDIT -- also found this in the log: Build machine MyMachine lost connectivity to message queue tfsmq://buildservicehost-25/.
Earlier today we experienced a YSOD on one of our MVC sites running on IIS on Windows Server 2003.
Usually, these are reported via e-mail using ELMAH (using this setup), but since this was a compilation issue (of some sort), it did not get reported via e-mail.
The specific error was:
"The directory 'App_GlobalResources'
is not allowed because the application
is precompiled."
This is a major problem, since a potential customer could notice the problem before we do. How can we make sure these YSODs are logged, when the exception handler on the site is not called?
It is possible to monitor the event log with VBScript. You could then email this when it occurs:
Here's an example:
http://www.microsoft.com/technet/scriptcenter/resources/qanda/feb07/hey0226.mspx
and email from vbscript:
http://www.paulsadowski.com/WSH/cdo.htm
You could do this with powershell and/or another .net app on the box also.
If you can, check the event viewer on that machine. This is the logger of last resort on a Windows machine.