Make IT Complete

I found that the SBS2003 licenses are kept in the licstr.cpa file in the WINDOWS\system32 folder. Thankfully, Microsoft actually keep an automatic backup of this in autolicstr.cpa. The simple process was to stop the License Logging Service, rename licstr.cpa to licstr.cpa.old, then copy autolicstr.cpa to licstr.cpa. After this I started License Logging Service and used Server Management to confirm that the licenses had been restored.

Check the instructions in the lower section of the page:

http://blogs.technet.com/corybu/archive/2007/06/01/detaching-databases-in-moss-2007-environments.aspx

Basically:

First we need to find out which databases are currently not in sync, this can be done from a simple stsadm command on your SSP web front end.

stsadm -o sync -listolddatabases 5

This command will list all databases that have not synced up correctly with the SSP in greater than 5 days.  Based on your schedule to index your age value may change.  You may want to change this value to 10 or 15.  The result set returned is a list of database GUID’s and the date/time they were last synchronized. Now that we have determined the list we need to clean them up and get those guys synced.  To do this we execute an stsadm command that sets all of those GUID’s as old, then during your next index it will pick up the new GUID’s for your production databases not currently being synced.

stsadm -o preparetomove -contentdb sqlserver:dbname -oldcontentdb <GUID>

where sqlserver is where your content is housed, dbname is any database in your child farm, and GUID is a guild from the list of non-syncing databases we generated with the command above.

Based on your crawl schedule wait until the next full crawl.  Once it completes go back into your SSP and run the stsadm -o sync -listolddatabases 5 command again.  Anything left can likely be removed at this point.  You can remove what is left by running the following command.

stsadm -o sync -deleteolddatabases 5

this will delete all GUID entries in the SSP for anything that is out of sync for more than 5 days.  You have now successfully cleaned all inconsistencies with syncing in your SSP.  All out of sync alerts should now subside.

Remember use stsadm -o preparetomove before detaching a database and this will not be a problem!

Released LitterSitter.com today.  Litter Sitter is a pet sitting service located in Sugar Land Texas.  If you are in Sugar Land and need pet sitting services please contact them at http://www.litterservice.com

- External SQL Server Database Move

•  Log Shipping Method(low impact)

To migrate your content database from 1 SQL Server to another there are a few choices, your choice will depend on how much downtime you are willing to take.  First option being you can setup SQL Log shipping, Once your 2 databases are in sync you would do the following steps.

 Stsadm –o preparetomove –contentdb SQLServerA:demo_content_1

 Stsadm –o deletecontentdb –url http://demo –databasename demo_content_1 –databaseserver SQLServerA

 At this point you would perform the final cutover on your log shipped database to SQLServerB

 Then finish with

 Stsadm –o addcontentdb –url http://demo –databasename demo_content_1 –databaseserver SQLServerB

• Copy Method(high impact)

Your other option would be to simply detach the database from SQL and copy the .mdf and .ldf to the new SQL server.  While in transit your users will get a generic “Cannot connect to content database” error when visiting their site.  Following the copy you would perform the following on your web front end.

 Stsadm –o preparetomove –contentdb SQLServerA:demo_content_1

 Stsadm –o deletecontentdb –url http://demo –databasename demo_content_1 –databaseserver SQLServerA

 Stsadm –o addcontentdb –url http://demo –databasename demo_content_1 –databaseserver SQLServerB

This link has some good info about the problem I am having.

http://vivekthangaswamy.blogspot.com/2007/12/enabling-drop-down-menu-for-multi-level.html

I find this useful when restoring a SQL database and then needing to reconnect the database use to the login account.

This used to be a pain to fix, but currently (SQL Server 2000, SP3) there is a stored procedure that does the heavy lifting.

All of these instructions should be done as a database admin, with the restored database selected.

First, make sure that this is the problem. This will lists the orphaned users:

EXEC sp_change_users_login 'Report'

If you already have a login id and password for this user, fix it by doing:

EXEC sp_change_users_login 'Auto_Fix', 'user‘

If you want to create a new login id and password for this user, fix it by doing:

EXEC sp_change_users_login 'Auto_Fix', 'user‘, ‘login‘, ‘password‘

They ended up deactivating my phone by mistake.  So now we are trying to get that all fixed up.  We are porting Carrie’s number to AT&T

Adobe Creative Suite 3 products crash when you save, open, or place a file, after installing the Version Cue CS3 3.1.0 update (Mac OS X v10.4.x - 10.5)

ISSUE

After you install the Adobe Version Cue CS3 3.1.0 update, the following Creative Suite 3 products may crash when you attempt to save, open, or place a file on Mac OS X:
Adobe InDesign CS3
Adobe InCopy CS3
Adobe Illustrator CS3
Adobe Photoshop CS3
Adobe Flash CS3 Professional
Adobe Bridge CS3
REASON

The Version Cue update was not successfully completed and the installed VersionCueUI.framework file is damaged.

SOLUTION

Download and run the FixVCUIFramework application.

Click this link: download the FixVCUIFramework.zip file.
Double-click FixVCUIFramework.zip to decompress it.
Double-click the FixVCUIFramework application.
When prompted, enter your password for the administrative user of the machine.

Note: There is no visual feedback that the script ran successfully, but the completion of it is instantaneous. You don’t need to reboot.

You can now use the Creative Suite 3 products as expected.

SPDisposeCheck is a tool to help SharePoint Developers follow memory management best practices when using the SharePoint API with IDisposable objects including SPSite and SPWeb. This tool is not supported by Microsoft and is recommended to be used on Developer workstations and not on production SharePoint Server installations.

It was released yesterday at http://code.msdn.microsoft.com/SPDisposeCheck

The tool reviews a .NET Assembly (DLL or EXE) and evaluates SharePoint API’s used in that assembly. It will produce a report identifying where code doesn’t follow best practices for memory management in SharePoint. It may not find all memory leaks in your code and it may produce false positive results but it does it much faster than you can review source code yourself. The tool checks for guidance published in an update to the MSDN Article (Best Practices: Using Disposable Windows SharePoint Services Objects) that describes the best practices for this area of SharePoint development. This guidance applies only to customers building custom software that they compiled to .NET assemblies that make use of SharePoint API calls. While these messages need expert evaluation in order to determine if the software is not performing properly, in some cases just running the tool on your custom code can lead you to simple fixes that improve the quality and performance of custom code on SharePoint. Customers who are currently experiencing difficulties with memory management in their custom applications should review the guidance listed above. Customers who are currently experiencing difficulties with Microsoft Office SharePoint Server 2007 should contact their regular Microsoft Customer Support Services contact, or refer to http://support.microsoft.com.

I found this tip to be very helpful.  It will let you capture a single element from the screen instead of drawing a banding box around the object and then cropping it in another application later.  This is great for writing documentation.

http://www.apple.com/pro/tips/screenshots.html?sr=hotnews?sr=hotnews.rss