Browse by Tags
Sorry, but there are no more tags available to filter with.
-
-
Body: “Failed to start service SearchServiceInstance on this server after completing upgrade. Please start it manually.” The service it is talking about is Office SharePoint Search. PSConfig stays on the “task 8” screen for a while, though it does later complete “successfully”. Here’s the other symptoms: When I am logged in as MOSSsa, my Farm Admin account which is a member of Administrators, and I try to start the service I get: Let’s help the search engines: The error shown is “Error 183: Cannot create a file when that file already exists.” When I logged in as Administrator (my box/domain admin – this machine is a Domain Controller), I got a different message once (approximately: service started then stopped, which sometimes is OK), but on a subsequent attempt, got the same message as above. Resolution/Workaround: Add MOSSSearchSvc to the Administrators group, start the service. The service starts successfully. Stop the service, remove it from the group, then restart the service. No complaints. Apparently, it just needed extra permissions long enough to remove the offending file. My guess is that the file was created by MOSSsa since I was logged in as MOSSsa when I ran the Infrastructure Update. --Michael Category: MOSS 2007 Published...
-
-
Body: So I decided that the best way for me to get some content into this new MOSS farm that I created was to attach a content database. I logged into my farm server (it’s a demo environment so it’s all on one box). I logged in as my Farm Admin account. I went into SQL Server Management Studio, right clicked the Databases folder, and then clicked Attach. Got this: That’s not what I was expecting. After asking one of our SQL gurus to take a look and having him tell me that he’d never seen this one before, I feared my install of SQL Server 2008 was broken and I’d have to reinstall…. But one last thing came to mind – I was logged in as my Farm Admin account, not the box admin/domain admin (machine is a Domain Controller so box admin is domain admin), so I only had Security Admin and DB Creator roles, not full control / system admin. Sure enough, when I logged into the machine as domain admin, the Attach dialog worked. Hopefully, the attach will achieve what I want as well… --Michael Category: MOSS 2007 Published: 4/20/2009 10:52 AM Attachments: http://blumenthalit.net/blog/Lists/Posts/Attachments/120/image_2_70AF5C03.png http://blumenthalit.net/blog/Lists/Posts/Attachments/120/image_thumb_70AF5C03.png Del.icio.us | Digg It | Technorati...
-
-
Body: Currently, I am setting up a single server MOSS virtual machine which will host a demo site that will be used by part of Magenic’s sales force. The demo site will represent a repeatable service offering. Additionally, another project team in my office is working on a MOSS and Commerce Server solution that will have multiple concurrent MOSS developers. We are planning to give each developer their own single server farm. I believe the best way to do this is through a scripted install. Because of these two projects, I have been building out a MOSS VM using command line scripts and answer files as much as I could. To this end, I have created an answer file for DCPROMO, a SQL Server 2008 answer file. a batch file that runs PSCONFIG, and batch files that run several STSADM commands. I also wrote a PowerShell script to create users, configure them, and put them in the right OrganizationalUnit. Plus I am documenting almost everything. I’ll do my best to share these later in the week. In the mean time, I wanted to cite a few resources: Alpesh Nakars on having good examples of these: http://www.alpesh.nakars.com/blog/stsadm-command-line Also http://www.powershellpro.com/powershell-tutorial-introduction/powershell-tutorial-active-directory...
-
-
Body: In Central Admin, in Operations, you have an option to quiesce the farm. This stops all new connections, and is a good idea before, for example, restoring a content database. it's the next to last operation under Global Configuration. When the farm is quiescent, you will get certain errors, such as the following. "The server is currently being taken down for maintenance" is InfoPath Forms Services' way of saying the farm is being quiesced, and we can't do any new connections - although the fact that the web pages leading up to this screen didn't object seems a little inconsistent. To fix this, go to the Quiesce Farm option in Central admin and click on Reset Farm. --Michael Category: MOSS 2007 Published: 2/20/2009 10:41 PM Attachments: http://blumenthalit.net/blog/Lists/Posts/Attachments/108/image_2.png http://blumenthalit.net/blog/Lists/Posts/Attachments/108/image_4.png http://blumenthalit.net/blog/Lists/Posts/Attachments/108/image_6.png http://blumenthalit.net/blog/Lists/Posts/Attachments/108/image_thumb.png http://blumenthalit.net/blog/Lists/Posts/Attachments/108/image_thumb_1.png http://blumenthalit.net/blog/Lists/Posts/Attachments/108/image_thumb_2.png Del.icio.us | Digg It | Technorati | Blinklist...
-
-
Body: I know I'm overdue to respond to some blog comments you all have been kind enough to leave, but in the mean time I want to share this item I came across. I had a requirement (one of several) from a business user that had a site hierarchy with a site (Projects) that had many subsites (Project 1, Project 2, Project 3...) and wanted a searchable list of these sites. In the process of figuring out the best way to meet this requirements, I discovered this: You know how you can specify properties in a keyword search? Property:PropertyValue. Well, there is a property called ContentClass that you can use to specify sites only. The property value is STS_Web. Without the ContentClass filter: With it: -- Category: MOSS 2007 Published: 10/16/2008 9:06 AM Attachments: http://blumenthalit.net/blog/Lists/Posts/Attachments/82/image_2.png http://blumenthalit.net/blog/Lists/Posts/Attachments/82/image_4.png http://blumenthalit.net/blog/Lists/Posts/Attachments/82/image_thumb.png http://blumenthalit.net/blog/Lists/Posts/Attachments/82/image_thumb_1.png Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks
-
-
Body: Tonight I was supposed to be involved in the deployment of a workflow Solution I had built, but when the deployment window opened, I went to my client's SharePoint intranet site and got three terrifying error messages: http://server.dom.tld/ returned a 404. http://server.dom.tld/managedPath/siteCollectionRootSite returned a 404. http://server.dom.tld/managedPath/siteCollectionRootSite/default.aspx returned a "An unexpected error has occurred. " I don't have access to Central Admin on this farm, but the Farm Admin who was going to deploy my Solution (WSP) quickly identified the problem - the database server that holds all SharePoint's databases was down. In as much as it's not a problem with my WSP, I am relieved. In as much as it keeps me from deploying my solution and getting to my weekend, I am frustrated. Such is life. -- Michael Category: MOSS 2007 Published: 9/26/2008 9:03 PM Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks
-
-
Body: We loaded a WSP into the solution store with STSADM, and then used STSADM to deploy the solution and execute admin service jobs. STSADM reported a success, but when we looked in Central Admin, we saw that the solution deployment was scheduled but never starting. When we canceled the deployment job, the status page for the solution package said that it had deployed to WFE (Web Front End) Server 2 (which hosts Central Admin too), but not server 1 which is just a WFE for the user-facing web apps. The net of it is that the OWS Timer on Server 1 was not running (even though it said it started, but when we right-clicked to restart, it gave us a start option instead of stop or restart). It was not running due to a bad config file that we had made for it because we needed to provide some application settings and some WCF settings for a workflow solution we built. Both OWSTimer as well as the web.config for the user-facing MOSS site needed the config settings for our workflow because our workflow has a delay task and the workflow is owned by the w3wp process (assuming it was started via MOSS ) until it hits a delay task. Once a workflow hits a delay task, it resumes under the context of OWSTimer. The error message that we get in the ULS...