Date parsed: 07/04/2008 10:45:25
Date: Mon, 07 Apr 2008 10:45:25 GMT

Hello Gerry,

For your first question about oleview run in x64 system, the current design
of oleview is to enumerate the SysWow64 sub-keys as well as the real ones.
We can differentiate the two according to the OLEVIEW's outputs. If you
feel this design is not convenient, it is my pleasure to help send a wish
to the developer of oleview via internal channel.

For the second question about "the library not being registered" error
thrown from oleview when users right-click + view on "Microsoft Windows
Installer Object Library (ver 1.0)" in the list of TypeLibs:
Based on my tests on both x86 and x64 machines with oleview.exe from
Windows SDK 6.0A, I failed to reproduce the error because the typelib
detail is shown successfully on my side. However, I find a feedback about
oleview at:
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?Feedbac
kID=289440
The feedback says oleview hangs when select "view.." from the context menu,
and the application freeze. If your experience is not the same as it, I'd
suggest you submit a ticket in
https://connect.microsoft.com/VisualStudio
to report the problem. Developers of oleview may cooperate with you and try
to resolve the problem.

Regards,
Jialiang Ge (jialge@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Date parsed: 08/04/2008 06:15:23
Date: Tue, 08 Apr 2008 06:15:23 GMT

Hi Gerry,

I have verified the registry entries of
000C1092-0000-0000-C000-000000000046, and they are exactly the same as
yours.

The error 8002801d "Library Not Registered" literally indicates that there
is a problem with the registry information for this object. The registry
entry may be missing or contain incorrect information, or the user may not
have permission to read the registry entry. Would you check if the TypeLib
and CLSID entries in registry give proper read permissions to the user who
runs the oleview? To check the permission, you can right click on the key,
and select Permissions|Security. The CLSID entry of Microsoft Windows
Installer Object Library (ver1.0) is located at
HKEY_CLASSES_ROOT\CLSID\{000C101C-0000-0000-C000-000000000046}.

If the problem continues after you change the permissions for ClassID and
TypeLib, you can also use the ProcMon or RegMon utility to monitor registry
activity while you run the failing oleview. The ProcMon/RegMon log shows if
any attempts to read the registry fail. You can download ProcMon/RegMon
from the following position:
http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
http://technet.microsoft.com/en-us/sysinternals/bb896652.aspx
And refer to the blog article "Process Monitor - Hands-on Labs and Examples"
http://blogs.technet.com/softgrid/archive/2008/01/24/process-monitor-hands-o
n-labs-and-examples.aspx
We can start to log before we click on the Microsoft Windows Installer
Object Library entry in oleview, and ends logging when the error is thrown.

Regards,
Jialiang Ge (jialge@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

=================================================
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@microsoft.com.

This posting is provided "AS IS" with no warranties, and confers no rights.
=================================================

Date parsed: 10/04/2008 02:44:10
Date: Thu, 10 Apr 2008 02:44:10 GMT

Sorry, Gerry, I suddenly realize my previous test of x86 and x64
environment was conducted with an OLEVIEW currently available to Microsoft
internal only. This oleview.exe tool can read the 64-bit hive. I am
checking with the SDK team to see whether & when will they include this x64
version into the public SDK.

Regards,
Jialiang Ge (jialge@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

=================================================
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@microsoft.com.

This posting is provided "AS IS" with no warranties, and confers no rights.
=================================================

Date parsed: 10/04/2008 21:36:30
Date: Thu, 10 Apr 2008 20:36:30 +0100

Hi Jialiang Ge,

Please can you check the OLEVIEW you are using is the one from the 6.0A
SDK (not the "internal" one). I've tested it two machines, x86 and x64
and get the same problem. On Vista, the TypeLib keys are locked down anyway.

Jialiang Ge [MSFT] wrote:
> Hi Gerry,
>
> I have verified the registry entries of
> 000C1092-0000-0000-C000-000000000046, and they are exactly the same as
> yours.
>
> The error 8002801d "Library Not Registered" literally indicates that there
> is a problem with the registry information for this object. The registry
> entry may be missing or contain incorrect information, or the user may not
> have permission to read the registry entry. Would you check if the TypeLib
> and CLSID entries in registry give proper read permissions to the user who
> runs the oleview? To check the permission, you can right click on the key,
> and select Permissions|Security. The CLSID entry of Microsoft Windows
> Installer Object Library (ver1.0) is located at
> HKEY_CLASSES_ROOT\CLSID\{000C101C-0000-0000-C000-000000000046}.
>
> If the problem continues after you change the permissions for ClassID and
> TypeLib, you can also use the ProcMon or RegMon utility to monitor registry
> activity while you run the failing oleview. The ProcMon/RegMon log shows if
> any attempts to read the registry fail. You can download ProcMon/RegMon
> from the following position:
> http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
> http://technet.microsoft.com/en-us/sysinternals/bb896652.aspx
> And refer to the blog article "Process Monitor - Hands-on Labs and Examples"
> http://blogs.technet.com/softgrid/archive/2008/01/24/process-monitor-hands-o
> n-labs-and-examples.aspx
> We can start to log before we click on the Microsoft Windows Installer
> Object Library entry in oleview, and ends logging when the error is thrown.
>
> Regards,
> Jialiang Ge (jialge@online.microsoft.com, remove 'online.')
> Microsoft Online Community Support
>
> =================================================
> Delighting our customers is our #1 priority. We welcome your comments and
> suggestions about how we can improve the support we provide to you. Please
> feel free to let my manager know what you think of the level of service
> provided. You can send feedback directly to my manager at:
> msdnmg@microsoft.com.
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> =================================================
>


--
Gerry Hickman (London UK)

Date parsed: 11/04/2008 08:21:14
Date: Fri, 11 Apr 2008 08:21:14 GMT

Hello Gerry,

I've checked it with the oleview from the pulic SDK 6.0A in my x86 Vista
machine, and reproduce the error 8002801d "Library Not Registered".

I queried our internal product issue data base, and find an entry for this
problem. The error is due to the algorithm of oleview for user default
LCID. However, the resultion/fix was not described clearly in the entry. I
am asking the corresponding issue owner for more information, and will get
back to you soon. If you feel this problem is very critical to your
business, I'd suggest you contact Microsoft Product Support Service. Since
we've confirmed that this is an issue of Microsoft product, the support
incident will be free of charge. You can contact Microsoft Product Support
directly to discuss additional support options you may have available, by
contacting us at 1-(800)936-5800 or by choosing one of the options listed
at
http://support.microsoft.com/common/international.aspx?rdpath=fh;en-us;cntac
tms.

Regards,
Jialiang Ge (jialge@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

=================================================
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@microsoft.com.

This posting is provided "AS IS" with no warranties, and confers no rights.
=================================================

Date parsed: 16/04/2008 04:20:16
Date: Wed, 16 Apr 2008 04:20:16 GMT

Hello Gerry,

Sorry for my delayed response. I've got the confirmation from the Windows
SDK team as follows:

The fix of the LCID issue in oleview has not been included in the released
oleview tools yet. Oleview from both Windows Vista SDK and Windows 2008
Server SDK can reproduce the error 8002801d "Library Not Registered" when
users view "Microsoft Windows Installer Object Library (ver 1.0)". The SDK
will include the fix in the next release of standalone Windows SDK, and if
time permits, the SDK team also considers shipping it with Visual Studio
2008 SP1. A short-term workaround for the error is to open the msi.dll
(should be located in c:\windows\system32\msi.dll) with oleview -> File ->
View Typelib... Please have a try and let me know if it works for you.

Regarding the x64 version of oleview, the SDK team has not responded to
confirm the release date yet. Maybe they are busy with other higher
priority issues. I will continue striking them and inform you about the
latest confirmation from the SDK team.

I cannot share the internal version of x64 oleview with you directly due to
Microsoft policy, but I can update you as soon as it's released.

Regards,
Jialiang Ge (jialge@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

=================================================
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@microsoft.com.

This posting is provided "AS IS" with no warranties, and confers no rights.
=================================================

Date parsed: 17/04/2008 21:08:12
Date: Thu, 17 Apr 2008 20:08:12 +0100

Hi Jialiang Ge,

Thank you for taking the time to look into this for me and get some answers!

The work-around of opening the DLL directly is helpful.

The news on the lack of x64 support is disappointing. It _should_ be a
priority; x64 support for Windows development is now essential, and
VS2008 and SDK 6.0A are supposed to be the flagship development tools
for Vista and Windows 2008. The fact this tool looks in the wrong
registry hive implies a poor standard, and the fact Microsoft already
fixed these issues, but refuse to release the updated tool, is also
disappointing.

> Hello Gerry,
>
> Sorry for my delayed response. I've got the confirmation from the Windows
> SDK team as follows:
>
> The fix of the LCID issue in oleview has not been included in the released
> oleview tools yet. Oleview from both Windows Vista SDK and Windows 2008
> Server SDK can reproduce the error 8002801d "Library Not Registered" when
> users view "Microsoft Windows Installer Object Library (ver 1.0)". The SDK
> will include the fix in the next release of standalone Windows SDK, and if
> time permits, the SDK team also considers shipping it with Visual Studio
> 2008 SP1. A short-term workaround for the error is to open the msi.dll
> (should be located in c:\windows\system32\msi.dll) with oleview -> File ->
> View Typelib... Please have a try and let me know if it works for you.
>
> Regarding the x64 version of oleview, the SDK team has not responded to
> confirm the release date yet. Maybe they are busy with other higher
> priority issues. I will continue striking them and inform you about the
> latest confirmation from the SDK team.
>
> I cannot share the internal version of x64 oleview with you directly due to
> Microsoft policy, but I can update you as soon as it's released.
>
> Regards,
> Jialiang Ge (jialge@online.microsoft.com, remove 'online.')
> Microsoft Online Community Support
>
> =================================================
> Delighting our customers is our #1 priority. We welcome your comments and
> suggestions about how we can improve the support we provide to you. Please
> feel free to let my manager know what you think of the level of service
> provided. You can send feedback directly to my manager at:
> msdnmg@microsoft.com.
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> =================================================
>


--
Gerry Hickman (London UK)

Date parsed: 19/04/2008 22:20:59
Date: Sat, 19 Apr 2008 21:20:59 +0100

Nathan Mates wrote:

> Microsoft is taking some steps, but not a *lot* of steps, towards
> making x64 a first class member. In VS2005, x64 compilation required a
> a 'Pro' level of the software. Now, it "only" requires the 'standard'
> edition'. The express edition is 32-bit only. All according to
> http://www.microsoft.com/downloads/details.aspx?FamilyID=727bcfb0-b575-47ab-9fd8-4ee067bb3a37&DisplayLang=en
> If MS considered x64 support "essential," then they would have made it
> part of the Express Edition. Maybe in the next VS.

Thanks, but I think you're out of touch. Exchange 2007 will ONLY run on
x64, so OBVIOUSLY it's essential as all large corporations are running
Exchnage.

For new builds of Active Directory, SQL Server, Sharepoint and Exchange,
only a fool would specify x86. The express edition is only for beginners
so doesn't count. The professional platform is x64 hardware, x64 o/s and
x64 compiled applications using C++ and COM, hence my requirement for a
reliable DCOM/COM/Automation/TypeLib enumeration/premissions tool.

Here's a quote from Microsoft's website

"With a larger addressable space, the Exchange servers can utilize more
memory thereby reducing the required input/output per user (IOPS),
enabling the use of larger disks as well as low cost storage such as
SATA2 drives. Testing at Microsoft has shown an IOPS decrease of
approximately 70 percent with Exchange Server 2007 on 64-bit hardware."

--
Gerry Hickman (London UK)