DAO Installation Problem

[barrp]

I removed 3.310 and installed 3.303 and everything appears to work again. I still like to see a solution for 3.310 so I can upgrade in the future.

[ddouglass]

Admin - I think I have found the problem. This is from a MS Knowledge Base Article #916903

Symptom:
You receive the following error message on the client computer when the package is installing:
Error 1706. No valid source could be found for product Product Name. The Windows installer cannot continue.

Cause:
These problems occur because the Windows Installer packages do not have the ALLUSERS property value preset when the packages are created. This causes Windows Installer to set the value to "NULL." When you deploy a package by using SMS 2003, the installation runs under the SYSTEM context. The ALLUSERS property value must be defined if Windows Installer is trying to install as a user who differs from the locally logged-on user. Additionally, when the ALLUSERS property value is set to "NULL," the package performs a "per user installation," and no registry key entry is written to following registry subkey: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall

Resolution:
To resolve this problem, type Name.msi /SwitchesALLUSERS=2 in the Command line box. For example, you can type the following command: install_flash_player_active_x.msi ALLUSERS=2
This transfers the ALLUSERS property to the Setup phase, and the correct data is written to the registry entry key.

Note You cannot use the ALLUSERS property together with the /passive command-line switch.

What this is saying, I believe is that when you scripted for the Jet Engine install the ALLUSERS property was not set......maybe?

GPayne and barrp, when you are installing Hoster are you doing it as an administrator of the computer? If not then try that.

Otherwise, I hope I have found the lead we need to get this one fixed. It is very baffling.

[barrp]

Originally Posted by ddouglass

GPayne and barrp, when you are installing Hoster are you doing it as an administrator of the computer? If not then try that.

Yes, the administrator account is the only one I set up on my system. This is a new hard drive and every thing has been loaded from scratch. One thing I just noticed is that there is another account that does not show on the main start up screen, but under user accounts there is this account:

ASP.N Machine A...
Limited Account
Password Protected

What the heck is it that?

[ddouglass]

ASP.Net - Account used for running the ASP.NET worker process (aspnet_wp.exe) This so you can use those webpages that use ASP (interactive script processing) such as your Store Account for MTU.

You should have a Guest account (disabled) and a Support account (disabled) too.

"I'm having the same problem and running the same 760A drive, but this drive has not worked for a few months" Are sure it is a 760A because they just came out with that model about amonth or so ago?

[barrp]

Originally Posted by ddouglass

ASP.Net - Account used for running the ASP.NET worker process (aspnet_wp.exe) This so you can use those webpages that use ASP (interactive script processing) such as your Store Account for MTU.

You should have a Guest account (disabled) and a Support account (disabled) too.

"I'm having the same problem and running the same 760A drive, but this drive has not worked for a few months" Are sure it is a 760A because they just came out with that model about amonth or so ago?

You are correct it's the 716.

Can I delete the asp.net account? I don't have a support account. I'd like it to just open up, bypassing the main screen.

[gpayne]

Originally Posted by ddouglass

Admin - I think I have found the problem. This is from a MS Knowledge Base Article #916903

Symptom:
You receive the following error message on the client computer when the package is installing:
Error 1706. No valid source could be found for product Product Name. The Windows installer cannot continue.

Cause:
These problems occur because the Windows Installer packages do not have the ALLUSERS property value preset when the packages are created. This causes Windows Installer to set the value to "NULL." When you deploy a package by using SMS 2003, the installation runs under the SYSTEM context. The ALLUSERS property value must be defined if Windows Installer is trying to install as a user who differs from the locally logged-on user. Additionally, when the ALLUSERS property value is set to "NULL," the package performs a "per user installation," and no registry key entry is written to following registry subkey: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall

Resolution:
To resolve this problem, type Name.msi /SwitchesALLUSERS=2 in the Command line box. For example, you can type the following command: install_flash_player_active_x.msi ALLUSERS=2
This transfers the ALLUSERS property to the Setup phase, and the correct data is written to the registry entry key.

Note You cannot use the ALLUSERS property together with the /passive command-line switch.

What this is saying, I believe is that when you scripted for the Jet Engine install the ALLUSERS property was not set......maybe?

GPayne and barrp, when you are installing Hoster are you doing it as an administrator of the computer? If not then try that.

Otherwise, I hope I have found the lead we need to get this one fixed. It is very baffling.

Dale, my DAO promblem got fixed when I re-installed XP pro.

gpayne

[Beavis]

Originally Posted by gpayne

Dale, my DAO promblem got fixed when I re-installed XP pro.

gpayne

i always say that, when you cant figure out how to fix a problem with hoster, reformat ! its a lot quicker than waiting weeks for a glimmer of hope

[ddouglass]

Originally Posted by Beavis

i always say that, when you cant figure out how to fix a problem with hoster, reformat ! its a lot quicker than waiting weeks for a glimmer of hope

That depends on how much you have on the computer. Starting over can be a real pain if you have a lot of older programs and don't remeber where you put the @#$%^ disks!

Gary glad you got your problem solved and sorry it had to come to a reload.