Microsoft has made a hotfix available for an issue that might crash your browser when opening a document from a SharePoint 2007 site in Office 2007.
This problem occurs if the following conditions are true, in the order in which they are presented:
• You install a Microsoft Office 2003 product on the computer.
• You install one or more 2007 Office system programs on the computer.
• You repair or update the installation of an Office 2003 product.
http://support.microsoft.com/kb/938888
23 July 2007
28 June 2007
Domain migrations and SPUserUtil
Although SharePoint Server 2007 is here there might still be people out there using SharePoint 2003 who will want to migrate users into another AD domain. Keith Richie has created the excellent SPUserUtil for this and there is plenty of information about using this utility to migrate domain users.
I ran into an issue while testing a domain migration and using SPUserUtil where certain stored procedures could not be found that should have been installed by the hotfix or SP2. Comments to a post on BlueDogLimited describes the same issue: "Could not find stored procedure 'dbo.sps_hMigrateAreaContactSids'."
The most likely reason that these stored procedures (there seem to be 4 of them) are not available is that the SITE database that contains the Portal site was originally created on SPS SP1 and then restored into a SP2 environment. The stored procedures are only created when you create a new portal on SP2. You can find the stored procedures in the portal site database when you create a new portal on your SPS2003 SP2 environment. These are the missing procedures:
Orgle_UpdateOrgleRulesWithMigratedAccounts (Profile database)
profile_UpdateUserProfileSID (Profile database)
sps_hMigrateAreaContactSids (Portal site database)
sps_hMigratePersonListingSids (Portal site database)
I ran into an issue while testing a domain migration and using SPUserUtil where certain stored procedures could not be found that should have been installed by the hotfix or SP2. Comments to a post on BlueDogLimited describes the same issue: "Could not find stored procedure 'dbo.sps_hMigrateAreaContactSids'."
The most likely reason that these stored procedures (there seem to be 4 of them) are not available is that the SITE database that contains the Portal site was originally created on SPS SP1 and then restored into a SP2 environment. The stored procedures are only created when you create a new portal on SP2. You can find the stored procedures in the portal site database when you create a new portal on your SPS2003 SP2 environment. These are the missing procedures:
Orgle_UpdateOrgleRulesWithMigratedAccounts (Profile database)
profile_UpdateUserProfileSID (Profile database)
sps_hMigrateAreaContactSids (Portal site database)
sps_hMigratePersonListingSids (Portal site database)
14 November 2006
SQL Procedure to script your data
Sometimes you need to insert a few records from a table into another table or another database. Here's the solution: http://vyaskn.tripod.com/code.htm#inserts
Tabbed web part
GotDotNet has a SharePoint 2003 web part for implementing a tabbed interface. One web part provides navigation among pages using tabs, the other allows different web parts on a single page to be controlled using tabs. Link...
SQL Server file locations
In MS SQL Server you can get an overview of all database file locations using the 'sysfiles' table. In combination with the stored procedure 'sp_msforeachdb' (which will loop through the databases) you can get a list of all database files used by the SQL Server instance.
USE master
EXEC sp_msforeachdb 'use ? SELECT ''?'' as dbname, filename FROM sysfiles'
USE master
EXEC sp_msforeachdb 'use ? SELECT ''?'' as dbname, filename FROM sysfiles'
Subscribe to:
Posts (Atom)