I'm trying to delete a subsite in my site collection, but I get an error that says "Can not reach the Messages.xml file!"
A few days ago I was able to delete a site, but now it seems to be impossible to delete any sub sites.
If I use the stsadm deleteweb with force parameter I'm able to delete, but I would like to be able to delete sites via the interface.
I'm thinking that the error might be coming from some feature because the error message is in english and all other Sharepoint msg is in danish(Running a danish version of Sharepoint 2007)
Any suggestions?
Regards
Birger
The problem was happening because the MSITDeleteFeature had been installed some time ago and after moving the site to a new server som of the feature was not correctly installed on the new server.
The missing Messages.xml was a part of the feature and should have been placed in this folder
C:\program files\common files\Microsoft shared\web server extensions\12\template\layouts\1030
After copying the file to the folder the problem was solved.
/Birger
Related
We frequently use Excel to perform bulk updates of data in TFS. Up until very recently, the Team Foundation Add-In has worked very well. However, it has started failing in several ways:
It will connect to the server, but attempting to connect to any
project causes Excel to crash, producing a Watson report in the
Windows Application Event Log.
If I restart Excel, it reports that it is running into problems with
both the shim and the add-in, and offers to disable it. If I do not
disable it, I still can't connect to a project.
Eventually, the add-in refuses to load at all, until I use the
Options dialog to manually add the COM add-in back into the
application. Doing so produces the same results (Excel crashes when
attempting to load a project).
I have taken the following steps in an attempt to resolve the issue:
Removed and completely reinstalled Office.
Re-registered the add-in component.
Uninstalled and reinstalled Team Foundation Office Integration.
None of these have produced a fix to the issue.
Does anyone know how to resolve this issue?
P.S. If this is not the correct "stack" for this question, kindly point me to the correct one on the exchange. Thank you.
If you are reading the accepted answer and it still isn't working, here's an additional tip. I had the EXACT same problem and saw that same link to clear the cache from numerous sites, bit it didn't work.
Here's the thing. I don't think that article lists ALL of the places that cache can be hiding on your machine. I deleted the cache folder in two different places on my machine and had given up on that as a solution.
Then I searched my entire hard drive for any folder with "Team Foundation" in the name and found a couple more buried in other hierarchies. Deleting these FINALLY solved the problem.
Here are some folders to look for, but like I said, check the entire drive
c:\users\yourlogin\AppData\Local\Microsoft\Team Foundation
c:\Program Files\Common Files\Microsoft shared\Team Foundation Server\
c:\users\yourlogin\AppData\Local\Temp\Microsoft\Team Foundation
The actual cache folder will be nested another level deep under a numbered folder named with something like "7.0" or "8.0" delete the cache folder from every one you find under every number.
In general cleaning the caches on your client machine will resolve such problems, including the TFS and VS caches...
To clean the caches, please see How to clear the TFS cache on client machines
When starting VS 2012, I'm getting this error in the Output window:
> TF205020: Could not connect to server ‘https://Xxxxxxxx. This server was used in your last session, but it might be offline or unreachable. Confirm that the server is available on the network. To attempt to connect again, or to a different server, click ‘Connect To Team Foundation Server’ in Team Explorer or the Team menu.
>
> The server returned the following error: TF400324: Team Foundation
> services are not available from server https://Xxxxxxx. Technical
> information (for administrator): The underlying connection was
> closed: Could not establish trust relationship for the SSL/TLS secure
> channel.
(Xxxxx used for server name here).
This is a TFS server I used on a contract project a couple of months ago - I'm no longer working with them so I want it just gone. I removed the server in the Team / Connect to Team Foundation Server... dialog but this seems to live on in VS's memory somewhere.
Anyway to make it be gone/gone?
I (finally) was able to remove all my bindings and references to an old TFS server by doing the following:
Delete the contents of the folder, %LocalAppData%\Microsoft\TeamFoundation\Cache.
As someone else suggested, search for all occurrences of LocalItemExclusions.config within %LocalAppData%\Microsoft\Team Foundation\, and remove any/all "TeamProjectCollection" elements that reference the obsolete server in their uri="..." attribute.
Edit the file, %LocalAppData%\Roaming\Microsoft\VisualStudio\11.0\TeamExplorer\TeamExplorer.Config. Remove all "Server" elements having a url attribute that references the obsolete server.
I did this for both VS 2010 and VS2012. It was not until I completed the third step that the error mentioned by the original poster went away, and Visual Studio started quickly, as it always used to.
I was unwilling to use the nuclear option as described in the first part of superlime's answer to this question--deleting the entire contents of "%LocalAppData%\Microsoft\Team Foundation\".
Instead I followed the second part of his answer--deleting the contents of "%LocalAppData%\Microsoft\Team Foundation\N.N\Cache", which I did for all versions (N.N) found.
That helped, but wasn't quite enough. I also had to do the following:
Search for all occurrences of a file called LocalItemExclusions.config within "%LocalAppData%\Microsoft\Team Foundation\" and its subfolders.
Remove from those files, in their entirety, any <TeamProjectCollection> elements that reference the obsolete server in their uri="..." attribute.
That was enough for me--however, I can imagine other references lurking, if you've been using TFS targeting that server for awhile. If the above steps are insufficient, you might simply try searching for additional references in all files (excluding logs) in that directory hierarchy, and surgically removing them.
I found that I needed to do both steps to remove this from VS 2012 :
Delete the content of the folder %LocalAppData%\Microsoft\TeamFoundation\Cache
Delete the content of the folder %LocalAppData%\Microsoft\Team Foundation\
Much thanks to both contributors for their help. Shame to Microsoft for not insuring that removing Team Foundation occurs cleanly.
Bit of a "nuke from orbit" option, but try deleting the contents of the TFS client cache. Should be located in this location:
%LocalAppData%\Microsoft\Team Foundation\
According to this blog post (which is for 2010, and a little stale on version info), you should just delete the contents of the cache folder, not the cache folder itself (or the parent dir).. So theoretically you'd just want to delete everything inside of:
%LocalAppData%\Microsoft\Team Foundation\4.0\Cache
I got a backup of a Sharepoint 2010 site that I created from our client's production server so that I can make some new changes to it on my staging server.
I can restore the site collection from the backup without a problem but when I try to create a backup of the same site on my staging server, I always get the error "Operation is not valid due to the current state of the object".
Before the error is given however, a small part of the backup file is created. If I try to run the Backup-SPSite again, it always fails at the same point and the corrupt backup files are always the same size.
Going through the logs it looks like the problem might be related to user permissions. I wonder if it's possible that the user permissions, user data, etc that came over from the client's production server are somehow screwing the backup process now because the same data cannot be found on my staging server.
The same error is mentioned here http://technet.microsoft.com/en-us/library/ee748617.aspx but UseSqlSnapshot parameter doesn't work anyway in my case.
I've been hitting my head against the wall with this problem and would appreciate if anyone has any advice on what might help! :)
The setup:
Windows Server 2008 R2
Sharepoint 2010 Server (no SP1 because it hasn't been installed on the client's production server)
Microsoft SQL Server Express Edition
Cheers!
The backup process started working after I checked in a file that had been checked out by a user on my client's production server.
I found out what file that was by opening the corrupted backup file and looking at the title of the last entry.
I have created an asp.net web application on my local machine and I am deploying it to sharepoint. For that I am refereing the following
Deploying ASP.NET Web Applications in the Windows SharePoint Services 3.0 _layouts Folder
[http://msdn.microsoft.com/en-us/library/cc297200.aspx]
Its works perfect on my local machine but when I was trying to deploy the same on clients machine it was giving me the "An unexpected error has occurred." Error.
The scenario is, There is not visual studio install on my clients machine so what I was doing is I simply copying my solution folder in 12'hives LAYOUT folder along with the bin folder. Then when I was try to access it by hitting the URL
http://[machineName]/_layouts/[MyCustomFolder]/default.aspx it was giving me the error mention above.
Can anyone help me to solve this issue..?
Thanks in advance..
Sachin
Unexpected error might be anything, You need to see what is the root cause of the Error,
Open the Web.Config file of the IIS SharePoint WebSite
Search for the CallStack and change it to CallStack="true"
Search for the CustomError and change it to CustomError="Off"
Browse the page you will get to know the actual issue that causes the error
You yourself can rectify it , it might be as simple as missing dll
Try to watch the logfiles, set logging level to maximum to be sure you see what sharepoint says about your page.
To do that, if you have access to the server:
open SharePoint Central Admin
go to Operations tab, select "Diagnostic logging"
select category 'All' and change the trace log level to 'Verbose', save changes
reset IIS server (for the purpose of a clean experiment)
open \\server\c$\Program Files\Common Files\Microsoft Shared\web server extensions\12
logs and order by modification date
try to load your webpage in /_layouts folder, see the error again
open the newest logfile you can see and search for [MyCustomFolder] name
Then post the error message here.
An unexpected error can have multiple reasons.
Go to C:\inetpub\wwwroot\wss\VirtualDirectories\80
Open Web.Config
Change
<SafeMode MaxControls=”200″ CallStack=”false”
to
<SafeMode MaxControls=”200″ CallStack=”true”
Turn off custom errors
<customErrors mode=”Off”/>
I know that is an old question but for me the fix was to stop and start again the SharePoint Web Application from IIS.
I remembered that there is a log file that you can check for Sharepoint Services 3.0. I don't remember where I can find this. The reason I ask this I have an error when implementing the new template and it works on one, but not on the other machine. The error on the page is very generic: "The template you have choosen is invalid or can not be found".
Thanks
SharePoint log files are usually in the "Logs" folder in the '12 Hive' which by default is in C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\Logs.
It's easier to have the error displayed completely. You can enable this by modifying the web.config.
Find the SafeMode entry in your web.config and change CallStack="false" to CallStack="true". Then find the customErrors entry and set mode to mode="Off".
Now errors will be shown as a complete ASP.NET error screen