Tech for the Enterprise

May 3, 2010

Moving SharePoint 3.0 from one server to another

Filed under: Microsoft — Rick @ 8:21 am

(Specifically Windows 2003 32-bit to Windows 2008 R2 64-bit)

This should also work if you are moving SharePoint from a Windows 2003 32-bit to a Windows 2008 R2 64-bit. This is for a single server farm. The SQL Server can be on a separate machine.

Make a batch file. If you are using Windows 2008 or 2008 R2 make sure when you run the batch file to right click and click “Run as administrator”

********* Start Batch File *************

C:

cd\

cd Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN

stsadm -o backup -url https://sharepoint.domain.com -directory \\192.168.1.50\Wholesite -backupmethod full -percentage 10 -backupthreads 3

pause

********* End Batch File *************

The batch file needs to have the URL of the site you are backing up and a UNC path to the folder that will store the backup files. Note: The UNC path is only needed if the SQL Server is a separate machine from the SharePoint server. Without the UNC path the SQL Server would not know where to put the backups of the databases and thus error.

Run the backup batch file.

Install SharePoint on the new server.

When I install SharePoint I use the Advanced Option then I select “Web Front End…” then I click “Install Now” This gives you more options and allows you to select whatever SQL Server you want.

At the end I leave the box checked that says “Run the SharePoint and …” and Click Close.

When the Wizard runs I select “No, I want to create a new server farm”. Now is when you need to put in your database information. The user name needs to be a Windows login not SQL. Note: “If you are using both 64-bit SQL and SharePoint you may need to enable the TCP/IP protocols for the 64-bit the 32-bit seem to be enabled by default.

That is it. Now let’s restore.

Create a batch file. If you are using Windows 2008 or 2008 R2 make sure when you run the batch file to right click and click “Run as administrator”

Here you can use a SQL login

********* Start Batch File *************

c:

cd\

cd Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN

stsadm -o restore -hostheaderwebapplicationurl http://sharepoint.domain.com -directory \\sharepointtest\restoresp -restoremethod new -username sa -password xxxxxxxx -newdatabaseserver sql2008

pause

********* End Batch File *************

KEY: The SQL Server SQL Service has to be running under an account that has access to the Share where your restore files are located.

The first thing you will get asked is “New web application URL” and it will give you a default option but do not use it. This will be the default from the server you backed up from. The only exception is if this server has the same server name. We want to use something like https://servername:portnumber. The S in https is optional and will depend on if you used SSL in the backed up SharePoint site.

  1. Then it asks you for the “New web application name” I leave this at the default.
  2. Now it asks you for “New server name”. This is your SQL server name. You need to enter the name of the SQL server. It can be just the server name or you may need to enter servername\incidentname.
  3. “New directory name” I look at the default data path on the SQL server and I use that. Sample “C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA”
  4. “New database name” you can select the default.
  5. “New web application URL” this is where you want to use the URL of your SharePoint Site. Example https://sharepoint.domain.com/ Make sure and use the S if you are using SSL.
  6. “New web application name” You can use the Default.
  7. “New server name” this is the SQL Server name again. Same as #2
  8. “New directory name” Same as #3.
  9. “New database name” You can use the Default.
  10. “New server name” Same as #2.
  11. “New directory name” Same as #3.
  12. “New database name” You can use the Default.

Now if you restored a site that uses an SSL Certificate you need to attach that certificate to the IIS web site that was created during the Restore.

February 7, 2010

An I/O operation initiated by the Registry failed unrecoverably. The Registry could not read in, or write out, or flush, one of the files that contain the system’s image of the Registry.

Filed under: Microsoft,Misc,Software — Rick @ 9:51 pm

As time went on I realized this did not fix the issue. I restored the machine to an earlier vision and then restored the databases and that did work. This is a virtual machine this made restoring very easy.

Started getting this error* the other day. I look on line and searched but could not come up with anything that fixed it.

*An I/O operation initiated by the Registry failed unrecoverably. The Registry could not read in, or write out, or flush, one of the files that contain the system’s image of the Registry.

Seeing it was an I/O error and I saw something on Microsoft saying something about disk operations I thought why not try a chkdsk /f and sure enough that fixed it. I took a re-boot because this was the system drive but it worked.

February 3, 2010

mapi32.dll is an invalid Extended MAPI Library and Mail is not installed

Filed under: Exchange Server,Microsoft — Rick @ 11:00 pm

I had a customer that uses Word 2007. They were having a problem when they clicked Send and “Send as PDF” and was getting this error “mapi32.dll is an invalid Extended MAPI Library” and “Mail is not installed”. I could not figure it out.

Finally I got to another computer in the office and compared the mapi32.dll files. They both had Office 2007. They were quite different  in size so I renamed the mapi32.dll on the machine throwing the error and copied over the mapi32.dll from the second computer and after that it worked fine.

Before I copied the mapi32.dll I also installed “2007 Microsoft Office Add-in: Microsoft Save as PDF or XPS” but I do not think I really needed to do that.

December 2, 2009

Office 2010 / Outlook 2010

Filed under: Microsoft,Software — Rick @ 10:36 am

I have been using Outlook 2010 now for several days. I like it better that Outlook 2007 but again they have changed some stuff around. Not nearly as different as the change was from Office 2003 to 2007.

One changed feature is the file tab. I especially like the layout of File Tab better that the standard file menu.

I also like the layout of the new Ribbon compared to Outlook 2007.

If you use 2 accounts in Outlook they have move the accounts drop down. This is used when sending an email. You can choose which email address you want the email to come “From:” this also changes your signature if you have one set up for each account. The drop down is now above the “To:” field and is more appropriately called “From”.

Another thing I do like is the threading of discussions grouping as a default. The only thing about this is I wish they had made it a little smarter. It only groups on Subjects and not content. So for example when I email a distributor for a price a lot of the time in the Subject I will say “Price Please”. Well it groups these together even if they are not from the same discussions or thread. If they looked into the message (they already have it on indexed on the Exchange Server) and picked out key words they could group it on true discussions.

Overall I’m Happy with this new Outlook 2010 and think it will be a nice upgrade.

November 28, 2009

Office 2010 Installation Errors

Filed under: Microsoft — Rick @ 2:15 pm

I tried installing the Office 2010 Beta 64 and got an error. So I thought forget the 64 and install the 32-bit. Not too many people need the 64-bit anyway. I don’t but I thought I should get the experience anyway. I will be uninstalling 64-bit and installing the 32-bit soon. I like that my Outlook profiles stayed in please even after I uninstalled Office 2007.

First off I got this error:

Error: 1935: An error occurred during the installation of assembly competent {659FB0C5-3A28-4A7D-B6FD-322E91478238}. HRESULT: 0×80070005

Then I got Error: 2203.

Really there was a simple fix for both but I think Microsoft will need to make this a little simpler to have the masses installing it.

The fixes were… Well the first thing I should have done right off the bat was right click on the executable and click run as administrator. That being said I would have thought their Office even Beta could be installed without disabling THEIR Anti-Virus. Yes I am running “Microsoft Security Essentials” on my home office computer. I had to disable “Real-Time Protection” in order to get Office 2010 Beta to install.

Powered by WordPress