In our Ms EPM 2010 setup, as an administrator I am unable to delete a project.
Initially, in order to delete,I had to check-in the project. When I did so, it showed me that the project is checked out to the admin account. When I logged in using that admin account, I coudlnt do anything as it says that its checked out to me/admin in another session.
When I open the project detail page for this project I see this on the top:
Status: Checked-out to you in another session since 18/09/2014 10:17 Last Modified: 25/08/2014 09:40
Now I cant delete it, cant force check-in. Any ideas?
Resolved.
I restarted the "Microsoft Project Server Queue Service 2010" service, first on the App Server and then the same named service on the Web Server. After that I checked if the project was checked in or not - it wasnt, it still was showing checked out to admin. I ignored it and opened the "Delete Enterprise Objects" page.
It worked this time!
So I am guessing that restarting the services did the trick!?
Related
I have a 2013 SharePoint hosted app. I made some changes and went through the update process (changed the app version, kept the id the same, uploaded the package to the app catalog and updated the app immediately through the site contents of the site collection). Everything worked fine. However, when I go through the same process again with an even higher version, the app says that it's updating and after completion everything is the same. In fact, the app even shows that a new version is available. If I click "Get It", it says that it's updating for about 5 to 10 minutes and then nothing changes, same old app, same old files, same old version number, still says that a newer version is available. I get no error messages.
Any help or pointers are greatly appreciated, of course. Thank you.
UPDATE: In Central Admin. I started to monitor the app and found that there were failed upgrades with an error message of "There was a problem accessing the file system on the server."
We are using TFS2010 (for source control only), and until recently everyone was using VS2010. Our developers just installed VS2012.
Pulling down code works fine in Visual Studio. When you go to "Pending Changes" in Team Explorer, we are seeing TF201072: A user or group could not be found. Verify that the users and groups used in your work item type definition have been added to Team Foundation Server., twice, at the top. We can still check-in code from VS - seems this error is ignored.
However, we are unable to shelve changes - when you attempt to shelve, the same error comes up in a popup, and the shelveset is not saved.
We can shelve using the command prompt (tf shelve), and can still shelve using VS2010, so it doesn't seem to be a permission issue. Also, the TFS administrator is not seeing the error message, and can shelve from VS2012 with no error.
Any thoughts as to what could be causing VS to error out here? We've tried clearing out the TFS cache, creating a new workspace, and gone over every option we could find in Visual Studio.
I had the same issue. Tried many different stuff from web sites and non of them helped. Finally find the solution for this. Follow these to make it work:
1) Create temporary AD User
2) You will need to transfer all old user configuration into a new temporary account. If you are OK with using the temporary account you may just keep it and get rid of old account. Go into the machine that TFS is installed and Run this command: TFSConfig identities /change /fromdomain:mydomain /todomain:mydomain /account:oldAccount /toaccount:temporaryAccount
(TFSConfig is in C:\Program Files\Microsoft Team Foundation Server XX.0\Tools\)
3) If you don't want to use temporary account you will need to convert from temp account to your old account. To do that run the same command wit changing the user names:
TFSConfig identities /change /fromdomain:mydomain /todomain:mydomain /account:temporaryAccount /toaccount:oldAccount
That's all you need to do.
Here is the setup:
We had a one server TFS solution previously. We split each part out so the DB, TFS and the Build Service each have their own server now.
I manually restored the TFS DBs to the new server. I installed the app tier on the app server and the Build Service on another server. As usual, everything works fine on my computer. However, about half of my team has an issue where the team explorer shows just one project. Most of the team doesn't even have permissions to view this project yet it is all they see.
I had each of them run the tf workspaces ... command to sync up their workspaces to the new server location. I verified permissions. I had one of the affected delete his workspace and create a new one. Same issue. Team explorer only shows one project... that he doesn't even have permission to view. Source control explorer seems to operate fine.
Also, this only seems to affect one project collection. I have not heard anyone on another project collection having this issue.
Suggestions?
Hmm, I'm wondering if you need to do a ChangeServerID.
Our Sharepoint 2013 Application failed to install and is stuck in a odd state. I followed the recommended approach for deleting the application using powershell commands on the hosted Sharepoint server, but it doesn't execute properly.
Visual Studio Deployment/Retract Reports:
Skipping the uninstall step because the app for SharePoint is in an invalid state and cannot be uninstalled.
PowerShell Commands
$instances = Get-SPAppInstance -Web http://mysite/sites/collection
$instance = $instances | where {$_.Title -eq 'Application.Title'}
Uninstall-SPAppInstance -Identity $instance
Executing this PS command throws...
The System Account cannot perform this action.
There is no option from the Sharepoint UI to remove the application, and retrying the install also fails. I've tried other user accounts to execute this powershell command (other than the system account), but no dice. I will have to delete the developer site collection if there is no other solution.
I'm faced this problem before on my Office 365 SharePoint Online when deploy SharePoint Hosted App. Then I submit Microsoft Service request and work with MS Technical Support Team on this issue. This problem seem to be something error in SharePoint backend database by itself (I'm not sure to consider it is SharePoint defect).
Did you check the app details installation error report? If you get the message:
"The content database on the server is temporarily unavailable."
Need help: Error 'Install App for SharePoint': An instance of this App already exists at the specified location., I'm quite not understand the answer but there is one comment from Jeremy Thake which seem to be deleted on this thread, he said that:
"…so I actually just restarted the whole environment and when Windows
came back up and I went to the SharePoint Site…the App was gone ;-)"
So here is my advice before you commit to delete your site collection:
Try to deploy your to the another developer site collection and check whether this problem still occur as the same.
Try to increase your app version or change app name/title/id and deploy to the same site collection and check whether this problem still occur as the same to your new app instance.
For SharePoint Server, try to restart IIS/Window Server if you're able to do that. Also install any latest SharePoint Update/CU.
For Office365 - SharePoint and have you have license account, you should submit the service request, if not you should wait about several day and try to remove this app instance again through UI.
Hope you can remove your app and know the root cause exactly.
I have faced this issue some times in on-premises SharePoint.
But for solving this I gave another account (or you can use 1 that you have) shell admin rights.
Note this account CAN'T be marked as a System account on SharePoint!!
Then with this different shell admin account you execute the same script. That always worked for me (I also got some strange installation behavior and needed do remove the app).
Yesterday, I was having trouble trying to publish a Visual Studio web app to the wwwroot folder. I could publish it to other folders. The suggested solution to fix the issue was to give the logged on user full rights to the folder. That worked, but I was puzzled because the active user, BESI-CHAD/CHAD, was an Admin user (see image at the bottom of the linked page.)
Now, I am trying to uninstall and re-install TFS and I get the following error suggesting that the user Chad is not in the ServerAdmin role-but I am in that role!
What is going on here?
Error [ Configuration Database ] TF255286: An error occurred while verifying you have the SQL server permission or role membership: serveradmin. You may not even have enough permissions to check. Consider adding your account to the sysadmin server role. The server hosting the databases is BESI-CHAD. The error was: TF30040: The database is not correctly configured. Contact your Team Foundation Server administrator.. See the log for more details.
I ended up using another SQL instance for my TFS db server, an express instance. That worked. I didnt really want another instance. Now, I want to know what happened. If there is a good theory, I might blow away Express and reinstall TFS again.
THis was a while back, but if memory serves, I was an Amdin on the SQL server but did not have rights to the db.