Suddenly my sharepoint site showing this error "Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT)) "
I am running my site on MOSS 2007 (version 12.0.6425.1000) and SQL server 2008 R2.
I was getting a similar error but running SharePoint 2007 on Windows Server 2003 SP2 with SQL 2005 as the database. This is an organisation environment where all users access SharePoint intranet via the domain so I gave access to the NT AUTHORITY\NETWORK SERVICE account access as a db_owner to the SharePoint content database, Search database and that eliminated the error.
Related
I am trying to configure Release Management Client to work with a Release Management Server for Microsoft TFS 2013 on a Windows Server 2008 R2 Standard.
I installed (without any errors) the following two from our subscription downloads:
en_release_management_server_for_team_foundation_server_2013_with_update_4_x64_web_installer_5920525
en_release_management_client_for_visual_studio_2013_with_update_4_x86_x64_web_installer_5920526
I have not installed any Microsoft Deployment Agents.
I have installed and configured the RM server for a SQLExpress db (different from the TFS db in our case) and for now I used my own network credentials (being a member of Administrators group on the server and a member of Default Collection Administrators on TFS, with "Make requests on behalf of others" set to "Allow" on TFS).
When I copy the RM Server URL from "Configure Release Management Server" screen (http://xxx:1000/ReleaseManagement) and paste it into a browser, the page loads without any errors.
However, when the same URL is used in RM Client Configuration, I get an error: "The server specified could not be reached":
We have VS2012 on the server and VS2013 Ultimate on my own dev machine.
I tried installing and configuring the client on both the server (Win Server 2008 R2 Standard) and my dev machine (Win 8.1 Pro), and I still get the same error (so I assume the version of VS is not an issue).
Looking at the event log, I get two errors.
ERROR ONE:
The remote server returned an error: (404) Not Found.: \r\n\r\n at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at Microsoft.TeamFoundation.Release.Data.WebRequest.PlatformHttpClient.EndGetResponse(IAsyncResult asyncResult)
at Microsoft.TeamFoundation.Release.Data.WebRequest.RestClientResponseRetriever.EndGetAsyncMemoryStreamFromResponse(IAsyncResult asyncResult, IPlatformHttpClient platformHttpClient)
.... [edited out for brevity]
Process Name: C:\Program Files (x86)\Microsoft Visual Studio 12.0\Release Management\Client\bin\ReleaseManagementConsole.exe
ERROR TWO:
Error communicating to the web server URL: http://xxx:1000/ReleaseManagement/account/releaseManagementService/_apis/releaseManagement/
Indeed, when I enter that URL in a browser, I get "404 - File or directory not found". Here is what the site structure is:
What I should do to be able to configure our Release Management Client without errors, please?
Additional observations:
I cannot see "Release Management" role on our server, but have seen in mentioned in relation to RM installs.
The client installer reads "Release Management Client for Visual Studio 2013 Update 4", whereas instructions here indicate it should be "Release Management Client for Team Foundation Server 2013 Update 4". Surprisingly, when I ran the installer recommended by that article, the title again read "...for Visual Studio" as opposed to "...for Team Foundation Server".
Many thanks in advance!
You're entering the wrong URL. The URL should be http://<RM Server Name>:<Port>. No /ReleaseManagement/.
The /ReleaseManagement/ folder is not for the desktop client, but rather for the approval dashboard.
Over the weekend, our network admin install updates on our Windows Server 2008 R2 server. After the updates, TFS can no longer connect to Sql Server. Both TFS and Sql Server are on the same box.
I am getting the following error when trying to connect to the http://mytfsname:8080/tfs/ :
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.
In the TFs Admin Console, I tried to connect with the NETWORK SERVICE account, which results in the following:
Exception Message: The database is being upgraded to the
Tfs2010.SP1.KB2564498.P#5 schema. The database cannot be used until
the upgrade is complete. (type DatabaseSchemaException)
Digging into the event logs, there are about 20 errors right after the server was restarted:
Error in Template (C:\Program Files (x86)\Microsoft Visual Studio
9.0\Common7\IDE\ItemTemplates\Web\VisualBasic\1033\AdoNetEntityDataModelVB_ASPNET.zip),
file (ModelObjectItemVB_ASPNET.vstemplate). Invalid template element
(TemplateID) value
(Microsoft.Data.Entity.Design.VSTemplate.ModelObjectItemVB_ASPNET).
Then I start seeing the TFS error:
TF53010: The following error has occurred in a Team Foundation
component or extension: Date (UTC): 2/15/2015 7:00:22 PM Machine:
xxxxxxx Application Domain:
/LM/W3SVC/8080/ROOT/tfs-1-130685004138949511 Assembly:
Microsoft.TeamFoundation.Framework.Server, Version=10.0.0.0,
Culture=neutral, PublicKeyToken=xxxxxxx; v2.0.50727 Service Host:
Process Details: Process Name: w3wp Process Id: 6180 Thread Id:
7364 Account name: NT AUTHORITY\NETWORK SERVICE
Detailed Message: Application Request Processing Started
Server Version = Microsoft.TeamFoundation.Framework.Server,
Version=10.0.0.0, Culture=neutral, PublicKeyToken=xxxxxxx Service
Account = NT AUTHORITY\NETWORK SERVICE Machine Name = XXXXXXX Product
ID = xxxxxxxxx License Edition = xxxxx
Exception Message: The database is being upgraded to the
Tfs2010.SP1.KB2564498.P#5 schema. The database cannot be used until
the upgrade is complete. (type DatabaseSchemaException)
I have tried the following:
Reinstall TFS (repairing) '
ReInstall TFS SPI 1 (failed)
Delete TFS Cache
When I want to connect to a server in Microsoft Test Manager I got this error message:
Unable to connect to server 'tfsserver:8282'. Check that the server name is correct and that you have access to the server.
This is Microsoft Test Manager 2010.
I can access tfs server in that url throughout a web browser, using Visual Studio 2010, using Team Explorer 2012.
The TFS server is installed in Windows Server 2008 R2 Standar
The TFS installed version is: 11.0.50727.1 (RTM)
Configured virtual directory is: \tfs
Configured ports are: 8282
Service account: NT AUTHORITY\Network Service
Authentication: NTLSM
Notificacion url: http: //tfsserver:8282/tfs
Server url: http: //localhost:8282/tfs
Web Access url: http:// tfsserver:8282/tfs
Machine name: TFSSERVER
My PC and the server are under a windows domain. My domain user is included in the management console users in TFS.
What can be wrong?
this is compatibility issue you need
tfs 2010,test manager2010,team explorer2010
or
tfs 2012,test manager2012,team explorer2012
and the second solution for this is to download update patches from Microsoft Website to enable upward or downward compatibility.
Does anyone know the resolution to the following error. In this scenario, TFS will be using a local report server instance which points uses a separate SQL Server database engine instance.
An error occurred while querying the
Windows Management Instrumentation
(WMI) interface on the following
computer databaseServer. The
following error message was received:
Access is denied. (Exception from
HRESULT: 0x80070005 (E_ACCESSDENIED)).
You can grant the priveleges temporarily at install time and then remove them. I had the same issue and that appears to be the only solution.
I am unable to access Sharepoint Central Administration.
I installed MOSS 2007 successfully on Windows Server 2008 (IIS7 and SQL Server 2005), I launched the admin and got "Cannot connect to the configuration database" error.
Application pool is using NetworkService account which has access to SQL Server.
I can access the configuration databases through SQL Management Studio. SQL server is on the same machine.
Any help, suggestions on how to solve the problem? I am very new to SharePoint.
Maybe try running the SharePoint Products and Technologies configuration wizard again to see if that highlights what the issue might be.