How can I remove an Application Pool in SharePoint 2013? - sharepoint-2013

I use SharePoint 2013 and I create Secure Store Service App and remove it.
When I want create this Service Application with the same Pool Name I get this error :
This Server Application Pool already exist....
How can I remove an Application Pool in SharePoint 2013?

I found this post that also works for Share point 2013.
according to that, we can do this :
Launch the SharePoint 2010 Management Shell with administrator privileges
(Start -> All Programs -> Microsoft SharePoint 2010 Products -> Right click on SharePoint 2010 Management Shell -> Run as administrator).
Run 'Get-SPServiceApplicationPool'.
Run 'Get-SPServiceApplicationPool -Identity <"Name of the application pool">
Run ‘Remove-SPServiceApplicationPool’.
Input the Identity <"Name of the application pool">.
Input 'Y' to delete the application pool.

Related

Why can't Team Explorer connect?

After having issues with VS2017 Enterprise memory leaks, but none with Team Explorer functionality, I've uninstalled and installed community edition.
tf settings connections shows I'm connected
tf vc checkin works just fine.
where tf shows it is running the 2017 TF.exe
removed my account from both the tfs section, and the vs sign-in in visual studio and added back.
going to the project in a browser at ____.visualstudio.com shows my login works just fine there too.
removed connection from team explorer manager and it no longer has any hosted repositories showing in the Connect to a Project dialog
devenv /resetuserdata as an administrator did not fix it
going in the visual studio baked-in web browser, it comes up as already logged in and shows the projects just fine.
I'm not behind a proxy
deleted project's .suo file
removed stored Microsoft account credentials from Windows 10 credential manager
tried opening vs stand-alone (not opening a project to open it) and connecting
What causes VS2017 to refuse to show VSTS projects?
I experienced the same behavior today with version 15.9.5.
I also tried other options like deleting the VS related folders in %LocalAppData%, etc. to no avail.
The solution is to remove your account from within Visual Studio by selecting 'Account Settings' from the drop-down after clicking your name in the upper-right. Now remove the VSTS account, restart Visual Studio, enter your VSTS credentials anew and voila.

SharePoint 2013 Autohosted App Feature Activation Issue

We have created SharePoint 2013 Auto hosted app. In that, we have created near about 50 lists from the solution in visual studio. but when i deploy it, it gives following error:
"there was a problem with activating the app web definition."
What is the reason? any limit for creating lists in Auto hosted app?
Please suggest me...

How can I make Visual Studio automatically attach its debugger to both a web application and web service?

I'm working on a Visual Studio project. I'm using Visual Studio 2010. The project has an ASP.NET application project and a separate ASMX web service project. The web application project is set as the start-up project.
When I tell Visual Studio to start debugging, it correctly starts both the web application and web service. However, it only attaches the debugger to the web application and not the web service. This problem seems to occur regardless of which web server I use for either project (IIS, IIS Express, Visual Studio Development Web Server).
In order to debug both simultaneously, I need to manually attach the debugger to the web service during the debugging session.
How can I make Visual Studio automatically attach to both projects when I tell it start debugging?
I found that this works if I set both the web service and application to start-up projects. Do this by right-clicking the solution file and choosing something like Set Start-up Projects....
One of the options is to open two instances of Visual Studio and debug the projects separately, however it is pretty much the same inconvenience as attaching the debugger manualy.
By the way, do you have ASP.NET debugger allowed in both projects (project properties > web tab > debuggers section)?

ASP.NET Web Service returning Bad Request in Windows Azure

After a Windows 7 fresh restart, I open the Visual Studio 2010 as administrator, create a new project of Windows Azure Project with ASP.NET Web Role, then at the WebRole1 project I add a WebService1.asmx and press F5 (run).
The Windows Azure services starts OK and the browser open the http:/127.0.0.1:8080/WebService1.asmx perfectly. But when I click at Invoke button to test the webservice method I always receive a Bad Request - Invalid Hostname, with a http:/127.0.0.1:8081/WebService1.asmx/HelloWorld.
The most likely cause is ASMX's WSDL file doesn't stand by load balanced environment such as Windows Azure. The test feature relies on WSDL. You will see similar issues if you add a web/service reference. It is recommended to upgrade to WCF. In WCF, you can use useRequestHeadersForMetadataAddress (http://msdn.microsoft.com/en-us/library/ee816894.aspx) to fix the issue. If you need to use ASMX, please try to manually provide a correct WSDL file.

Sharepoint server 2010 Central Administrationa and other settings

I want to read following setting configured on Sharepoint server 2010:
file types blocked" for web
application
Anti-virus setting
configured to scan documents on
upload
Is error report collection
enabled (Central Administration >
Operations > Logging and Reporting >
Error Reports > ) etc.
My question is, where are these setting stored on sharepoint server machine? Are they in any config file or in database?
I know programmatic way to read these settings (Got Sharepoint 2010 SDK sample code in C#), but my application is in C++ (VS 2003 .Net) and all the API/interfaces are available in .Net (managed code). Please let me know if the API/interfaces to access these setting are available in unmanaged code also?
Any help is greatly appreciated.
Regards,
Krishnakant
You cannot directly call sharepoint API in unmanaged code.
The settings are stored in sharepoint configuration database and must be called as you say in the SDK. You will need to create a .NET class library assembly which you will need to call from your managed code as a COM DLL.