I'm writing a service application for SharePoint 2010. I've implemented the Microsoft.SharePoint.Administration.IServiceAdministration in my service class. There's method called GetCreateApplicationOptions in this interface which returns the SPCreateApplicationOptions enumeration.
The enumeration has three distinct values, e.g. "None". The description of "None" reads: This service application is not created in single-click (eval) mode or shown/created in the farm configuration wizard.
I'm good with the farm creation wizard, but what is "single-click (eval) mode"? There seems to be no info around...
Yes, there is not a lot of help available. But based on description, it sounds like: Single-Click (eval) mode is applicable when you do NOT choose to install/configure SharePoint Farm yourself. For example, when you want to install everything on same machine on windows 7. And when you are not in single-click mode, SharePoint presents you a config wizard when you run the central admin first time, soon after installation.
Related
I know it's possible to create and register an executable or .dll as an additional Windows Control Panel via the registry but would like to integrate with the Windows 10 Settings application, for instance as an additional entry in the 'Network and Internet' Settings pane. I've found a reference to OEM Partner Settings but am neither an OEM, nor a Partner, and just want to add Control-Panel like functionality in an obvious place. I can't find any more developer documentation on SO or MSDN that relates to this so wonder if it's possible or whether MS have locked the Settings application a little tighter than the old (and maybe to be deprecated?) Control Panel? What's best practice for Windows 10 system-wide settings applications/applets/panels?
I'm trying to publish the search service application from my Sharepoint 2013 farm and have the Sharepoint 2010 farm consume it. Ive followed these steps from the Technet site and I am stuck at step 6:
http://technet.microsoft.com/en-us/library/ff621100.aspx
If you click the link in step 6 and scroll down, you see the first shell command:
Set-SPAuthenticationRealm -realm <RealmName>
This command apparently doesn't exist in SP 2010. The command doesn't exist. Is there a way around this or any other different steps that someone knows about to finish up this connection? I'm almost done I just need this last step (6).
Any help would be appreciated.
Never mind. Step 6 is not required. Just make sure to set the Connection to the new search service as the default instead of having the original service as the default.
To set it as default, navigate to Central Admin, Application Management, Configure service application associations and for the Web Applications View, select "default" (or your Application Proxy Group name) and then you should get an option to set the new search as the default. Be aware that any Scopes you have may not work if they weren't upgraded.
Does anyone here know what could cause a new feature to not show up in the SharePoint UI?
The solution it is part of has been correctly deployed to the GAC and shows up in the central administration list of deployed farm solutions, the feature appears in the FEATURES folder of the 14 hive, yet the feature itself does not appear in the features list for the site collection, either in the UI or in PowerShell using Get-SPFeature.
Yes, the feature is correctly scoped, and no, it is not hidden. :)
Any thoughts or pointers would be very welcome!
Answer supplied on sharepoint.stackexchange.com, with thanks to Simon Doy. https://sharepoint.stackexchange.com/questions/73871/sharepoint-2010-feature-not-appearing-in-ui
Somehow, something had gone wrong with the installation of the feature, and neither the UI nor commands like Get-SPFeature revealed its existence, although the Install-SPFeature -ScanForFeatures command emboldened below displayed the missing feature.
"Check that the feature has been installed. For example, if you are
performing Update-SPSolution and a new feature has been added between
solution deployments then the feature is not installed by default.
To check do the following:-
Run SharePoint 2010 Management Shell from one of the SharePoint
servers Type Install-SPFeature -ScanForFeatures This will show you any
features that are available in the SharePoint Root but have not been
installed. You can install any missing features using the command :-
Install-SPFeature -AllExistingFeatures
See the following TechNet
Article for more information.
http://technet.microsoft.com/en-us/library/ff607825(v=office.14).aspx"
Look in central admin to see what site collection the feature is deployed to. Make sure in that site collection the feature is turned on.
Also, check the deploy job status to see if it actually finished.
Is there a on install event receiver? If it errors out, the feature will not finish installing even after the DLL is copied.
I thought I'd give SharePoint development a go, to broaden my understanding of Microsoft technologies and ran into a situation I refuse to understand.
I have a new web application created: http://localhost:11523 and set up the site collection as required. I can browse to the web site fine, without any issues, but now I want to start developing against this, using the object model.
Right, so after I struggled with SPSite site = new SPSite("http://localhost:11523"); I figured that I'm not running VS2008 in elevated permissions, so restarting VS I finally got one step further.
Whenever I step into my code, I get:
The Web application at
http://localhost:11523/ could not be
found.
I've Googled this without luck. The application is most definitely there, I can browse it, add web parts and go mad. I just can't seem to connect to it via Visual Studio.
Any ideas would be great.
EDIT
I thought I'd isolate my method, called "GetListFromSharePoint(string name)" into a test method (nUnit Framework) and to my surprise returned 9 entries from the list, as expected. When I dumped the method back into my web application (not SharePoint, trying to test the Composite Control through a normal Web site), and run into the mentioned problem.
This is in SharePoint 2007, and I'm developing on the same machine onto which SharePoint 2007 is installed.
This approach used to work, for some reason, I just can't get it to recognize SharePoint. The test stubs work find, just not the web application.
Edit 2
So there where a couple of things I "missed", which kind of solved the problem by itself.
Firstly, I was developing on a x64 Windows 2008 box, thus SharePoint 2007 was running in x64 mode. Cassini, turns out, is 32bit regardless of the platform you run it on, which caused some compiler bugs (I did not have IA64 compilers installed). After installing this, I figured out that the default web site (localhost:80) had been disabled by SharePoint.
Renabling the default web site, allowed me to create my web application as a virtual directory against it, which allowed my debugger compiler to run in x64.
My next challenge was access permissions. Because any new virtual directory on port 80 is assigned to the default application pool, is it assumed that the user does not have the right permissions, so I had to change my web application to run under my SharePoint web application's application pool.
The last thing I had to do was run my SharePoint code with elevated permissions.
Working like a charm :D
Note! Enable debug on your SharePoint web application....
Thanks,
Eric
(You have not specified version - assuming SharePoint 2010).
You need to decide what object model you want to use:
client (to be able to access the server from any other machine)
server (the one that you are trying now, can only be run locally).
Most likley reasons your code not work:
using "localhost" instead of ""computer name" in the Url. (I believe it is the reason.)
you are running your code not on the same machine as the SharePoint
you are running code under non-admin account
Check out how sites collections are configured in "Central Administration" site - urls associated with each site collection are listed there - make sure you are using correct one.
You can also try enumerating all site collections in SPWebApplication (http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.administration.spwebapplication.sites.aspx) to start expiriments.
I dont think the SPSite connect through the IIS, and if SharePoint isn't set up to respond to localhost (done in the Central Administration) you wont be able to connect to that url. IIS works a bit different here since it relays the signals to "localhost" to the "web application instance".
Start by checking in your SharePoint Central Administration. Go to "Configure alternate access mappings" in the "System Settings" section. Here you have your SharePoint instances, there are three properties which you can see directly in the list; 'Internal URL', 'Zone' and 'Public URL for Zone'.
If the Internal URL isn't set to Localhost you wont be able to use that connection you suggested. It bay be improper to change this to another url as well, so simply try to set your SPSite site = new SPSite("http://yourinternalurl:11523"); to whatever's in that box! :)
Cheers
I setup a test box computer with server 2008 (standard edition, not R2 and not hyper-v editing). I then installed SharePoint 2010. I was amazed how easy the whole setup went (the prerequisites setup on the SharePoint disk made this process oh so easy – great install system). Really this was just so easy.
This test box is being used for testing Access web services. I am able to well publish access applications to this test server and Access applications publish and run just fine on the web SharePoint site through an web browser.
However, the only thing that does not work is when I launch a Access report. The error message I get back is
This report failed to load because session state is not turned on.
Here is a screen shot:
I can’t seem to find the setting anywhere to turn session state on. Any hints or links on how to enable session state in SharePoint 2010 would be most appreciated.
On Todds blog you can find a post which explains how to turn on session state in SharePoint 2010.
Here is the solution:
http://geekdeck.com/sharepoint-2010-this-report-failed-to-load-because-session-state-is-not-turned-on/
Probably not in SharePoint head over to the IIS configuration and see whether session state is enabled there. I am not aware of anything in the SharePoint forms (I did set up 2010 on the weekend) that indicates session state. And as session state on farms is an administrator action (state server etc.), maybe they simply did not activate it?;)