Sorry, something went wrong (when adding a site-collection) - sharepoint

I am working on a group project using Microsoft Azure VM that has following issue when we try to create a site collection from Sharepoint Central Administration 2013.
Cannot complete this action
I looked trough the Sharepoint logs and have searched online, but couldn't find a resolution. Please advise and let me know if you need further information.

Related

How do I remove a user from TFS 2018?

I have a user that is getting alerts from TFS. When I looked at [Tfs_Configuration].[dbo].[tbl_Identity] I found several people that I have no idea how they got in there.
When I do a backup of the TFS server through the console, they get an email notification.
How do I remove them? I have tried attempting to sync with JobService, rebooted the server, looked in AD at the person, and I've looked in TFS in User Management in the Console. They are not there. I can find them in TFS if I search for a Subscriber on a Project, but nothing in regards to backup or the like or a way to remove them from the entire TFS instance.
I have also looked a the Console and group membership for individual projects. They are not Team Foundation Administrators.
You do not: TFS/VSTS/ADO needs to refer to past users reference in work item, version control and other subsystems.
You can break your database in an unrecoverable way modifying the tbl_Identity table.
The only reasonable thing to do is to remove these users from all TFS (and Active Directory) groups so they only appears in old data. The TFSSecurity utility can help you identify which groups has a specific user.

Sharepoint 2007 deleted documents appear in search results

I'm totally new to sharepoint, My question is simple. I have a document library with some documents in it. When I delete a document from the library, this document still appears in search results. I solved this by running something called full crawl, I honestly don't know what this is. Do I have to do this every time I modify the documents in the library?
Reset your index, good guide here :)
http://sharepointnoob.wordpress.com/2009/05/27/reset-crawled-content-in-moss-2007/
Check the crawl logs for errors during the crawl.
Also try
Go to SharePoint Central Administration > Operations > Services on Server, stop the Windows SharePoint Service Search service
Started the Windows SharePoint Service Search service from SharePoint Central Administration and create a new search database
Re-associated the indexer to the content database from SharePoint 3.0 Central Administration > Application Management > Content Databases
Make sure that your crawl account does not have administrator level privileges to your SharePoint farm. If it does, it can see deleted items and can cause this issue to occur. It should just be a default user account with read permissions.
Yes, I guess you have to do this every single time you do any modification. At least this is how I do it/

How to find out where sharepoint is running from?

Our team has a sharepoint website and I need to maintain the shared documents on our site. Problem is, it was designed by someone else and I was just given the link to the team website. I have tried using search and setting alerts and both of these don't work. i googled trying to find out what's happening and everyone keeps asking me to go to central administrator. I don't see central administrator anywhere in the website(I have full access). I am thinking I have to go to the server where sharepoint is running from. How do I figure out where it is running from? Sorry, I'm new to sharepoint.
Central Admin is the website that SharePoint creates when you install the software. It generally runs on your main SharePoint web frontend. If you RDC to your main web front end and then click on Start, All Programs and then click on the SharePoint folder, you'll see Central Administration. Click on that and the website will appear. You must be a farm admin to be able to access the site.
It sounds like you may not be a farm admin though. Depending on the permissions you have, you should be able to see your team site's Shared Documents or other document libraries under All Site Content, which you can either see by clicking on Site Actions or find it on the bottom left of the web page (again depends on what modifications have been created).
You need to assign the sign-in user account the permission to check the Shared Documents and you need to get at least Contribute permission level to maintain the Shared Doc on the site.
For Central Administrator, you can either RDC to the Web Front End server where the SharePoint was intalled or visit that server IP:port or computer name:port(80 by default).
Hope this may help!
First of all,the link you got may not be a Central Administration link.It is probably a common site collection.If you have full control permission over this site collection, you should be able to maintain Shared Document.
About the question that where SharePoint is running from?
SharePoint must be installed in a server. Generally, only farm admin can access this machine. If you want to know or learn about it, and if you don't have farm account to access the server, you can contact your farm administrator.
Central Administration is also a site.But it is different. You can manage all web applications and site collections in Central Administration.So you can manage or modify your team site in Central Administration
Hope this helps.

TFS Error after migration - TF250016 on Reports Site in Sharepoint

Good day all,
We recently migrated from TFS2008 to TFS2010. We migrated our TFS_name databases and our WSS databases. We followed the migration steps and our upgrade was successful, except for a single piece regarding the project sites.
Whenever I go into a team project portal, I receive the following error when trying to access the "Reports" site.
TF250016: No access rights have been granted for the following site: http://<tfsserver>/Sites/<project portal site>. You must grant access rights between the SharePoint Web application and Team Foundation Server. You must also associate this site with reports and dashboards for a specific project in Team Foundation Server. For more information, see the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=147580).
I have gone through the TFS upgrade steps and made sure we followed every step and we are running of ideas. Can anyone point me in the right direction? We didn't notice this error as we are not using reports at this time, but it's something we would like to implement in the future.
Thank you
Edit
(to read in the comments)
You did a move from one server to another and upgrade your TFS Server.
It's most likely you didn't follow the "how to move a TFS from one hardware configuration to another" procedure, then you'r SQL Report Server is down or incorrectly configured (the SQL Connection strings in the Data Sources configuration are incorrect).
Follow the procedure I gave you for the SQS Server Resport Service part and you should be fine.

Unable to Deploy PerformancePoint Dashboard Page to SharePoint 2007

I'm creating a PerformancePoint (henceforth PP) Dashboard that contains a web report to be deployed to the a SharePoint web application that I had created. I followed the instruction in the link below.
Deploy a PerformancePoint dashboard to a SharePoint site
In summary, following the instructions in the link, I published the Dashboard to the PP site. Then, I added my account in PP as Creator in the Application level, Editor in both the Dashboard and the Web Report. In the SharePoint site, I added my account under Contributor. I even added the PerformancePointDefault.master just to be sure.
Now, when I deploy my Dashboard to a Report Library, I was able deploy the folder for the Dashboard, but not the Dashboard Page file.
I googled for this, but I could not find any article helpful.
UPDATE 2009-09-30:
I was able to resolve the issue by creating another site collection. Maybe the first site collection is messed up.
I had the EXACT same problem. I was about to take the best advice I could find and delete my site collection and create a new one from scratch, but by the grace of God, I had one final thought.
In our case, the site created was originally http://ServerName but we later added a host header (i.e. http://BiSite). I had been deploying the dashboard using the host header the entire time, so I decided to try using the original name of the site using the server name and viola, the dashboard finally deployed correctly, pages and all.
When you publish a dashboard in MOSS, you have to make sure that you select Publish a Major Version in the dashboard page's drop-down in the report library.
Why is this a community wiki? Seems like there should be a right answer to this question...

Resources