Jamie's Blog

Default QLogic SAN Surfer Password

What is the default password for SANsurfer HBA Manager?  

The default password is ‘config’ 
Operating System
  
 
OS
Linux Red Hat
Linux SUSE
MAC OS X
Netware
Solaris
Windows 2000
Windows XP
Windows Vista
Windows Server 2003
Other

Dell Systems Build stuck at 15%

To address a browser limitation around downloading large files (see Microsoft KB article 298618: You cannot download files that are 2 GB or larger instead:

Download the two ISO file segments to a new, empty folder and concatenate them. Create a single DVD image file using the following commands:
Windows: copy /b OM* OM_6XX_SMTD_A00.iso
Linux: cat OM* > OM_6XX_SMTD_A00.iso

Ghost NetBackup Jobs In Queue

If there are jobs which appear “hung” in the NetBackup Activity Monitor, it is possible a stop and restart of the NetBackup services/daemons may not clear them. If a queued job cannot be canceled or killed, note the job ID (for the example, assume the job ID 397084), and then do the following:

1. When there are no backup or restore jobs running, stop all NetBackup services/daemons on the master server
2. Delete any files with 397084 in the name from the /usr/openv/netbackup/db/jobs/trylogs/ and /usr/openv/netbackup/db/jobs/ffilelogs/ directories on the master server (the <install_path>\veritas\netbackup\db\jobs\trylogs and <install_path>\veritas\netbackup\db\jobs\ffilelogs directories on a Windows master server).  
3. Delete the /usr/openv/netbackup/db/jobs/bpjobd.act.db file (the <install_path>\veritas\netbackup\db\jobs\bpjobd.act.db file on a Windows master server)
4. Restart the NetBackup services/daemons

Because the bpjobd.act.db file contains active and queued jobs, deleting it will only remove the unwanted job, since no other jobs were running at the time that the NetBackup services/daemons were stopped. Completed jobs are stored in bpjobd.db file, so do not remove it.

Installing and Configuring MOSS 2007 and SQL 2008

When installing SharePoint on the initial servers we need to do an full install as follows:

1. Install from CD ->Click Advanced

Click Complete and Finish Install

When setting a service account as the application pool you must grant DCOM permissions as follows

—-
You may see this error – more than once – when working with your Microsoft Office SharePoint Server (MOSS) 2007 deployment. This animal / error generally shows itself after you have applied an upgrade to an existing deployment. For example, when upgrading from B2 MOSS to B2TR MOSS – or when applying a special service pack from MSFT – you may begin to see a lot of these errors pop up in the SYSTEM event log.

The error CLSID is followed by a class ID for the DCOM+ application that the service account trying to activate that application – does NOT have permission to activate.

For example, let’s say I installed MOSS on a server, and used the account mossService as the service account (a least privileged, user account you created to run the MOSS service(s))., when I get this error, I could very well see an error like the following:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

{61738644-F196-11D0-9953-00C04FD919C1}

to the user <serverName>\mossService SID (S-1-5-21-<serviceSID>). This security permission can be modified using the Component Services administrative tool.

Copy the GUID following the CLSID above, and Start–>Run–>regedit

With the registry editor open, ensure that your cursor is on the computer at the beginning of the tree (make sure you are not in the middle of some previous edit session in the registry editor).

Edit–>Find and paste in the GUID. It’ll stop at the application entry – and you will want to note the application name on the right side pane. In this example, it was the IIS WAMREG admin service that popped up.

Now, open Component Services (typically, from the server – Start–>Administrative Tools–>Component Services), expand Component Services, Computers, My Computer, DCOM Config. Scroll down and find the application (IIS WAMREG in this case). Right-Click–>Properties and select the Security tab. You’ll have some options here – the first block Launch and Activation Permissions – ensure that the Customize radio button is selected, and click Edit. Now, add your service account – giving it launch and activate – and in some requirements – remote launch / activate permission.

Restart IIS and continue on.

NOTE: This is not applicable to MOSS setups only – and hopefully this will help someone else that sees these annoying DCOM errors in their SYSTEM event log.
—–