DAO Installation Problem

[gpayne]

Originally Posted by gpayne

Thanks!

I was going to try to do the remove option but I thought I would wait to get some feedback. I will do an install with the delete option and let you know.

I just did a new install with the delete option. I got the same results. No need to bother Bryan on his vacation. It's not that big a deal. When he gets back you might ask him if the following scenario would or could cause the DAO problem.
1. I have Hoster 3.310 on my non-show compueter.
2. I have been importing bin files on that computer.
3. I then transferred them to the hard drive on my show computer which had Hoster 3.303 on it.
4. I deleted the songs.mdb and songs backup.mdb on the show computer.
5. I then started the show computer and Hoster 3.303 automatically rebuilt the database.
6. After doing this and playing two shows on the show computer, I tried to upgrade the show computer to Hoster Version 3.310.

This is when I started having the DAO installation problem.

This might be someting that effects it or not. I do have all!!!! windows xp and Office xp updates. They are current as of yesterday!

Thanks

gpayne

[admin]

Excellent facts for us to go on. We all want to get to the bottom of this. We are studying the Plextor drive models you have to see if there may be a wrong definition structure for them that might cause this.

The code we are using is new to us from a reputable vendor. All drives that are "claimed" to be supported have been "assumed" to already be proven. However, I'm beginning to question that.

The question yet to be determined is what is causing this and how to fix it.

[barrp]

Was there ever a solution for this? I'm having the same problem and running the same 760A drive, but this drive has not worked for a few months and I'm using an external drive to load cdg's. chemas-microsoft-com:office:office" />

Hoster 3.310 is also locking up while trying to read cdg's from my external drive that had worked with the old version.

This is the same computer that has been running Hoster for over a year with a new hard drive. I tried the 3.310 upgrade on the old drive before adding the new drive, and did not get the error message but Hoster did lock up trying to load cdg's.

[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?

[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