Errors 1904 followed by 101

  • Thread starter Thread starter Bill-R
  • Start date Start date
B

Bill-R

Back when MSAS first came out, I had an Error 1904 on installation and an
error 101 when I attempted to run MSAS on one of the five installations that
I did. Other people also had the error and there was a lot of discussion
and suggestions in the newsgroup.

I tried ALL the suggested solutions to get MSAS to install on the computer.
With no luck. I eventually gave up and uninstalled MSAS including the files
the uninstall program misses.

I had hoped that build 509 would fix the problem. It does not.

The initial installation and upgrade worked on the other four systems.

Is there a way of submitting a real "bug/issue report" to the developers on
this problem with backup data and logs?

Bill Rankin
 
The known issues section of the help in build .509 has the standard
prescription for what do do about 101 errors.

Can you verify that doing a change, update, still doesn't fix this on this
particular machine?

The level of interaction you're looking for just isn't possible with the
public beta. You can bet that given the number of folks out here reporting
these errors, they are not having trouble replicating them.
 
I installed MSAS on 10 machines and I have the same
problem on one machine. I tried everything I could but I
have always the same problem as discribed from Bill-R.
See also my mail from the same day at 12:02 for more
information.
Daniel
 
Bill,

I do not know what you mean by verify.

I tried to install build 509 and got exactly the same results I got with
501. The attempt to update also failed. The 101 error is not really the
problem. The real problem is that MSAS never completes the install. During
installation (and Update) I get the following error:

Error 1904 Module C:\Windows\System 32\hashlib.dll failed to register.
HResult - 2147220473.
Contact your support personnel.

That is, all install attempts fail and an attempt to use MSAS results in the
expected 101. This was on the system with 501 uninstalled. I tried several
accounts on this system.

I am of two opinions (that means I have no real evidence):

1. that the problem involves the configuration of options of the two active
administrator-level user accounts on this system (not counting the
administrator account). The argument against this opinion is I have MSAS
installed on a different system with three user accounts and do not have a
problem.

2. that the uninstall program has not removed something that is blocking
the reinstall. I uninstalled, rebooted, then removed all the MSAS files
that uninstall did not remove. That did not help, but there may be more
files I missed.

Hopefully this issue is being worked,
Bill Rankin
 
Bill--it isn't clear from your message whether you tried the update route,
rather than remove and reinstall.

However, rather than mess with this further, I'd recommend the following:

Send an email to (e-mail address removed)

Jeff Dillon is looking into the 103/110 errors, and is interested in the
errors.log files from such systems. I'm not sure he wants those files
immediately, but if your file is small, you might zip it up and add it to
the email.
 
Yes, I tried update on a partial installation and it failed with a 1904
error without completing the update. Essentially it acted the same for both
an install and an update. It failed to install.

However, I went back and looked at the Windows\System 32 folder and the
hashlib.dll file was still there from an earlier install I attempted on 20
Mar. I deleted it and tried again. This time I got a good install for one
user.

Now I am only getting the 101 error for the other user on the system. Isn't
this a known error for computers with multiple users?

Bill Rankin
 
That's useful information--thanks. Surely the installer should be able to
replace that file, rather than just giving up in disgust.

I'd go ahead and send email, mentioning that you only get the error in the
multi-user context. I don't know the breadth of what Jeff Dillon is looking
for.
 
Bill,

My only guess is that the installation is configured not to replace existing
files. For your info, there are at least four system32 files that are not
uninstalled: GCCollection.dll, gcTypLibA.tbl, gcUnCompress.dll and
hashlib.dll.

I sent Jeff a more coherent version of the Issue and the errors.log file as
you suggested.

Thanks
Bill
 
Thanks. There are enough installer issues seen that I hope a thorough rev
is happening in that area of the product.
 
Bill,

Build 1.0.614 does not correct the 1904 error. The message is "Error 1904
Module C:/Windows/.../hashlib.dll failed to register. HResult 2147220473"

It looks as if a rev for the installer area did not happen.

Bill-R
 
Have you tried the current 101 fix?:
--------------------------------------
We have a possible workaround in place for the 101 error. Please test this
and provide feedback on the following steps:

For Windows XP Professional:
To change the setting on Windows XP Professional, open "Local Security
Policy" in Administrative Tools, or run secpol.msc. You need to be an admin
to use this tool. In the left pane, browse to Security Settings \ Local
Policies \ Security Options. The policy name is "System objects: Default
owner for objects created by members of the Administrators group". The
allowable settings are "Administrators group" or "Object creator". Change it
to "Administrators group." After that change has been made, please refresh
the policy by typing: "gpupdate /force" from a command prompt.

For Windows XP Home Edition:

IMPORTANT: This article contains information about modifying the registry.
Before you modify the registry, make sure to back it up and make sure that
you understand how to restore the registry if a problem occurs. For
information about how to back up, restore, and edit the registry, click the
following article number to view the article in the Microsoft Knowledge
Base:

256986 Description of the Microsoft Windows Registry
The "Local Security Policy" snap-in is not available on Windows XP Home
Edition. To change the setting on XP Home, you need to modify the Registry
directly. Please back up your registry in case you need to restore it. If
you do not feel comfortable doing this, do not try this workaround.

In Regedit, navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa. Find the value
called "nodefaultadminowner". The supported values are "0" for
"Administrators group", or "1" for "Object creator". Set the value to 0.

Please provide feedback if this is working.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security

--
 
Bill,

Yes, I tried to try it. I changed the security policy as soon as I saw the
suggested fix but MSAS was not installed.

I had uninstalled MSAS and other applications in an unsuccessful attempt to
fix NAV 2005 which would not install over NAV 2004 because of an internal
error. When build 614 came out I thought that this was my chance to try out
the MSAS fix. Unfortunately I got the 1904 error when I tried to install
it, so I never got as far as the 101. I work out of town so I will have to
wait until next weekend to try again with an older build of MSAS.

The result is that I have neither NAV nor MSAS working, and there is a bug
in Spybot 1.4 Resident Tea-Timer. This is just not my week.

Bill-R

Bill Sanderson said:
Have you tried the current 101 fix?:
--------------------------------------
We have a possible workaround in place for the 101 error. Please test this
and provide feedback on the following steps:

For Windows XP Professional:
To change the setting on Windows XP Professional, open "Local Security
Policy" in Administrative Tools, or run secpol.msc. You need to be an
admin
to use this tool. In the left pane, browse to Security Settings \ Local
Policies \ Security Options. The policy name is "System objects: Default
owner for objects created by members of the Administrators group". The
allowable settings are "Administrators group" or "Object creator". Change
it
to "Administrators group." After that change has been made, please refresh
the policy by typing: "gpupdate /force" from a command prompt.

For Windows XP Home Edition:

IMPORTANT: This article contains information about modifying the registry.
Before you modify the registry, make sure to back it up and make sure that
you understand how to restore the registry if a problem occurs. For
information about how to back up, restore, and edit the registry, click
the
following article number to view the article in the Microsoft Knowledge
Base:

256986 Description of the Microsoft Windows Registry
The "Local Security Policy" snap-in is not available on Windows XP Home
Edition. To change the setting on XP Home, you need to modify the Registry
directly. Please back up your registry in case you need to restore it. If
you do not feel comfortable doing this, do not try this workaround.

In Regedit, navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa. Find the value
called "nodefaultadminowner". The supported values are "0" for
"Administrators group", or "1" for "Object creator". Set the value to 0.

Please provide feedback if this is working.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security

--

Bill-R said:
Bill,

Build 1.0.614 does not correct the 1904 error. The message is "Error
1904
Module C:/Windows/.../hashlib.dll failed to register. HResult 2147220473"

It looks as if a rev for the installer area did not happen.

Bill-R
Click to expand...
Click to expand...
 
Bill-R said:
Bill,

Yes, I tried to try it. I changed the security policy as soon as I saw
the suggested fix but MSAS was not installed.

I had uninstalled MSAS and other applications in an unsuccessful attempt
to fix NAV 2005 which would not install over NAV 2004 because of an
internal error. When build 614 came out I thought that this was my chance
to try out the MSAS fix. Unfortunately I got the 1904 error when I tried
to install it, so I never got as far as the 101. I work out of town so I
will have to wait until next weekend to try again with an older build of
MSAS.

The result is that I have neither NAV nor MSAS working, and there is a bug
in Spybot 1.4 Resident Tea-Timer. This is just not my week.

Bill-R
Click to expand...

Indeed--not a good week. My own experience with difficulties with NAV isn't
pretty--I've always been able to work them out using Norton's tools and KB
articles, but the process has never been confidence-inspiring. Tea-timer
may be worth avoiding until all else is working. My bias will show here,
but I'd like to see all the NAV removed (via their removal tools), and then
see whether Microsoft Antispyware will install and run cleanly, then
reinstall NAV 2005. I've got NAV2005 and Microsoft Antispyware running on a
number of machines, ditto NAV2004, and the 2005 machines are upgrades over
2004, by and large--so there's nothing inherent in the combinations of
things you mention that is bad. I don't have tea-timer running on any of
those machines, though, nor have I brough those machines up to 614 yet.
 
Back
Top