Christopher W. Szabo

less info
130 reputation
7
bio website
location Phoenix, AZ
age 37
visits member for 2 years, 3 months
seen Jul 10 '12 at 17:19

Jun
13
awarded  Popular Question
Apr
4
awarded  Self-Learner
Oct
23
awarded  Revival
Jul
9
answered Can't pass authentication to browse a sharepoint site
Jul
7
awarded  Scholar
Jul
7
accepted A bug, saboteur, or am I going crazy… SharePoint 2010 Farm That Keeps “breaking”
Jul
7
answered A bug, saboteur, or am I going crazy… SharePoint 2010 Farm That Keeps “breaking”
May
7
comment A bug, saboteur, or am I going crazy… SharePoint 2010 Farm That Keeps “breaking”
I'm also able to recreate the problem in several other lists. For example, if I navigate to site permissions and try to edit any of the users or groups I receive the same error. I just discovered that last night.
May
7
comment A bug, saboteur, or am I going crazy… SharePoint 2010 Farm That Keeps “breaking”
No actually, this is the first time I've seen that, but the behavior with the error when I try to edit the list item is the same. A was reading something last night about cache account (super user) and anonymous list access. Any ideas there?
May
7
comment A bug, saboteur, or am I going crazy… SharePoint 2010 Farm That Keeps “breaking”
There are no group policies in place that are impacting the servers, I've run group policy modeling on each of them. You're though is a good one though; the policy might be applied after the farm is stood up which would explain why everything works at first and then breaks. Unfortunately, that's not the cause in this particular case. I've also validated the SQL Express is not the cause of the problem by moving the state and session state service application databases to the main database server.
May
7
comment A bug, saboteur, or am I going crazy… SharePoint 2010 Farm That Keeps “breaking”
The primary database server has 12GB of RAM allocated, SQL Server can use up to 8GB, leaving 8GB for the operating system. Each of the other servers in the farm have a total of 4GB of memory allocated. I know that the servers are not out of memory because I've used data collectors to trace resource usage.
May
7
comment What are the dangers of using a static class that contains your SPWeb object?
The HttpContext has absolutely nothing to do with a transaction. It encapsulates all of the information that is specific to a request. If 100 people are being served content from the same web application or website the context for each of those requests will be the same. There might be different content served for each of those requests, but the context in which that content is served is the same. That's why it's a static (shared) property.
May
6
answered Search site getting 404 error
May
6
answered What are the dangers of using a static class that contains your SPWeb object?
May
6
answered Cannot access sql database
May
6
asked A bug, saboteur, or am I going crazy… SharePoint 2010 Farm That Keeps “breaking”
Jan
6
comment Staff directory webpart broken after a manual synchronization
You probably don't want to run the DTS under the SharePoint account, and you shouldn't have to. As long on the DTC on that server and on the server that the request is originating from are both setup for local and remote launch requests NetworkService will be just fine. Did you add the SharePoint domain group that stores the application pool accounts to each server in your farm?
Jan
3
answered Staff directory webpart broken after a manual synchronization
Jan
3
revised Managed Metadata Service Application and Crazy Behavior
I made additional progress with the farm implementation and found a potential cause for the problem. I've updated the thread with the information to provide additional insight.
Jan
2
comment Managed Metadata Service Application and Crazy Behavior
Yes, the service is started on the appropriate host. There is a specific Web application for the syndication hub. I tried implementation using the specific Web application, and using the primary portal as the Web application with the same results. I did find the information pertaining to the use of Claims Authentication in the white paper that Microsoft published. There is a single paragraph that explains that in the 200+ pages of information. Thanks for providing some feedback.