Tag Info

Hot answers tagged

6

Problem solved and it was a very strange one (or maybe not). There is custom IHttpModule deployed that handles auditing view on list items. Client wanted to log everything so custom module was developed and deployed. Something like this: Sharepoint (WSS/MOSS) Auditing VIEW On List Items But if you read my question again you will see that there was problem ...


5

I found interesting article about this issue here http://geekswithblogs.net/kjones/archive/2010/10/29/142510.aspx Author created a small graphic files, copied them to C:\Program Files\Common Files\Microsoft Shared\web server extensions\1x\TEMPLATE\IMAGES and insert them to page footer. Because every WFE look to their own images directory, he can simply ...


4

You should be able to see a ULS log entry on the WFE that is serving the request. It will only appear on one of the WFE's. It might also reveal other information about what's going on with the web part. The defauly location of the ULS logs is here: C:\Program Files\Common Files\Microsoft Shared\Web server extensions\12\LOGS Check out the ULS Log Viewer ...


3

Looking at your reputation I guess you probably know more then me but have you considered or looked at SharePoint Warm Up Timer Job SharePoint Warm Up Timer Job Tutorial It could be something to do with Application Pools as well, as I once heard our SharePoint infrastructure manager was talking about it. and If there was any problem with code, it must had ...


3

Enable SessionStateService... http://technet.microsoft.com/en-us/library/ff607989.aspx


2

I've got a neat little web part that you can throw on your server. It'll show you the current server name, perfect for this issue. See http://sp2010adminpack.codeplex.com/


2

The features you are missing are out of the box SharePoint (Enterprise) features. They should be there. It sounds like there is a difference between the binaries or something you installed on server2. And you say you are trying to join a new machine to the farm and upgrading? Could you explain the steps you took in detail?


1

You have an error in your script. It should be: // in your code it was /viewfields. it must be ViewFields CAMLViewFields: "<ViewFields><FieldRef Name='Body'/></ViewFields>", // the filter must be SPFilterNode("z:row") //without the []


1

This link shows you how to move from different modes. Guess you would see on step 6 what mode you are using now: Click Database Setup to open the Database Setup page. The page contains information about the database currently in use.[]


1

SharePoint-Reporting component must be installed from SQL 2012 SP1 on SharePoint 2013 Have you not you installed SQL2012 (and not SP1)? See Supported Combinations http://msdn.microsoft.com/en-us/library/gg492257.aspx


1

There is a registry value that doesn't exist by default, that can be added to change the timeout of the server, I think on development machines the default SP settings dont allow for deployment of large .WSP solutions, or could also be slower platforms. Goto the following regustry key: HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\SharePointTools ...


1

it could be related to ChannelOperationTimeout http://msdn.microsoft.com/en-us/library/ee471440(v=vs.100).aspx Also, don't forget to restart Visual Studio


1

It looks like you are having a javascript related issue. Are there any custom scripts referenced from those pages? If part of the custom script is broken it can interfere with the standard scripts and methods. If the publishing features are activated on this site be sure that any javascript files stored in the site assets or related libraries are all ...


1

I had the same problem and found this very simple solution which worked for me. http://social.technet.microsoft.com/Forums/sharepoint/en-US/4cadb1a7-d933-4b35-b115-2b5e2bb1d504/cannot-complete-this-action-the-url-pageshomeaspx-is-invalid-it-may-refer-to-a-nonexistent?forum=sharepointgeneralprevious The above link offers more detail, but simply put, this is ...


1

Doesn't the user code proxy spawn a process for each web application?


1

Go to Run-> Services.msc -> Please check if the "SharePoint 2010 User Code Host" service is running. If running then please reset it and try to create a simple Event receiver/Web part to confirm whether Sandbox Hosting service is up and functional. Or in other words develop a "Hello World" web part and deploying it as a Sandboxed Solution. As soon as I try ...


1

Access Denied and similar exceptions are almost always logged in the trace/ULS logs, and easy to discover.


1

While not a definitive answer, some of the questions I ask myself when trying to diagnose issues like that are: What is the user trying to do when they receive the error? (ie access content, modify content etc)? Is the problem isolated to a specific user, or to a group of users? Is the problem isolated to a single site collection? Are there any third party ...


1

You could try telling SharePoint to keep the temporary files. This can be done using stsadm: STSADM -o editcontentdeploymentpath -pathname -keeptemporaryfiles Never|Always|Failure You can then look inside the various cab files and figure out what is going on (I didn't say it would be easy). This blog article has some suggestions. Stefan Gossner has a ...


1

If it's displaying error messages you should have a correlation ID, likely that correlation ID will only match in one WFE's log (unless both are somehow working in tandem to produce the problem, be mindful of this depending on your web part), you'll just have to figure out which one. Other than that, you could try setting up alternate URL's that don't go ...


1

You can use an old friend here, Sysinternals Process Monitor. Run it on your system. You can filter it to lock only on your specific process. If you run PSConfig from the cmd window, just use the target looking icon, drag it to the shell window and it will isolate on processes executed from that process. It will then report on all file, registry, and ...


1

Yes, to a certain extend you can watch CAML being executed by SharePoint Server. Here are the high level steps: Go to Central Admin -> Monitoring --> Configure Diagnostic Logging -> Expand "SharePoint Foundation" and Check Monitoring Make sure you select "Verbose" for event log and trace log and then save your settings You may want to do IIS reset at ...


1

Have a look at IDERA's tool. http://www.idera.com/Products/SharePoint/SharePoint-page-profiler/



Only top voted, non community-wiki answers of a minimum length are eligible