Jun 18

MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-2147467259)

This solution is with regards to the following error message. Unfortunately now I am running all my software in spanish so the error code is half in Spanish and half in English. This error is generated when you try to mount a database in Exchange 2007 right after you are done installing. The Public Folder Database works fine though.

——————————————————–
Microsoft Exchange Error
——————————————————–
No se pudo montar la base de datos "Mailbox Database".

Mailbox Database
Error
Error:
Exchange no puede montar la base de datos especificada. Base de datos especificada: ServerNameFirst Storage GroupMailbox Database; código de error: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-2147467259)

In order to resolve this issue follow the steps on KB925825 at http://support.microsoft.com/kb/925825/en-us

I've seen some issues with people trying to run Setup /PrepareAD as it will indicate the following message:

C:Usersusername>Setup /PrepareAD
Welcome to Microsoft Exchange Server 2007 Unattended Setup
Preparing Exchange Setup

Exchange Server setup encountered an error.

This is due to the fact that you are not running the command line as an Administrator. Remember that in Vista and Windows 2008 you must run CMD as an administrator. Right click the Command Prompt shortcut and select the Run as Administrator option before you try to prepare AD.

I would also suggest you take a look at the help for preparing AD for an Exchange 2007 installation. Here is an extract from the KB on how to do that:

Click the Contents tab, expand Deployment, expand New Installation, expand Preparing to Deploy Exchange 2007, and then click How to Prepare Active Directory and Domains.

Finally, I also found that this is the sequence you want to follow to prepare your AD for deployment:

  1. Setup /PrepareSchema 
  2. Setup /PrepareAD

I had done the /PrepareSchema but missed the /PrepareAD. Once I did that I was able to mount the store. Good luck to everyone! 

Feb 03

Client Application Services

So, I was trying to do an application I have been avoiding for the past 8 years and the first thing I began working at was the authentication part of it. I remembered ASP.Net had membership and roles features with their authentication and login functionality so I was looking around for that. This time I decided to make it simple by just doing a Windows application using WPF (Windows Presentation Foundation). To my surprise it seems you can only use the authentication in ASP.Net and there is nothing built-in for a Windows Application. This time around though (ASP.Net 3.5) they have the Client application services which "enables your Windows-based applications to use the ASP.Net login (authentication), roles, and profile (settings) services" (Visual Studio 2008 Services Screen). It is a pain to figure out how to set everything but here is the general overview of what I've discovered thus far:

  1. You need some sort of database to store your users and roles and what not just as in ASP.Net
  2. You need a web service to provide authentication services for your Windows application
  3. You need to check out this walkthrough. After hours of internet search I think this is your one place to learn 90% of what you need.

 

Jul 01

Useful tool

The following allows you to safelly share your computer with others:

http://www.microsoft.com/downloads/details.aspx?FamilyId=D077A52D-93E9-4B02-BD95-9D770CCDB431&displaylang=es

Jun 27

Executing or Opening Control Panel Items

 Sometimes you have to open or access Control Panel Items via a script or you want to open it for a remote client and it is kind of hard to come up with a command line to address that issue. Microsoft has posted in their MSDN website (http://msdn2.microsoft.com/En-US/library/bb419052.aspx) information regarding how to do this.

Most importantly, if your application wishes to open an item in the Control Panel you use:

WinExec("c:windowssystem32control.exe MyCpl.cpl", SW_NORMAL);

And if you simply wish to open something like the Printers and Faxes folder, take a look at this (obtained as is from the website mentioned above):

 

Legacy Control Panel Commands

When you use the WinExec function, the system can recognize special
Control Panel commands. These commands predate Windows Vista.

control.exe desktop Launches the Display Properties window.
control.exe color Launches the Display Properties window with the Appearance tab
preselected.
control.exe date/time Launches the Date and Time Properties window.
control.exe international Launches the Regional and Language Options window.
control.exe mouse Launches the Mouse Properties window.
control.exe keyboard Launches the Keyboard Properties window.
control.exe printers Displays the Printers and Faxes folder.
control.exe fonts Displays the Fonts folder.

For Windows 2000 and later systems:

control.exe folders Launches the Folder Options window.
control.exe netware Launches the Novell NetWare window (if installed).
control.exe telephony Launches the Phone and Modem Options window.
control.exe admintools Displays the Administrative Tools folder.
control.exe schedtasks Displays the Scheduled Tasks folder.
control.exe netconnections Displays the Network Connections folder.
control.exe infrared Launches the Infrared Monitor window (if installed).
control.exe userpasswords Launches the User Accounts window.

 Alternatively you can try something like:

 ::{2227A280-3AEA-1069-A2DE-08002B30309D}

That would open the Printers and Faxes if ran from the Start–>Run Menu. You can probably leverage this and use similar IDs for different things in Windows.  

Aug 29

How to add computers to a Domain via Scripting

I personally prefer to use the solution provided by Berkeley found at http://calnetad.berkeley.edu/documentation/scripts/.
I went ahead and downloaded the joinDomain.cmd
script and made slight changes to it. I also got the latest netdom.exe from the
support tools from the Windows 2003 R2 CD. I might add the zip file in the future just in
case they take it offline, but I think this is a good resource nevertheless.

Jul 15

“Service Unavailable” message when you access a website (when installing 32 and 64 bit versions of ASP.Net)

Let me clarify that about a billion things (ok, probably no more than a 100) can cause this error message, so this is just a particular scenario and it happens when you have 32 and 64 bit versions of asp.net installed on your web server. Here is an easy way to move around versions. In my case, I was happy with my 64 bit version, but I needed the 32 bit asp 1.1.xxxx to run the BDD on my server, so… I had to install it. Anyways, what a pain one thing breaks another, but here is how to fix it!!

obtained from: http://support.microsoft.com/?id=894435

ASP.NET 1.1, 32-bit version

loadTOCNode(2, 'moreinformation');
To run the 32-bit version of ASP.NET 1.1, follow these steps:

1. Click Start, click Run, type cmd, and then click OK.
2. Type the following command to enable the 32-bit mode:

cscript %SYSTEMDRIVE%inetpubadminscriptsadsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1
3. Type the following command to install the version of ASP.NET 1.1 and to install the script maps at the IIS root and under:

%SYSTEMROOT%Microsoft.NETFrameworkv1.1.4322aspnet_regiis.exe -i
4. Make sure that the status of ASP.NET version 1.1.4322 is set to Allowed in the Web service extension list in Internet Information Services Manager.

ASP.NET 2.0, 32-bit version

loadTOCNode(2, 'moreinformation');
To run the 32-bit version of ASP.NET 2.0, follow these steps:

1. Click Start, click Run, type cmd, and then click OK.
2. Type the following command to enable the 32-bit mode:

cscript %SYSTEMDRIVE%inetpubadminscriptsadsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1
3. Type the following command to install the version of ASP.NET 2.0 (32-bit) and to install the script maps at the IIS root and under:

%SYSTEMROOT%Microsoft.NETFrameworkv2.0.40607aspnet_regiis.exe -i
4. Make sure that the status of ASP.NET version 2.0.40607 (32-bit) is set to Allowed in the Web service extension list in Internet Information Services Manager.

ASP.NET 2.0, 64-bit version

loadTOCNode(2, 'moreinformation');
To run the 64-bit version of ASP.NET 2.0, follow these steps:

1. Click Start, click Run, type cmd, and then click OK.
2. Type the following command to disable the 32-bit mode:

cscript %SYSTEMDRIVE%inetpubadminscriptsadsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0
3. Type the following command to install the version of ASP.NET 2.0 and to install the script maps at the IIS root and under:

%SYSTEMROOT%Microsoft.NETFramework64v2.0.40607aspnet_regiis.exe -i
4. Make sure that the status of ASP.NET version 2.0.40607 is set to Allowed in the Web service extension list in Internet Information Services Manager.

Note The build version of ASP.NET 2.0 may differ depending on what the currently released build version is. These steps are for build version 2.0.40607.

Jul 12

How to enable ink

  1. Ink is only supported on Internet Explorer as it is an activex plug-in
  2. To enable ink, you have to activate it in your user profile. Just click your username in the upper right corner and set enable ink to yes under the "Site Options" tab. To learn more about Profile settings and options, click here to read the guide.
  3. You'll need to add the website that has the ink to your list of trusted sites in IE (Internet Explorer)
    • Tools
      > Internet Options > 'Security' tab > 'Trusted Sites' > click
      the Sites button.
    • In the Trusted sties window type https://*.jcbauza.com and http://*.jcbauza.com to trust the entire site. You might run into the issue of having a window display "Site added to this zone must use the https:// prefix. This prefix assures a secure connection." Just click ok, uncheck the checkbox that says "Require server verification (https:) for all the sites in this zone, click add, recheck the checkbox, click OK.
  4. You might run into more issues if you have the .Net framework 2.0 installed. If you do, follow this instructions:
  • If you have the .NET Framework
    version 2.0 installed, Internet Explorer will try to use the v2.0 runtime
    to run the hosted component. To keep Internet Explorer from doing this,
    you must setup a .config file for Internet Explorer to use, to force it
    to use v1.1 of the .NET Framework. To do this, create a file named iexplore.exe.config
    in Internet Explorer's home directory (e.g. C:Program FilesInternet
    Explorer) and put the following XML into it:

    <configuration>
    <startup>
    <supportedRuntime version="v1.1.4322"/>
    <startup>
    <configuration>

    That didn't work for me personally, but uninstalling the .Net framekwork 2.0 did work :O. I seriously would try that and look around before uninstalling it, as it might be needed for some other program you might have, plus ink is just a nice bonus, not a must have thing I think. Best of luck!!

Jul 09

Error 28805 Setup cannot finish the request to the SQL Server 2005 Reporting Service report server. Verify that the report server is installed and running, and that you have sufficient privledges to access it.

Seriously, this error message is such a drag… I had to reinstall the stupid thing over and over and I even went through the trouble of reinstalling the whole server when the only problem was Reporting Services was using a certificate… Anyways, that's all you have to do, go to the Reporting Services configuration manager, and turn off the SSL requirements for the website. If you need more assistance with error codes, I found this usefull readme: enjoy!!

Visual Studio 2005 Team Foundation Server Readme

Updated May 15, 2006

See Visual Studio 2005
Team Foundation Server Known Issues
for non-setup related issues.

 

1. System Requirements

The system requirements for Team Foundation Server and Team Explorer are
located in the Team Foundation Installation Guide. The most current version of
the Installation Guide is available for download from the Microsoft Download
Center. For more information, see http://go.microsoft.com/fwlink/?LinkId=40042.

1.1    Installing Team Foundation Server That Has Microsoft SQL Server 2005
(32-Bit) on a 64-Bit operating system is not supported.

If you try to install Team Foundation Server on a 64-bit operating system
with Microsoft SQL Server 2005 (32-bit), setup does not detect the SQL Server
services and blocks installation.

To resolve this issue

Use dual-server deployment, complete the installation steps for the Team
Foundation data tier using Microsoft SQL Server (64-bit). For more information,
see the topics "Team Foundation System Requirements" and "Overview of Team
Foundation Server Dual-Server Deployment" in the Installation Guide.

2. Product Installation

2.1   Antivirus applications that are configured to clean the temp folder
will cause setup to fail if it must restart.

If setup must restart, and the antivirus application is set to clean the
temp directory on start, required setup files will be deleted and setup will
fail with a program not found error.

To resolve this issue

Restart setup after restarting the computer.

2.2    Time-Out errors occur when the Team Foundation Server application and
database tiers are separated by many network hops.

In this release, high latency between the Team Foundation Server application
and database tiers may cause time-out errors when you are trying to transfer
large files between the two tiers.

To resolve this issue

Minimize the number of network hops between the Team Foundation Server
application and the database tiers.

2.3    Installing SQL Server 2005 using the provided answer file fails on
non-English editions of Windows Server 2003.

When you use the provided answer file to install SQL Server 2005, you may
receive the following error:

"SQL Server Setup could not validate the service accounts. Either the service
accounts have not been provided for all the services being installed, or the
specified username or password is incorrect. For each service, specify a valid
username, password, and domain, or specify a built-in system account."

To resolve this issue

The answer file provided with Team Foundation Server contains English user
account names that will cause setup to fail on non-English editions of Windows
Server 2003. Modify the answer file to use the correct localized names for the
specified accounts.

2.4   Error 32000 (ConfigureNTLM.exe /addntlm "Team Foundation Server"
returned non-zero value: 1) during Team Foundation Server setup.

If you install Team Foundation Server on a server that is already using TCP
port 8080, Team Foundation Server setup will fail because this port is required
for the Team Foundation Server Web site, even if the Web site on port 8080 is
stopped during setup.

To resolve this issue

Make sure TCP port 8080 is not already being used before you install Team
Foundation Server. Delete all Web sites bound to port 8080 or change their port
number.

2.5    Error 32000 (ConfigureNTLM.exe /addntlm "Team Foundation Server"
returned non-zero value: 1) during Team Foundation Server Proxy setup.

If you install Team Foundation Server Proxy on a server that is already using
TCP port 8081, setup will fail, even if the Web site on port 8081 is stopped
during setup.

To resolve this issue

Make sure TCP port 8081 is not already being used before you install Team
Foundation Server Proxy. Delete all Web sites bound to port 8081 or change their
port number.

2.6    Error 28918 TFServerStatusValidator: ErrorMakingWebServiceCall when
you run Team Foundation Server (services) Setup.

When you run Team Foundation Server (services) Setup, you may receive the
following error:

Error 28918.TFServerStatusValidator: ErrorMakingWebServiceCall – the tool did
not succeed calling Tfs Registration Web service. Either IIS is not running or
is not configured correctly.

The default settings for the URLScan Security Tool installed on IIS can cause
this error. If the URL contains more than one period, such as http://localhost:8080/services/v1.0/registration.asmx),
URLScan rejects the request.

To resolve this issue

Configure the URLScan
Security Tool
in the urlscan.ini file to allow for multiple periods in
requested URLs by setting AllowDotInPath=1. For more information, see How to configure the URLScan
Tool
.

2.7   Entering a password with Unicode characters may cause setup to
fail.

Although some Unicode characters are allowed in Windows passwords, Team
Foundation Server setup may fail if Unicode characters are used in
passwords.

To resolve this issue

Do not use Unicode characters in passwords.

2.8   Documentation is outdated or displays pre-release content.

If you previously installed MSDN Library for Visual Studio 2005 or if you use
locally installed Help for Team Foundation or Team Explorer as the primary
source of documentation, you might have outdated or missing Help
documentation.

To resolve this issue

Download and install the most recent edition of MSDN Library to make sure
that you have the latest product documentation for Team Foundation and Team
Explorer. For more information, visit the Team System Documentation Directory at
http://go.microsoft.com/fwlink/?LinkId=62213.

2.9   When working through the installation checklist, use the answer files
for SQL Server 2005 installation.

The most efficient way to install SQL Server 2005 is to use the answer files
instead of the installation wizard.

To resolve this issue

For single server installation, see the answer file procedure in “How to:
Install Microsoft SQL Server 2005 for Team Foundation Server (Single-Server
Deployment)” in the Installation Guide.

For the data-tier of a dual server installation, see the answer file
procedure in “How to: Install Microsoft SQL Server 2005 for Team Foundation
Server (Dual-Server Deployment)” in the Installation Guide. For the
application-tier of a dual server installation, see the answer file procedure in
“How to: Install Microsoft SQL Server 2005 Reporting Services for Team
Foundation Server (Dual-Server Deployment)” in the Installation Guide.

2.10   Error 28100: Error loading Event Web service when you install Team
Foundation Server.

Setup was unable to confirm the application-tier server name. In the MSI log,
you find the following entry: "Failed to load EventService proxy object:
TF30076: The server name provided does not correspond to a server
URI that can be found. Confirm that the server name is correct."

To resolve this issue

Open the registry and delete the registry key
HKEY_CURRENT_USERSoftwareMicrosoftVisualStudio8.0TeamFoundationServers,
and then restart setup.

2.11    Changing service accounts after installation of Team Foundation
Server can cause installation failure. 

If you find that you must change the service accounts you provided during a
previous installation of Team Foundation Server, make the changes using the
security setting options available in Team Explorer or using the TFSAdminUtil
command-line utility before you uninstall Team Foundation Server. Changing the
service accounts using tools other than those provided with Team Foundation
Server could lead to unexpected results. For example, changes to the accounts
using Windows Services Manager and Internet Information Services (IIS) Manager
are not automatically registered in Team Foundation Server.

To resolve this issue

We recommend that you change the accounts after reinstalling or repairing
Team Foundation Server if it is possible. If you must change the accounts when
Team Foundation Server uninstalled, create the accounts and then update the
service accounts for the application pools of Windows SharePoint Services and
Report Server. You can use Internet Information Services (IIS) Manager to update
the application pools.

We recommend that you use domain accounts for the service accounts. If you
chose a single-server deployment and you must use local accounts, make sure that
you include the prefix "machine" before the account name. For example, the
Installation Guide uses "domainTFSSERVICE" as a placeholder for the services
account. If you want to change to a local account by that name, you must specify
the prefix "

2.12   Moving the Internet Information Services (IIS) root directory from
the Inetpub folder to another folder causes Error 32000.

Installation of Team Foundation Server fails with Error 32000. "The
Commandline D:Program FilesCommon FilesMicrosoft SharedWeb Server
Extensions60BinStsadm.exe …' returned non-zero value: -2130242250." because
the Windows SharePoint Services administration site is not setup and Team
Foundation Server cannot configure the site.

The site should be set up during installation of Windows SharePoint Services
but if the Internet Information Services (IIS) root directory was moved from the
Inetpub folder to another folder and the AdminScripts subfolder was not included
in the move, the setup fails silently.

To resolve this issue

  1. Uninstall Windows SharePoint Services.
  2. Move the AdminScripts subfolder from the Inetpub folder to the new root
    directory for IIS.
  3. Re-install Windows SharePoint Services.
  4. Re-install Team Foundation Server.

2.13   Unable to install the application tier across domains that have the
firewall enabled on the data tier.

System Health Check uses remote Windows Management Instrumentation (WMI) when
you install the application tier. WMI requires that the remote administration
port be open on the data tier. If this port in not open, you receive warnings
that the data tier does not appear to be correctly configured.

To resolve this issue

Verify that the port is open on the data tier and then continue past the
System Health check. If you have the Microsoft Firewall enabled, the data-tier
setup opens the required ports for Team Foundation Server to operate correctly.

2.14   Unable to re-install because of service accounts.

When you uninstall Team Foundation Server and then try to reinstall on a
single server or on the application-tier of a dual-server deployment, you must
use the same service account that was used to install originally.

To resolve this issue

To determine the service account that was used, open Services Manager, sort
by “Log on as,” and then locate the services for Team Foundation Server at the
bottom of the list. Examine the “Log on as” value for the services at the
bottom; such as TFSServerScheduler. That value indicates the service account you
must specify during the re-installation.

2.15   Unable to install because of the Reporting Services application
pool.

Setup has detected a SQL Server 2005 Reporting Services IIS application pool
on this computer and cannot continue.

To resolve this issue

Before running setup again, remove the Reporting Services application pool by
opening Internet Information Services Manager, expanding the Application Pool
node, and then deleting the pools for Reporting Services.

2.16   Unable to install because of insufficient "Log on as a service"
permissions.

The service accounts must have the "Log on as a service" permission set to
Allow.

To resolve this issue

Verify that "Log on as a service" is allowed for both service accounts.

  1. On the Start menu, click Control Panel, click
    Administrative Tools, and then click Local Security Policy.
  2. Expand Security Settings, click Local Policies, and then click
    User Rights Assignments.
  3. In the details pane, locate and double-click Log on as a service.
  4. In Log on as a service Properties, locate the services you have
    specified for Team Foundation Server. For example, this guide uses the
    placeholders domain/tfsservice and domain/tfsreports for the service accounts.

2.17   Installation fails when the default Web site is configured to require
a secure channel (SSL), with error code: 28804 or 28805.

Team Foundation Server single- or dual-server (application tier) install
fails with error code 28804 or 28805. Further inspection of the installation
logs will indicate that the problem occurred with the CreateDS custom action,
and that the “operation you are attempting requires a secure connection
(HTTPS).” This is probably due to Report Server being automatically configured
to require SSL connections when an SSL certificate is required for the default
Web site. Team Foundation Server installation cannot automatically configure the
server for SSL-only connections. This is a post-install configuration operation.

To resolve this issue

For single server, open %ProgramFiles%Microsoft SQL ServerMSSQL.3Reporting
ServicesReportServerRsReportServer.config. Change the "SecureConnectionLevel"
value from “2” to “0.” On the Team Foundation Server installation error dialog
box, click Retry, or restart the installation.

For dual server,
click Cancel. Go to IIS manager and configure the default Web site so
that it does not require a secure channel (SSL) connection, and then re-run the
application tier installation.

2.18   TF53011 error when upgrading Team Foundation Server from trial to
workgroup edition.

After upgrading from the trial edition to the workgroup edition, trying to
connect to the server from Team Explorer causes a TF53011 error: "The Team
Foundation Server returned the following error: The request failed with HTTP
status 403: TF53011: domainuser is not a licensed user…". This error appears
because upgrading from trial to workgroup edition does not create the Licensed
Workgroup Users group.

To resolve this issue

After upgrading to workgroup edition, re-run the Team Foundation Server setup
(application tier installation or single server installation), in repair
mode.

2.19   Using different versions of SQL Server on a two server install may
cause setup to fail.

If you use different editions of SQL Server on the data tier and application
tier, some combinations (for example, SQL Standard on the application tier and
SQL Developer on the data tier) may cause setup failure.

To resolve this issue

Use the same edition of SQL on both the application tier and data tier
machines in a two server configuration.

2.20   Using a 64-bit operating system to run Team Foundation Server and SQL
Server 2005.

Team Foundation Server needs SQL Server 2005 (64-bit) installed on a 64-bit
operating system. If SQL Server 2005 (32-bit) is installed on a 64-bit operating
system, the System health check for the Team Foundation Server data tier setup
will fail.

To resolve this issue

Use SQL Server 2005 (64-bit) on a 64-bit operating system.

2.21   Reinstalling the Team Foundation Server application tier after
uninstalling and reinstalling the data tier causes an error.

Uninstalling and reinstalling the Team Foundation Server data tier does not
add the required registration stored procedure to the Team Foundation Server
Integration database, which causes the application tier installation to
fail.

To resolve this issue

Repairing the Team Foundation Server data tier installation will insert the
required stored procedures, allowing the application tier to install
successfully.

2.22   Final Installation Page for Team Foundation Server Proxy Contains
Misleading Information.

The Web page that appears after installing Team Foundation Server Proxy
contains incorrect information. In the XML example for configuring the proxy, an
extra space appears in the value for the Uri element of the Server node of the
proxy.config file, http://
TeamFoundationServerName:8080/VersionControl. The product name is also
incorrectly listed as Team Foundation Version Control Proxy.

To resolve this issue

When you open the
proxy.config file, you can copy the example, but be sure to remove the extra
space after http://. For more information about configuring the proxy, see "How
to: Enable Source Control Caching for Team Foundation Server Proxy" in the Team
Foundation Server Administrator's Guide.

3. Microsoft® .NET Framework 2.0

3.1   Installing Windows Server 2003, installing .NET Framework 2.0, and
then upgrading to Windows Server 2003 SP1 using a full CD breaks .NET Framework
2.0 applications.

Upgrading using a CD with the full Windows Server 2003 SP1 installation,
replaces the shared file mscoree.dll on a computer that has the .NET Framework
1.1 mscoree.dll file.

Any applications compiled against the .NET Framework 2.0 will not run after
the service pack is installed.

Note   This does not occur when updating Windows Server 2003 with just
the service pack. This is a problem when you upgrade with a CD that contains
Windows Server 2003 and Windows Server 2003 SP1 bundled together.

To resolve this issue

After you install the Service Pack, the .NET Framework must be repaired.

1.      In Control Panel, open Add or Remove Programs.

2.      Select Microsoft .NET Framework 2.0.

3.      Click Change/Remove.

4.      When the Change/Remove dialog box appears, click
Repair, and then click Next.

5.      If prompted to restart, restart the computer.

4. Microsoft® Office Primary Interop Assemblies

4.1  Installing the Required Primary Interop Assemblies

Certain Visual Studio features require the presence of the following primary
interop assemblies (PIAs):

  1. Microsoft Office Excel 2003†‡
  2. Microsoft Office Word 2003
  3. Microsoft Office Outlook 2003
  4. Microsoft Forms 2.0
  5. Microsoft Graph
  6. Smart Tag
  7. Microsoft Office Project 2003†‡

† Required for creating Microsoft Visual Studio Tools for the Microsoft
Office System projects. When you create an Office project, Visual Studio tries
to install any required PIAs that are not installed. If the PIAs were not set to
“Installed on first use” during Office installation, you might need the Office
installation media and administrative rights to install them. You can now either
create Excel, Word, and Outlook projects or manually install the PIAs (see in
the following section).

‡ Required for Microsoft Office integration with Visual Studio 2005 Team
Explorer.

To manually install the required Primary Interop
Assemblies (PIAs)

You can manually install the PIAs by following these instructions if you are
running a full edition of Office 2003. Follow similar steps for stand-alone
versions of Excel, Outlook and Word, but note that not all the PIAs are
available.

1.      In Control Panel, open Add or Remove Programs.

2.      Make sure that Change or Remove Programs is selected.

3.      Select Microsoft Office in the Currently installed
programs
list.

4.      Click Change.

5.      Select Add or Remove Features and then click Next.

6.      Select Choose advanced customization of applications and then
click Next.

7.      Expand Microsoft Office Excel, select the option for .NET
Programmability Support
, and then click Run from My Computer.

8.      Expand Microsoft Office Outlook, select the option for .NET
Programmability Support
, and then click Run from My Computer.

9.      Expand Microsoft Office Word, select the option for .NET
Programmability Support
, and then click Run from My Computer.

10.  Expand Office Tools, select the option for Microsoft Forms 2.0
.NET Programmability Support,
and then click Run from My
Computer
.

11.  Select the option for Smart Tag .NET Programmability Support and
then click Run from My Computer.

12.  Under Office Tools, expand Microsoft Graph, select the
option for .NET Programmability Support, and then click Run from My
Computer
.

13.  Click Update.

14.  Click OK.

15.  Select Microsoft Project in the list of programs installed and
then click Change.

16.  Select Add or Remove Features and then click Next.

17.  Expand Microsoft Office Project for Windows, select the option
for .NET Programmability Support, and then click Run from My
Computer
.

18.  Click Update.

19.  Click OK.

obtained from: http://msdn.microsoft.com/vstudio/teamsystem/tfsreadme.aspx

Jul 04

Create a self-signed, code-signing certificate

I've been mostly interested in self-signed certificates for other uses, but surely this provides a good idea of how to use the utility and you can mold it to your needs in the future. Here is the article:

Create a self-signed, code-signing certificate

You can use the following procedure to create a self-signed, code-signing
certificate that also creates and installs a private key. To perform this
procedure, use the Makecert.exe utility. Makecert.exe is available in the
Microsoft .NET Framework 2.0 Software Development Kit (SDK) (http://go.microsoft.com/fwlink/?LinkId=62598), which you can download from the Microsoft Web site.

Administrative credentials

To complete this procedure, you must be a member of the Administrators group
on the local computer.

To create a self-signed, code signing certificate that also creates and
installs a private key using a script

Example command:

makecert -r -pe -n "CN=CertForADFS" -b 01/01/2006 -e 01/01/2007 -eku
1.3.6.1.5.5.7.3.3 -ss my -sr localMachine -sky exchange -sp "Microsoft RSA
SChannel Cryptographic Provider" -sy 12
"CertForMe.cer"

Note:

Certificate expiration dates should be tracked to make sure that certificates
are replaced before they expire.

obtained from: http://technet2.microsoft.com/WindowsServer/en/Library/71977614-985a-4cce-8fcf-7b49d2e5a8951033.mspx?mfr=true

Jul 04

How to create a self-signed SSL certificate with IIS 6

I never ran into this issue with IIS as I usually install a Certificate Authority and do it that way, but I guess it might come in handy for personal websites and saving some money. Here are the details:

Create a self-signed SSL certificate with IIS 6.0 Resource Kit SelfSSL

The IIS 6.0 Resource Kit version 1.0 was released
5/30/2003. It contains a utility called SelfSSL.exe for instantly creating and
installing a self-signed testing certificate into IIS. The resource kit is
freely downloadable from the Microsoft website. Although the tool is intended
for IIS 6.0, it works just as well on IIS 5.1. It is so simple to use that no
instructions are required beyond the pointer to the download.

  • Download
    IIS 6.0 Resource Kit Tools
  • Install the resource kit (requires Windows Server 2003, Windows XP)
  • From the Windows Start Menu, go to the "ProgramsIIS ResourcesSelfSSL"
    folder and select "SelfSSL".
  • Instructions will be listed in a command prompt. Type "selfssl" to run the
    program.
  • Type "y" to confirm overriding/installing the certificate on the given site.
  • Test that it worked by visiting https://localhost/.

If you want hand-holding through these steps, read these instructions with
screenshots
by Jonathan Maltz.

Microsoft has also provided Microsoft
Internet Information Services 6.0 Resource Kit
the book for download
via their website in whole or chapter.

obtained from: http://www.somacon.com/p42.php

Load more