I've set up Team Foundation Server to be used as VCS for Dynamics AX 2009.
Now I tried to install the AX 2009 Team ID Server (on the same server as TFS), and get the following error during setup, no matter what I do:
Unhandled exception has occurred in your application. If you click
Continue, the application will ignore this error and attempt to continue.
If you click Quit, the application will close immediately.
Cannot drop database "AXTS" because it is currently in use.
The error is kind of stupid, since the AX Team Server installation created the database itself!
I'd say some error did occur, and the installation is trying to drop the database (without success, since the installation itself is using it).
Can anyone help me to get the AX Team Server installed?
Oh swell, I scrapped SQL Server 2008, used SQL Server 2005 instead, now it works.
I got no idea why it did not work with SQL Server 2008, though.
Related
I attempted to install Microsoft Dynamics CRM 2013, but I get the error shown in the image
When I drill donw into the error log I noticed the following message:
Installation of Microsoft Visual C++ Runtime failed. Exit code: 5100.
Result: Asia
As a result I decided to abort the installation CRM 2013 and tried to install Microsoft Dynamics CRM Setup. Everything appears to be going in the right direction, however I keep on getting the error that the Download failed for SQL Native Client, see image.
I have turned off the Firewall to make sure that the Firewall was blocking the download.
Any thoughts on what might be going wrong?
I am tring to install on Windows Server 2012 R2 with SQL Server 2014
To resolve this problem I manually downloaded the SQL 2008 native client from Microsoft site.
Make sure to restart the Server post installation.
I am sure that someone was successful to deployed SSRS report on the server where
SSRS is configured to access Oracle database.
I developed report on my machine where I have Visual Studio 2017,
ODTwithODAC122011 64-bit; 32-bit ODT withODAC122011. I connect to Oracle database and can run report.
After i deployed this report on Windows Server 2016. i got an error "An error has occurred during report processing. (rsProcessingAborted)
An attempt has been made to use a data extension 'ORACLE' that is either not registered for this report server or is not supported in this edition of Reporting Services. (rsDataExtensionNotFound".
I tried to complete the same ODAC install as on my machine.
1)Installed ODTwithODAC122011 64-bit - configured TNS name.
but with step
2) i tried to install 32-bit ODT - I received error that i need to install Visual studio to proceed with installation.
Do i really need VS on the server? What is the possible solution you can share?
thank you --Angelika--
with only the Oracla.DataAccess library should be enough, on the root of the service. Be aware the versions be the same as indicated in the project references
After cloning a 2010 TFS server, upgrading the clone's OS to 2012R2, upgrading SQL Server to 2012 SP2 (11.0.5343), uninstalling TFS 2010, and upgrading to TFS 2013 with update 5, we are running into issues starting the Build Service on the clone.
I've removed the agents and build controllers referencing the other original server through Manage Build Controllers, in Visual Studio 2013.
I've tried to use the TFS 2013 upgrade wizard and it fails when attempting to start the build service so I tried to unconfigure: "tfsconfig.exe setup /uninstall:TeamBuild" and reconfigure through the TFS 2013 upgrade wizard but it yielded the same result.
The TFS database server, Build Server, controller, and agent are located on the same box
For measure, I've even deleted the agents, controllers, and Unregistered and Registered the Build Service in the Team Foundation Server Administration Console as both the batch account used on the original server but that failed so to rule out authentication, I used my domain account (I'm a Local Admin, SQL Server Admin, and TFS Admin) but still had the same result with both accounts.
The Windows event log states “Service cannot be started. The handle is invalid”.
I'm not sure what else could be missed does anyone have any pointers?
There were over 100 Microsoft patches/updates applied over the weekend and the issue went away. Microsoft confirmed that the issue was related to the OS, not the TFS configuration or installation/upgrade.
Thanks for all your suggestions. Hopefully this will help someone else out if they are in the same situation and spinning wheels to find the answer. Keep your systems as up to date as possible!
Try to remove build service by going to Team Foundation Server Administration Console, select server name, and click Remove Feature, to remove build service feature, then re-configure it.
I just got a new Windows 7 computer with VS 2012. My old box was Windows XP with VS 2010. I copied over my project and had VS2012 upgrade the project and get the following error when running the ASP.NET MVC 3 application:
[Win32Exception (0x80004005): The wait operation timed out]
[SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 - The wait operation timed out.)]
[ProviderIncompatibleException: The provider did not return a ProviderManifestToken string.]
[ProviderIncompatibleException: An error occurred while getting provider information from the database. This can be caused by Entity Framework using an incorrect connection string. Check the inner exceptions for details and ensure that the connection string is correct.]
That was the order of the messages. I am connecting through EntityFramework (code first). The connection string was working just fine in VS2010:
Data Source=xxx.xxx.xxx.xxx; User ID=xxxxxx; Password=xxxxxxxxx; Initial Catalog=xxxxxxxxx; MultipleActiveResultSets=true
I have been searching for hours with no real solution. The only one I haven't tried is to remove VS 2012 and .NET 4.5. That would be a problem since then I can't code. I have tried to remove .NET 4.5, but then VS2012 doesn't start. I have installed .NET 4.0.
I have installed (only listing software based on what I have see in searches):
VS 2012
Windows 7
SSMS 2010 (which was initially installed after VS 2012)
I have done a repair on VS2012 as well. I have not uninstalled and reinstalled it.
Any thoughts? I am going nuts here. Right now I have a quad-core pc that can remote desktop REALLY fast to my old clunker.
NOTE: My firewall is off. I have Symantec Endpoint Protection and this is connecting to a live SQL server, so I know it's running.
Amazingly, this worked:
netsh Winsock reset
See Can't connect to database after installing VS 11 Pro Beta
I am currently working on a TFS 2008 to 2012 upgrade. Here is my situation: my current TFS 2008 box is Server 2K3 with SQL Server 2005 backend. I am not entirely sure what my upgrade paths are but I think the following 2 scenarios are the most likely:
Migrate the databases from SQL 2005 to SQL 2012 and then point TFS 2008 at the new SQL Server. From there I can upgrade TFS 2008 to 2012.
Spin up a new Server 2008R2 box and do a clean install of TFS 2012 with a SQL Server 2012 backend.
The network guys would really like me to do option 2 because they want to decommission the Server 2003 box but my concern is how would I get all of the data in TFS 2008 over to the TFS 2012 instance? I have looked around the MSDN and Google but I haven't come across any documents that explain how to do this kind of upgrade.
Additionally are there any pitfalls that I should be on the look out for?
Any help would be greatly appreciated!
The Microsoft Documentation doesn't make this abundantly clear so for anyone in the future that is in a similar situation this is a great little how to. Some of the screens vary to what you actually see but it is mostly spot on.
Some points
If you spread your Data and Application Tier across multiple servers make sure the user account you specify for 'Report Reader Account' has access to both servers and has the 'Log on locally' permission.
Pitfall: After getting TFS 2012 configured I was getting a strange URL exception when VS2012 attempted to connect to the imported project collection but not when trying to connect to a project collection created from within 2012. A server bounce corrected this problem.
All and all the process is very straightforward and TFS2012 stands up pretty quickly.
There is great documentation on MSDN: http://msdn.microsoft.com/en-us/library/ms404860(v=vs.100).aspx