When trying to restore my backuped TFSCollection via Administration Console (attach collection) the attachment fails. (NullReference Exception)
Are there any problems when restoring collections without the original configuration database?
The Collections is listed, but state doesn`t change from "offline", even when i tried to re-run the job.
When looking into [TFSCollection].[tbl_projects] via Management Studio I can see all projects.
When trying to restore the collection via
TFSConfig RegisterDB /sqlInstance:DataCenter\MSSQLServer /databaseName:DataCenter\MSSQLServer;Tfs_Configuration
I get the following error:
The following exception was caught while trying to validate the database: Keyword not supported: 'tfs_configuration;integrated security'.
Or when i run:
TFSConfig recover /ConfigurationDB:DataCenter\MSSQLServer;Tfs_Configuration /CollectionDB:DataCenter\MSSQLServer;Tfs_TFSCollection
The following error occurs:
TF246017: Team Foundation Server could not connect to the database. Verify that
the server that is hosting the database is operational, and that network problem
s are not blocking communication with the server.
Maybe I´ve run into some serious problem when installing TFS Service Pack 1.
What could i do to restore my TFS?
Even the import in my virtual enviroment fails. See the logfile.
If anyone had the same problem, take a look at http://support.microsoft.com/kb/2516423.
If you cant access your collections you could try.
TfsConfig updates /reapply
To start the TFS Job Agent you can run.
TfsServiceControl unquiesce
Or if the "Serviving" State doesnt change you could try this.
TfsConfig diagnose /scope:updates
TfsConfig updates /reapply
Hope this could help..
Related
I am using AWS Elasticbeanstalk for my project.When I uploading new version app it is giving error
Update environment operation is complete, but with errors. For more information, see troubleshooting documentation
My IAM role has AWSElasticbeanstalkFullAccess
Then why I am getting this error.
Thank in advance
I had the same issue.
I did the following and it worked.
From Elastic Beanstalk environment page, I chose to Rebuild the environment (Actions > Rebuild Environment)
Deployed the new application version.
A number of things can result in this, including issues with .ebextensions files.
Troubleshooting tends to be iterative, since logs are frequently not created or inaccessible.
Things to try:
Roll back to a previous application version and verify any changes to .ebextensions are valid
Rebuild the environment (Actions -> Rebuild Envrionment) in the EB console. This frequently enables EBs log snapshot facility to recover such that you can get further insight into what might be amiss.
You can try digging what the error exactly was by getting the logs of the event in the 'eb-engine.log' file. In my case I got this error and follow one answer to solve it. You can try 'eb logs' command also to get detailed info.
I need your help on the following issue. I'm installing a software (which uses mysql) and it fetches me the following error during installation:
I install the software, during install it says to name the project, I input 'drilling' as name, the process goes on and after a whilee I get:
"Create project failed: Setup was unable to create the trusted drilling account for localhost\drilling" (Note: 'drilling' is the project name)
When I press OK, the installation goes on and finishes. After running the app it says:
"Setup the DB connecton first".
I go to options and there are 2 options: Local DB and Network Server. When I choose Local DB it says Can't find any suitable DB in your local machine! When I choose Network Server it allows me to choose the project DRILLING and when I press Test Connection it says "Test connection not successful".
Can you help me with this problem?
I understand that my explanation might look like very messy, but I did my best..
After fresh installs of Plastic SCM and MySQL, I try to change the database backend to MySQL but consistently get the following error.
The database rep_1 can't be created. Check the server log (plastic.server.log). Error: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. at Codice.CM.Data.BaseDataManager.CreateSingleRepository(Int64 repId)
at admintool.DatabaseCopier.Start()
at admintool.DatabaseMigrator.MigrateDatabases()
at admintool.DatabaseMigrator.Start()
Any ideas? How can I set up MySWL or SQL Server? I have Sqlite working but need to switch.
It seems your MySQL installation is throwing a timeout exception, some ideas:
Is the access granted for the user you specified???
Try changing the server name for an IP (Sometime the DNS can do ugly thing), or if you specified an IP or localhost try specifying the machine name.
Review the server log to get more info (plasticd.log.txt)
If you want to try MySQL or SqlServer you can follow the following tutorials, it's very easy, it doens't use the Plastic SCM admin tool but it's more powerfull since you can specify more parameters:
SqlServer: https://www.plasticscm.com/documentation/administration/plastic-scm-version-control-administrator-guide.shtml#ConfigurePlasticSCMwithMSSQLServer
MySQL: https://www.plasticscm.com/documentation/administration/plastic-scm-version-control-administrator-guide.shtml#ConfigurePlasticSCMwithMySQL
Going back to your problem, you can try the following, I guess that your db.conf file (inside the Plastic SCM server directory) is now trying to connect to MySQL (check it by opening it and reviewing the provider tag), then try to start the server in console mode, in order to do it, open an admin command line window, cd to the Plastic SCM server directory and type:
"plasticd.exe --console"
Do you see any error? From a different command line window type "cm lrep", can you see the default repo? If not, review the server log (plasticd.log.txt) to find out the issue.
Alternatively you can send all the log you can find (plasticd.log.txt) to the Plastic SCM forums www.plasticscm.net the community and the Plastic SCM guys will help you on this.
At the start of the year I pushed to setting up TFS for a more structured approach to things (before, everyone would change things as they went, obviously A Bad Thing). I set up a very basic single server TFS 2010 installation. The TFS databases resided on one of our Dev servers (SQL 2008).
Everything went well until:
We uninstalled SQL 2008, installed SQL 2008 R2 and reattached the databases. Since then TFS has been impossible:
The clients (SQL Mgt Studio and VS2008/2010) could no longer connect (error 404 not found)
http://localhost:8080/tfs/ gave:
"Team Foundation services are not available from the server.
Technical information (for administrator):
The request could not be processed because the application is not configured correctly. No service host is available for the request."
Team Foundation Admin Console finds the collections, everything SEEMS ok.
In an effort to jumpstart things:
I restarted the website and it's application pool
I rebooted the server
No effect.
Then I stopped the collection (that worked) to re-enter the database information, save it and start the collection again. However, it kept hanging on the save. I tried to detach the collection, but that didn't do anything. So now I have a stopped collection with the following activities:
Prepare Collection (Success)
Create Collection (Success)
Servicing Collection (Queued)
Detach Collection (Queued) (3 times, since I tried this a couple of time)
and nothing is budging.
I have all source in my local folder, so in extremis I can delete and uninstall the whole thing and start over, but... I rather not.
Any way to unblock this?
ok, This was solved by re-adding the TFS machine account to the new SQL Server installation using
EXEC master.dbo.sp_grantlogin #loginame = N'DOMAIN\MACHINE$'
as detailed here. From then on all tasks proceeded as they should..
What tipped me off was the following error in the Application Log:
TF53010: The following error has
occurred in a Team Foundation
component or extension: Date (UTC):
22/06/2011 18:07:22 Machine: AZT-TS-02
Application Domain: TfsJobAgent.exe
Assembly:
Microsoft.TeamFoundation.Framework.Server,
Version=10.0.0.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a;
v2.0.50727 Service Host: Process
Details: Process Name: TFSJobAgent
Process Id: 2980 Thread Id: 3804
Account name: NT AUTHORITY\NETWORK
SERVICE
Detailed Message: There was an error
during job agent execution. The
operation will be retried. Similar
errors in the next five minutes may
not be logged. Exception Message:
TF246017: Team Foundation Server could
not connect to the database. Verify
that the server that is hosting the
database is operational, and that
network problems are not blocking
communication with the server. (type
DatabaseConnectionException)
Good times,
Try running the following command:
TFSConfig registerDB /DatabaseName:Tfs_Configuration /SQLInstance:SERVERNAME /Continue
RegisterDB updates the name of the server that hosts the configuration database and in this case should resolve your DB issues. Another command you could try is RemapDBs.
Make sure you "Run As Admin" for these commands or they of course will not work.
I am guessing what is going on is attaching isn't going to be enough because TFS internal mappings no longer understands where your SQL Server db is.
Hope that helps.
Having some SSIS permissions issue.
I am calling the SSIS package in my .net console application with:
Package pkg = app.LoadFromSqlServer(packagePath, serverName, serverUsername, serverPassword, dtsEvents);
It is working when manually running it using the windows accout, but fails with the above call in my console application.
Shouldn't it work with the sql server sa account?
There are plenty of reasons for it to fail when run under different account, to avoid trying to fix it blindly, you should get the error information. It looks like you are supplying dtsEvent parameter - so your app should get the error message. Another way to get it to examine package.Error collection after execution, or enable SSIS logging and check the error log.
Once you have the error message, update the post :)
There is also a KB article dedicated to troubleshooting such errors:
http://support.microsoft.com/kb/918760/.
But it just lists lots of possible error causes - to find out your issue, you need to get the error message first.
This generally happens when you have sql queries that use linked server to access a database on a different server.