This error occurs after restoring database on TFS
Please guide if anyone resolve this error.
Thanks in Advance
Firstly please make sure you have correctly restored the database, see Back up and restore TFS, then check it again.
If the issue still exists, just try to check below things to narrow down the issue:
Make sure the SQL Server is stated and available, and the network
connectivity is OK.
Check the Service Account, make sure the Service Account has been
added in SQL Server.
Trying refer to the solution in below link to fix the issue:
http://www.ganshani.com/blog/2014/04/solved-tf246017-team-foundation-server-could-not-connect-to-the-database/
If above solution can not resolve the problem, please check the Event log. The Windows Event Log is a good candidate where to look for the potential cause.
Related
I am getting below error-
Got TLS error trying to find package cupertino_icons at https://pub.dartlang.org.
pub upgrade failed (69) -- attempting retry 2 in 2 seconds...
My understanding is I am on office network(VPN) thats why I am getting this error. I have tried multiple options and I have seen multiple multiple post but no post shows the exact way of doing things. So I will post my all questions here, if anyone help it will be really helpful for all persons who are going to start work on flutter
1) How to set and create a self-signed certificate?
Do we need to create a self signed certificate for pub.dartlang.org domain?
have tried to create a certificate by using this (https://www.akadia.com/services/ssh_test_certificate.html) use domain as pub.dartlang.org, is this a correct way or how to do it?
2)I have put DART_VM_OPTIONS=--root-certs-file=C:\Users\dev\certs\chrome.cer as my certificate but still issue not resolved.
3)If I have to set https_proxy? What are the values for hostname and port in VPN? How can i find these values?
Flutter app behind corporate firewall throws TLS error during packages get
4) To solve this issue I have seen the reference of this comment
https://github.com/dart-lang/pub/issues/1882#issuecomment-415588527
How to implement this?
I have tried multiple things, if anyone can help how to bypass this error that will help many persons, I think.
I have same error on MACbook when running Flutter Create. When I opened the web-browser to access pub.dartlang.org, there is an error message that says: Your Clock is set incorrectly.
Somehow my date was set to a week ago. Fixing the date resolve the TLS issue.
It can be a network error or some kind of permission issue. I was facing same issue. In my case it was due to network permissions in our organisation. I tried with some another network which has full access and my issue was resolved.
It might be problem with restricted network.
You can set proxy
systemProp.http.proxyPort=PortNumber
systemProp.https.proxyPort=PortNumber
systemProp.http.proxyUser=User
systemProp.https.proxyUser=User
systemProp.http.proxyPassword=Password
systemProp.https.proxyPassword=Password
systemProp.https.proxyHost=YourHost
systemProp.http.proxyHost=YourHost
systemProp.http.nonProxyHosts=YourNonHost
systemProp.https.nonProxyHosts=YourNonHost
It might be a problem with the restricted environment variables sequence. You can set bash_profile：
export FLUTTER_STORAGE_BASE_URL=https://storage.flutter-io.cn
export PUB_HOSTED_URL=https://pub.flutter-io.cn
keynote：
"FLUTTER_STORAGE_BASE_URL" is in front of "PUB_HOSTED_URL"
I was also getting the same error, after upgrading my flutter. I was connected to the internet but my clock was not on correct time. After I have corrected the time on my pc, the error was solved.
I am using VSTS for source control and I get this error (title) when I try to check code in.
How do I fix this issue? This impedes checking code in.
It somehow seems to be related to file size. The file that's failing is 9MBs. I find that peculiar since before I was able to check in a 3GB file (I since deleted it though). I am able to upload hundreds of megs in smaller files, too.
What could be the issue?
Error message on checkin
Thank you.
According the error message, the connection to the server was made but since the service was not available on machine, then the sever canceled the request.
You could try below ways to narrow down the issue:
First check the event view on the client machine, if there are some
related error info.
Check if you have set some checkin policies to restrict that.
Check another team project in some collection and different team
project collection, to check if they have the same issue.
Try to use another account to check in the changes.
Try to use your account to check in codes on another client machine. If the
issue only occurs on your machine, you may need to clear TFS and VS
cache which may do the trick.
Try to create a new workspace and map the source to a new location on your client machine, then try it again.
If you are using Window Server 2008R2. Just try to Apply the
HotFix and try the workaround.
I am using umbraco v 4.11.6 (Assembly version: 1.0.4834.19775) the issue is every time the server shuts down or restarts I need to republish the pages which are not loaded.
So please let me know the root cause for this issue if anyone knows or any other things that can be done to over come from this
Thanks in Advance
In version 4.6 there was an issue which had the same behavior when the SQL database was not available at boot time of the website. But with version 4.11 this should be fixed a long time.
I would investigate the logs (~/app_data/logs/). You might find some clue there. Append logs to your post if you can not find the issue.
This might be a problem with some ApplicationEventHandlers not running properly. Or with write permissions on the proper folders. Try adding more logs to the code, so you are sure what runs (and what doesn't).
If you can not find the answer, try the umbraco forums : http://our.umbraco.org/forum
I have configured TFS 2010, but when I try to load the project dashboard for a team project, it returns a reporting service error so I am not able to see the "Task Burndown (hours)" and " Burn Rate (hours/day)". Other parts of the page are working fine.
The error is as:
An error has occurred during report processing. (rsProcessingAborted) Get Online Help
Cannot impersonate user for data source 'TfsReportDS'. (rsErrorImpersonatingUser) Get Online Help
Log on failed. (rsLogonFailed) Get Online Help
For more information about this error navigate to the report server on the local server machine, or enable remote errors
I got resolution finally....
Go to analysis service.
You will see database named as TFS_Analysis.
Go to Roles node.
View properties of "TfsWarehouseDataReader".
Click on Data Sources.
Now you will see Tfs_AnalysisDataSource.
Change access to "Read" and check "Read Definition" box. Now Click OK and You are Done.
The main problem was with SCHEMA CONFLICTS.
First identify which fields are causing schema conflicts, invoke GetWarehouseStatus and observe the XML which fields got conflicted, and in which collection. once you found the filed names then rename the fields with the help of below link.
geekswithblogs.net/Natalia/Default.aspx
msdn.microsoft.com/en-us/library/ee921480(v=VS.100).aspx
then rebuild your warehouse from tfs admin console, take a back up of old database in sql database and delete it .wait for some time (depends on warehouse time to refresh the cube or check the GetWarehouseStatus next day and check the xml ). to check this use below link
type //localhost:8080/tfs/TeamFoundation/Administration/v3.0/WarehouseControlService.asmx?op=GetProcessingStatus
I spend lot of time to resolve this issue, that's why posting the solution here, this may help some one... any queries related schema conflicts and Reporting services feel free to post me... iam not a expert but for sure i can help you out in this issues....
Please use Mark as Answer if my post solved your problem and use Vote As Helpful if a post was useful.
We have a situation where our builds have stopped executing in a stable manner.
At a rate of about one every three we receive either TF215096 or TF215097 errors & the Build fails.
If we then restart the Build controller, it works again - until next time.
The errors we get are:
TF215096: An error occurred while connecting to controller vstfs:///Build/Controller/1: There was no endpoint listening at ht*p://XXXX that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
TF215096: An error occurred while connecting to controller XXX - Controller: Could not connect to ht*p://XXX. TCP error code 10061: No connection could be made because the target machine actively refused it 192.168.XXX.XXX:XXX.
TF215097: An error occurred while initializing a build for build definition \XXX: Team Foundation services are not available from server ht*p://XXX. Technical information (for administrator): The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.
TF215097: An error occurred while initializing a build for build definition \YYY: An error occurred while receiving the HTTP response to ht*p://XXX. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.
Server logs provide with little info, at least we 've found nothing that helps us resolve the situation. Various searches in the Net were also not productive.
Does anybody had these/similar issues? Any ideas on how/where to look for a resolution?
Thank you very much in advance for any input!
Yeah it does sound like you have some connectivity issues. You can try enabling SOAP tracing on both the build machine and the server (if possible) to see if there is any error. If it still does not give you any new information, contact Microsoft by filing a Connect Bug to get help.
I am not sure if it will help you but I have ran into similar issues with build agents and ended up just deleting and re-creating the agent. You may try deleting your controller/agent and adding it back in. A brute-force solution but a good starting point. If that doesn't resolve the issue at least you can eliminate the controller/agent as the issue and take a look at network/server related issues.
Today is a happy day, since we managed to get to the bottom of the matter. Sorry #Duat that I'm taking away the 'answer' checkmark - but it turned out that the problem was quite different from what you (and anybody else) has predicted.
In my last update I was about to forward the matter to MS, when we realized that our Firewall was misbehaving in the name resolution. So we assumed this was the culprit & awaited for this to resolve. After this was resolved, we STILL had the same issues and we went again re-examining the situation.
We isolated the problem within our Build Process, more specific with a custom code activity included in our build solution.
I had implemented a code activity that would kick in at the final steps of every build. This activity was about gathering BuildDetails about the running build & add them as a new line in a 'BuildLog.xls'. Implementation made use of Microsoft.Office.Interop.Excel.This excel sheet resides in another server (NOT on the Servers where the controller/agents reside).
During development of this activity I was faced with issues like this, but after I was done no instances of EXCEL were left hanging. So I thought this was done & dealt with.
With try & error, we observed that when this activity wouldn't ran, no problems would occur.
With this activity running, the very first build after a build-controller reset would succeed, any next build had a certain chance to fail. Once any build failed, no other would succeed until another build-controller reset.
I have only a general understanding of what the problem was (Excel-call is DCOM, TFS services are WCF : How on earth would they interfere?! Why would this sometimes succeed and sometimes fail?! ).
The provided diagnostics were no help either, in fact they mislead us into a loop that continued for months.
If I ever find the time, I 'd like to cleanly reproduce the error & make a Server Fault question out of it...
After removal of this activity it works! I now searched in SO & found this, where J.Saunders comments: "In general, you should never use Office Interop from a server environment". It's ironic that once you get to the bottom of any difficult issue, the whole universe seems to have known about it except you...