You are browsing the archive for 2011 June.

Avatar of kurtvh

by kurtvh

Very nice blog post about IT Business Service Form.

10:52 pm in Uncategorized by kurtvh

Hello,

Oskar Landman has written a nice blog about a scenario where an extension was needed on the Business Service class and the impact of this extension on the Service form.

The blog can be found on this URL: Creating the IT Business Form in Service Manager 2010 SP1 based on the IT Service Form 

Have fun,

Kurt Van Hoecke

Technorati Tags: ,
Avatar of kurtvh

by kurtvh

TIP – “SQL Server 2008 SP1 was not found" during installation of SCSM 2010 Data Warehouse Management Server

5:48 pm in Service Manager by kurtvh

Hello,

Lastly I had an issue on the installation of the SCSM data warehouse and had an annoying error. At the configuration page of the reporting server for data warehouse I received the error “SQL Server 2008 SP1 was not found”

image

The issue was that the reporting server database was installed on a SQL server instance that had an “_” included.

SQL  reporting services doesn’t like “_” in the server name and also in the configured SQL instance. Once the SQL reporting server configuration was adjusted to have the DB on another SQL server instance without the “_” I could proceed with the SCSM data warehouse installation without any issues.

Little tip when you use different SQL instances for you SCSM SQL environment.

Hope this helps!

Kurt

Technorati Tags: ,
Avatar of kurtvh

by kurtvh

Service Manager management servers in NLB

2:31 pm in Service Manager by kurtvh

Hello,

The following procedure will guide you through the installation and configuration of the Network Load Balancing functionality with multiple Service Manager management servers.

Network load balancing in Windows Server 2008 lets you to configure a pool of computers so that they take turns responding to requests. In Service Manager, the initial Service Manager management server you deploy is the server that processes workflows. You can deploy additional management servers to provide fail-over for a failed initial management server and to provide load balancing for handling Service Manager console.

As a minimum, you have to deploy an initial Service Manager management server, the management server that hosts the workflow processes, and at least one additional Service Manager management server. You can always install more management servers in your environment, for example to have a dedicated workflow mgmt server, and exclude them from the NLB cluster.

SCSMNLB

Installation information of the SCSM environment can be found here:

Installation of the NLB feature in server 2008 (R2):

  • Click Start, click Administrative Tools, and then click Server Manager. In the Features Summary area of the Server Manager main window, click Add Features.
  • In the Add Features Wizard, select the Network Load Balancing check box and confirm the installation.
  • Click Install.

image

To create a new NLB cluster

  • To open Network Load Balancing Manager, click Start, click Administrative Tools, and then click Network Load Balancing Manager.
  • Right-click Network Load Balancing Clusters, and then click New Cluster.
  • To connect to the host that is to be a part of the new cluster, in the Host text box, type the name of the host, and then click Connect.
  • Select the interface that you want to use with the cluster, and then click Next. (The interface hosts the virtual IP address and receives the client traffic to load balance.)

image

  • In Host Parameters, select a value in Priority (Unique host identifier). This parameter specifies a unique ID for each host. The host with the lowest numerical priority among the current members of the cluster handles all of the cluster’s network traffic that is not covered by a port rule. (You can override these priorities or provide load balancing for specific ranges of ports by specifying rules on the Port rules tab of the Network Load Balancing Properties dialog box. )

image

  • Click Next to continue.
  • In Cluster IP Addresses, click Add and type the cluster IP address that is shared by every host in the cluster. NLB adds this IP address to the TCP/IP stack on the selected interface of all hosts that are chosen to be part of the cluster.

image

  • Click Next to continue.
  • In Cluster Parameters, select values in IP Address and Subnet mask. Type the full Internet name that users will use to access this NLB cluster.
  • In Cluster operation mode, click Unicast to specify that a unicast media access control (MAC) address should be used for cluster operations. In unicast mode, the MAC address of the cluster is assigned to the network adapter of the computer, and the built-in MAC address of the network adapter is not used. It is recommended that you accept the unicast default settings.

image

  • Click Next to continue.
  • In Port Rules, click Edit to modify the default port rules. SCSM console make connection to port 5724. In this example only this network traffic is load balanced.

image

  • Wait until the NLB configuration is set on the first NLB member
    • Review log entries below the NLB mgmt console.
    • Status of the first NLB cluster member should be “Converged”.
  • To add more hosts to the cluster, right-click the new cluster, and then click Add Host to Cluster. Configure the host parameters (including host priority, dedicated IP addresses, and load weight) for the additional hosts by following the same instructions that you used to configure the initial host. Because you are adding hosts to an already configured cluster, all the cluster-wide parameters remain the same.

image

  • Same procedure, wait until the NLB configuration is set on the first NLB member
    • Review log entries below the NLB mgmt console.
    • Status of the first NLB cluster member should be “Converged”.

Job done, in normal cases you should be able to connect the mgmt console to the virtual NLB name.

SNAGHTML6a392ee

Some attention points that can help debugging failure of connection.

  • Security rights, of course you need to have the needed rights in SCSM to connect. No special configuration on this topic. If you can connect to the physical name you should also be able to connect to the virtual name.
  • Network issues can block the connection to the management servers. Work together with the network team to solve firewall,switch,… issues.
  • You need to manually configure the DNS A record for resolving the virtual name.
  • SPN registration: additional Kerberos SPN registration for the virtual NLB cluster name to the SDK account is required to make Kerberos working in the clustered environment. (MSOMSdkSvc/Netbios name & FQDN – Otherwise NTLM authentication is used)

Have fun,

Kurt Van Hoecke

Technorati Tags: ,,
Avatar of kurtvh

by kurtvh

SCSM–DataAccessLayer warning with event ID 33333

9:23 am in Uncategorized by kurtvh

Hello,

A hotfix for Cumulative Update 1 for System Center Service Manager 2010 SP1 ( http://support.microsoft.com/kb/2538810 ) is released in order to address the following issues:

Issue 1

After installing the Cumulative Update 1 for System Center Service Manager 2010 SP1 the SCSM Mgmt servers start logging the following events:

Log Name: Operations Manager
Source: DataAccessLayer
Event ID: 33333
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Description:
Data Access Layer rejected retry on SqlError:
Request: EntityChangeLogSnapshot — (ManagedTypeId=a604b942-4c7b-2fb2-28dc-61dc6f465c68), (BeginTransactionId=68184), (EndTransactionId=68226), (RETURN_VALUE=1)
Class: 15
Number: 156
Message: Incorrect syntax near the keyword ‘INNER’.

Log Name: Operations Manager
Source: DataAccessLayer
Event ID: 33333
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Description:
Data Access Layer rejected retry on SqlError:
Request: EntityChangeLogSnapshot — (ManagedTypeId=a604b942-4c7b-2fb2-28dc-61dc6f465c68), (BeginTransactionId=68184), (EndTransactionId=68226), (RETURN_VALUE=1)
Class: 15
Number: 102
Message: Incorrect syntax near ‘,’.

Important note is added on the Microsoft support KB: The GUIDs and transaction IDs vary, depending on the environment. However, the text in the description is the same.

Issue 2

Duplicated notifications or workflows that are triggered two times for the same object.

I recently encountered this issue and this fixed the issue.

Have fun,

Kurt