This project is read-only.

Activation Errors Out

Jul 6, 2009 at 5:39 PM
Edited Jul 6, 2009 at 5:45 PM

I've successfully installed and configured SLAM however it errors out when I start the Activation. I did this on three separate MOSS 2007 Server Farms and received the same error upon activation. One server farm is comprised of a SQL Server 2005 server, a Web Front End server and an App server. The other two server farms consisted of a SQL Server 2005 backend and one frontend web/app server.

SLAM Control Panel Diagnostics Results:

7/6/2009 12:30:09 PM Information Create table for SitesList
7/6/2009 12:30:08 PM Information Processing Sites List
7/6/2009 12:30:08 PM Information Attached Event Handlers for List: Projects List
7/6/2009 12:30:08 PM Information Attached Event Handlers for List: Sites List
7/6/2009 12:30:08 PM Information Activation Initiated
7/6/2009 12:30:08 PM Information Deactivation Complete
7/6/2009 12:30:08 PM Information Detached Event Handlers for List: - 43a8e2ce-e9a8-40e0-9ba6-a23cbc37cd1e - Sites List
7/6/2009 12:30:08 PM Information Detached Event Handlers for List: - 07511960-69e1-41ad-bd74-dd2c4e84e03f - Projects List
7/6/2009 12:29:43 PM Information Deactivation Initiated

Web Server:Event Viewer:Application Error Messages:

Error Event ID:6875 Windows SharePoint Services 3 error loading and running event receiver Microsoft.SharePoint.Workflow.SPWorkflow AutoStartEventReceiver in Microsoft.SharePoint Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c File Name:Microsoft.SharePoint.Msg.dll, File Version: 12.0.4518.1016, Product Name: Windows SharePoint Services, Product Version: 12.0.4518.0, Source: Windows SharePoint Services 3

...\12\LOGS Portion of Messages:

07/06/2009 12:29:32.70  w3wp.exe (0x0EF4)                        0x0948 Search Server Common           MS Search Query                90gl Medium   SQL: dbo.proc_MSS_ScopeCacheGetChangedConsumers 205 
07/06/2009 12:29:43.57  w3wp.exe (0x0EF4)                        0x0948 Windows SharePoint Services    General                        8e25 Medium   Failed to look up string with key "Sale_CTName", keyfile . 
07/06/2009 12:29:43.57  w3wp.exe (0x0EF4)                        0x0948 Windows SharePoint Services    General                        8l3c Medium   Localized resource for token 'Sale_CTName' could not be found for file with path: "(unavailable)". 
07/06/2009 12:29:43.57  w3wp.exe (0x0EF4)                        0x0948 Windows SharePoint Services    General                        8e25 Medium   Failed to look up string with key "Sale_CTDesc", keyfile . 
07/06/2009 12:29:43.57  w3wp.exe (0x0EF4)                        0x0948 Windows SharePoint Services    General                        8l3c Medium   Localized resource for token 'Sale_CTDesc' could not be found for file with path: "(unavailable)". 
07/06/2009 12:29:43.58  w3wp.exe (0x0EF4)                        0x0948 Windows SharePoint Services    General                        72kg High     #20001: Cannot open file "Resources.en-US.resx" for reading. 
07/06/2009 12:29:43.58  w3wp.exe (0x0EF4)                        0x0948 Windows SharePoint Services    General                        72kg High     (#3: Cannot open file "Resources.en-US.resx" for reading.) 
07/06/2009 12:29:43.58  w3wp.exe (0x0EF4)                        0x0948 Windows SharePoint Services    General                        8e26 Medium   Failed to open the language resource for Fea{75a0fea7-cd50-401e-af0e-782f3662a299} keyfile Resources. 
07/06/2009 12:29:43.58  w3wp.exe (0x0EF4)                        0x0948 Windows SharePoint Services    General                        72kg High     #20001: Cannot open file "Resources.resx" for reading. 

 

Developer
Jul 6, 2009 at 5:58 PM

I suspect the errors you have posted here are misleading.  First, SLAM does not use a Resources.resx file, nor language specific resources, anywhere.  Also the activation process goes into 12:30 and your log goes up until the time it looks your activation is starting, not during it.  I am assuming Create table for SitesList is the final line on diagnostics page, therefore in the SLAMMessageLog table.  Do you have a SiteList table in your slam database?  Are there are any events in Windows Event Log, under Application, where a source name of SLAM?  Had  you registered the Event source (used the reg file included in the Setup)?  If it is stopping I would also assume you are hitting an error and at the very least any error would bubble up, if nowhere else to the event log.

Jul 6, 2009 at 6:32 PM

I tried to correlate the timestamp on the error log to the time I clicked the Activate button, which was just before the first SLAM diagnostic message. The messages run from then throughout the activation process, there were just too many to show here.  These were the most common messages.  The Create table for the SitesList is the final line, it stops there every time. No tables are created in the SLAM database, therefore there is no SiteList table in the SLAM database.  I assumed the Activate process would create the event handlers and tables based on the configuration file - am I supposed to create the empty tables for the SLAM to populate?  There is only the one Windows Event Log entry under Application, the one I summarized, and it is shows up 21 times when I kick-off the Activate process. No events were logged for SLAM. I did register the Event source prior to installing SLAM.

I just realized the one common denominator between the three server farms I tried this on was that the Site Collections were all based on the Fab40 BudgetingTrackingMultipleProjects.wsp site definition.  Could this pose a problem?

Developer
Jul 6, 2009 at 7:06 PM

Got it.  No you do not need to do anything other than provide SLAM with the database.  When you do validation, everything is matched?  If so, can I see your slam config?

Jul 6, 2009 at 7:41 PM

Yes, everything was matched. Following is the config used:

<?xml version="1.0" encoding="utf-8" ?>
<Configuration>
  <ConnectionStrings Default="SLAM">
    <add Name="SLAM" ConnectionString="Database=SLAM_ITEMS;Data Source=SPS-SQL;User Id=slam_admin;Password=XXX" />
  </ConnectionStrings>

  <DataMapping DataSchema="SLAM">
    <List Name="Sites List" ActivationOrder="1">
      <Fields>
        <Field Name="Title" SqlType="varchar(255)" SPType="Text" Required="true"></Field>
        <Field Name="Location" sqlType="varchar(255)" SPType="Text" Required="false"></Field>
      </Fields>
    </List>
    <List Name="Projects List" ActivationOrder="2">
      <Fields>
        <Field Name="Title" SqlType="varchar(255)" SPType="Text" Required="true"></Field>
        <Field Name="SiteCode" SPType="Lookup" AssociatedList="Sites List" AssociationName="ProjectToSite"></Field>
      </Fields>
    </List>
  </DataMapping>
</Configuration>

Jul 7, 2009 at 6:57 PM

I did a fresh install of MOSS 2007, created a blank site collection, and added two basic lists {Projects and Sites}. The Projects list has a lookup to the Sites Title column renamed SiteCodes.

I monitored the application event log on the Web server at each point during the installation and services configurations. The only notable message were the following two Warnings:

- Windows SharePoint Services 3 Search: Could not import the registry hive into the registry because it does not exist in the configuratiojn database

- Office Server Search: Could not import the registry hive into the registry because it does not exist in the configuratiojn database

Both services started up successfully according to the SharePoint 3.0 Central Administration Site. Could this have anything to do with the SLAM Activation error?

When I tried to Activate SLAM this time, I didn't receive any Application Event Log errors however it errored out again and the diagnostic and log events are below. While the SLAM Control Panel Configuration sates both tables and all columns are matched it seems that it might be an issue with not being able to select/read the data.

7/7/2009 1:30:02 PM Information Create table for Sites
7/7/2009 1:30:02 PM Information Processing Sites
7/7/2009 1:30:02 PM Information Attached Event Handlers for List: Projects
7/7/2009 1:30:02 PM Information Attached Event Handlers for List: Sites
7/7/2009 1:30:01 PM Information Activation Initiated

07/07/2009 13:30:02.29  w3wp.exe (0x0AF4)                        0x0ADC Windows SharePoint Services    General                        8dzz High     Exception Type: System.Data.SqlClient.SqlException  Exception Message: An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Add a name or single space as the alias name.   
07/07/2009 13:30:04.97  w3wp.exe (0x0AF4)                        0x0ADC SharePoint Portal Server       Runtime                        8gp7 Medium   Topology cache updated. (AppDomain: /LM/W3SVC/2064898069/Root-1-128914611569370912) 
07/07/2009 13:30:07.95  OWSTIMER.EXE (0x0640)                    0x0AEC SharePoint Portal Server       Business Data                  7pkf Monitorable Portal Analytics processing job started. 
07/07/2009 13:30:07.97  OWSTIMER.EXE (0x0640)                    0x0AEC SharePoint Portal Server       Business Data                  63tr Monitorable Usage data processing on SSP SharedServices1_moss was skipped because it is not enabled. 
07/07/2009 13:30:08.05  OWSTIMER.EXE (0x0640)                    0x0AEC Search Server Common           MS Search Administration       7plh Monitorable Starting query log processing on SSP SharedServices1_moss. 
07/07/2009 13:30:08.06  OWSTIMER.EXE (0x0640)                    0x0AEC Search Server Common           MS Search Administration       7pli Monitorable Query log processing on SSP SharedServices1_moss complete. 
07/07/2009 13:30:08.06  OWSTIMER.EXE (0x0640)                    0x0AEC SharePoint Portal Server       Business Data                  7pkg Monitorable Portal Analytics processing job finished. 
07/07/2009 13:30:08.16  w3wp.exe (0x0AF4)                        0x0ADC Search Server Common           MS Search Query                90gl Medium   SQL: dbo.proc_MSS_ScopeCacheGetChangedConsumers 9 
07/07/2009 13:30:20.06  OWSTIMER.EXE (0x0640)                    0x0AEC Windows SharePoint Services    Topology                       0 Medium   Adding SPS\ssp_admin to local group 2. 
07/07/2009 13:30:20.06  OWSTIMER.EXE (0x0640)                    0x0AEC Windows SharePoint Services    Topology                       0 Medium   Adding SPS\ssp_admin to local group 0. 
07/07/2009 13:30:20.17  OWSTIMER.EXE (0x0640)                    0x0AEC Windows SharePoint Services    Topology                       0 Medium   Adding SPS\ssp_admin to local group 2. 
07/07/2009 13:30:20.18  OWSTIMER.EXE (0x0640)                    0x0AEC Windows SharePoint Services    Topology                       0 Medium   Adding SPS\ssp_admin to local group 0. 
07/07/2009 13:30:20.32  OWSTIMER.EXE (0x0640)                    0x0AEC Office Server                  Setup and Upgrade              8u3j High     Registry key value {SearchThrottled} was not found under registry hive {Software\Microsoft\Office Server\12.0}. Assuming search sku is not throttled. 
07/07/2009 13:30:20.35  OWSTIMER.EXE (0x0640)                    0x0AEC Search Server Common           MS Search Administration       90gf Medium   SQL: dbo.proc_MSS_PropagationGetQueryServers 
07/07/2009 13:30:20.37  OWSTIMER.EXE (0x0640)                    0x0AEC Search Server Common           MS Search Administration       8wni High     Resuming default catalog with reason 'GPR_PROPAGATION' for application 'SharedServices1_moss'... 
07/07/2009 13:30:20.39  OWSTIMER.EXE (0x0640)                    0x0AEC Search Server Common           MS Search Administration       8wnj High     Resuming anchor text catalog with reason GPR_PROPAGATION' for application 'SharedServices1_moss'... 
07/07/2009 13:30:20.43  OWSTIMER.EXE (0x0640)                    0x0AEC Search Server Common           MS Search Administration       8dvl Medium   Search application 'f379e9e4-8798-426f-9ab0-ca505369a507': Provision start addresses in default content source. 
07/07/2009 13:30:20.45  OWSTIMER.EXE (0x0640)                    0x0AEC Search Server Common           MS Search Administration       7hmh High     exception in SearchUpgradeProvisioner Keyword Config System.InvalidOperationException: jobServerSearchServiceInstance is null     at Microsoft.Office.Server.Search.Administration.SearchUpgradeProvisioner..ctor(SearchServiceInstance searchServiceInstance)     at Microsoft.Office.Server.Search.Administration.OSSPrimaryGathererProject.ProvisionContentSources() 
07/07/2009 13:30:20.47  OWSTIMER.EXE (0x0640)                    0x0AEC Windows SharePoint Services    Topology                       0 Medium   Adding SPS\ssp_admin to local group 2. 
07/07/2009 13:30:20.47  OWSTIMER.EXE (0x0640)                    0x0AEC Windows SharePoint Services    Topology                       0 Medium   Adding SPS\ssp_admin to local group 0. 
07/07/2009 13:30:34.15  OWSTIMER.EXE (0x0640)                    0x0D40 Excel Services                 Excel Services Administration  8tqi Medium   ExcelServerSharedWebApplication.Synchronize: Starting synchronize for instance of Excel Services in SSP 'SharedServices1_moss'. 
07/07/2009 13:30:34.15  OWSTIMER.EXE (0x0640)                    0x0D40 Excel Services                 Excel Services Administration  8tqj Medium   ExcelServerSharedWebApplication.Synchronize: Successfully synchronized instance of Excel Services in SSP 'SharedServices1_moss'. 
07/07/2009 13:30:43.98  OWSTIMER.EXE (0x0640)                    0x0AEC SharePoint Portal Server       SSO                            8inc Medium   In SSOService::Synch(), sso database conn string:  
07/07/2009 13:31:01.69  w3wp.exe (0x0AF4)                        0x02A0 Windows SharePoint Services    General                        0 Medium   Entering MRU trim routine. 
07/07/2009 13:31:01.69  w3wp.exe (0x0AF4)                        0x02A0 Windows SharePoint Services    General                        0 Medium   Initial table size: 8266585 in 106 entries 
07/07/2009 13:31:01.69  w3wp.exe (0x0AF4)                        0x02A0 Windows SharePoint Services    General                        0 Medium   Final table size: 8266585 in 106 entries 
07/07/2009 13:31:01.69  w3wp.exe (0x0AF4)                        0x02A0 Windows SharePoint Services    General                        0 Medium   Exiting MRU trim routine. 
07/07/2009 13:31:05.00  w3wp.exe (0x0AF4)                        0x0ADC SharePoint Portal Server       Runtime                        8gp7 Medium   Topology cache updated. (AppDomain: /LM/W3SVC/2064898069/Root-1-128914611569370912)