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?;)
Related
As described in the title, the app simply stops working after some time.
The application itself is a simple, one page form that pulls data from a webapi on another webserver by use of the Sharepoint WebProxy and displays that data using knockout.js. The environment and the Sharepoint Server (On-Premise, same domain as my Dev Machine) are configured correctly - supposedly - as described in
Configure an environment for apps for SharePoint (SharePoint 2013)
I can develop, debug in VS, deploy and open the App directly on the Sharepoint Site.
But after a while, when opening the app again without having changed or redeployed anything it stops at this point in the redirect process:
https://sharepointurl/_layouts/15/appredirect.aspx?instance_id=<some-guid>
and shows the "This page cannot be displayed" message. The Sharepoint Site still works.
There are no errors in the eventlog. Most of the time I can fix this by restarting the IIS service completely on which the Sharepoint Site resides. But sometimes even that doesnt work.
What could be the problem? Any Idea?
Update: The error is not consistent in that it may occur for user A but not for user B and even that can exchange after some time, so that the user B sees the error and user A can use the App.
Update: The error only occurs in IE 11 and doesn't happen when using Google Chrome.
Update: It seems as if Sharepoint 2013 Apps do not work with Internet Explorer 11, which I was using. As we had other issues with IE 11 and Reporting I downgraded my development machine to IE 10 and now it works.
Update: This had nothing to do with IE 11 either. The error eventually returned.
My first recommendation would be to have your client use the 32-bit version of Internet Explorer, even on a Windows 7 64-bit Operating System. Internet Explorer is the ideal browser for Active X and the preferred browser for SharePoint Online for Office 365.
Next I would recommend that your client configure Internet Explorer for SharePoint Online, to review the article detailing this process click here.
My last recommendation would be to have them install the latest updates and configure their computers for use with Office 365. The following links and instructions will detail that process.
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'm looking for a way to duplicate the content of a SharePoint 2010 server in order to work against it without taxing the main (production) server. I would need the backup server to update as needed, but I'm not looking for a failover solution. It looks like 2010 includes replication features for failover, but I can't tell if this is appropriate for my solution as well (simply not configuring the switchover feature). Can someone with SP 2010 experience tell me if this feature would work for my needs?
You could attach a restored backup of your production content database. See this MSDN documentation for more info: Attach or detach content databases (Sharepoint Server 2010).
There is also a GUI tool http://sushi.codeplex.com/ which should help you. You could backup production and restore to dev site whenever you needed to.
You could also use either stsadm.exe and the backup/restore option OR the powershell cmd backup/restore.
In addition, there is a built in interface in Central Admin to backup/restore sites. I've generally found either the command line or the SUSHI tool to be quicker and easier.
In most cases, the taxing work is on the sharepoint side, not the SQL side. You could attach another front end to the farm but reserve it for only your traffic. Otherwise you're looking at some form of backup/restore to copy everything to a 2nd duplicate farm.
I have installed MOSS 2007 on Windows Server 2008.
I am facing a strange problem:
I am unable to logon to SharePoint using IE 8, but am able to using Firefox. Pl note that I have taken care of the security in IE.
After creating a web application, when I try to chage the web application for creating a Site collection..I am unable to change it (even if I select the web application it says "No Selection".
I am unable to add web parts to any of the sites created! ( Pl note that I have created the sites by using a workaround..changing the SiteId=null to site Id = Id of the Site using SharePoint Manager)
I find no entries in the logs or no error messages..
Please help me in this regard.
Grace
IE8 on Windows Server 2008 is much more stringent with its default security settings. Even disabling IE Enhanced Security Configuration does not allow all functionality. This is to discourage you from logging into the server and perhaps inadvertantly installing an IE addon that compromises security.
You really should connect to SharePoint Central Administration from your local machine. Then you won't have the security problems and also will be following Microsoft best practice.
Try adding the Site (Central Admin ) to the Trusted Site in IE and Make the Security Setting as Low. It will give all the Required stuffs like Javascript and it should solve your issue.
I have also had the same problem, not being able to select a web application. In our case we ended up reinstalling sharepoint (actually a clean install of the OS), then it worked fine.
There was probably some step in the installation that we did not do in the correct order.
Installing Sharepoint on Windows Server 2008 is not a regular install. Make sure you have the latest Cumulative update installed + SP2. Better yet, slipstream the installation.
Take note, especially when installing Language Packs attention is need when performing the install, there is a specific order in which to install the product / updates / packs.
More info Code eater blog post
You may need to disable the loop back checking if the site is using a host header name. See this article for more details.
I have a series of reports served by SSRS. They are great and the users like them.
That being the case, upper management wants to throw a wrench in the works and serve the reports from the Sharepoint server.
Is there a realtively painless way to let users access the reports from sharepoint? How would somebody go about doing such a thing? Or do I just need to bite the bullet and try to stop the madness?
I'm not sure which version of SSRS or Sharepoint you're using, but there have traditionally been both a Report Viewer and a Report Explorer web part shipped with Sharepoint in the RSWebParts.CAB file (at least since SQL Server 2005 SP2 I think). You can start there, but if you wanted quick and low-tech you could put in an IFRAME web part and point it to the Reports folder on your SSRS Server. Since you're using Sharepoint, that's also making the assumption that you're using Windows Authentication, so that wouldn't be an issue there.
Here's a link that might be of some use:
Viewing Reports with SharePoint 2.0 Web Parts
The most painless is going to be to run SSRS in Native mode, which it sounds like you're doing already, then install the SSRS web parts on your WSS/MOSS server.
You will have to manage security and report source control using some other methods besides sharepoint, however you don't have to deal with installing WSS/MOSS on your SSRS box and adding it to your SharePoint farm.
The more painful option is to run SSRS in Integrated mode. This allows you to use all the SharePoint document management stuff for your reports and share the same security setup however, the server configuration can be lengthy and difficult to setup.
http://msdn.microsoft.com/en-us/library/bb677365.aspx
Hope this helps!
Ben