Runtime Installation problems on XP Service Pack 2 Machines

Help!!!

I have my runtime application installed on many network workstations that
are running XP Operating System, Service Pack 1. I have them:

1. log in as the network and workstation administrator,
2. install my runtime app which I created with the packaging wizard,
3. run the Art2002Sp3-kb834693-client-enu.exe patch,
4. and then log in as the workstation user, who has your basic limited user
rights to the workstation and network.
5. Click Start, Programs, MyApp.

It runs great! Full functionality! No problems!

The problem starts with workstations that are running XP Operating System,
Service Pack TWO (with all patches up to date). After following steps 1-4,
they click on Start, Programs, and MyApp does not show up!

I've tried putting the shortcut on all desktops when logged in as
administrator, then logging in as the user and trying to launch MyApp, but I
get very wacky results with this. Errors all over the place when I try to
do anything.

I've tried logging in as the user and trying to install my setup.exe created
by the packaging wizard, but of course since the user doesn't have
administrative rights to the computer, it bombs out.

I've tried giving the user administrative rights and installing. It
installs, but again, as soon as I try to do the most basic tasks, like run a
query, it starts erroring out. (Again, the same basic tasks that are
functioning perfectly on the machines with Service Pack 1).

Thank you in advance for any help,
K. Hart

I understand that this must be very frustrating for you, but "errors all
over the place" and "it bombs out" don't give us much to go on, either.

Could you be more specific as to exactly what you're doing, and what the
error messages you receive are?


"Karen Hart" wrote in message
k.net...
Help!!!

I have my runtime application installed on many network workstations that
are running XP Operating System, Service Pack 1. I have them:

1. log in as the network and workstation administrator,
2. install my runtime app which I created with the packaging wizard,
3. run the Art2002Sp3-kb834693-client-enu.exe patch,
4. and then log in as the workstation user, who has your basic limited
user
rights to the workstation and network.
5. Click Start, Programs, MyApp.

It runs great! Full functionality! No problems!

The problem starts with workstations that are running XP Operating System,
Service Pack TWO (with all patches up to date). After following steps
1-4,
they click on Start, Programs, and MyApp does not show up!

I've tried putting the shortcut on all desktops when logged in as
administrator, then logging in as the user and trying to launch MyApp, but
I
get very wacky results with this. Errors all over the place when I try to
do anything.

I've tried logging in as the user and trying to install my setup.exe
created
by the packaging wizard, but of course since the user doesn't have
administrative rights to the computer, it bombs out.

I've tried giving the user administrative rights and installing. It
installs, but again, as soon as I try to do the most basic tasks, like run
a
query, it starts erroring out. (Again, the same basic tasks that are
functioning perfectly on the machines with Service Pack 1).

Thank you in advance for any help,
K. Hart

Sorry, why don't we just start with the most obvious:
When I install as the machine's administrator, then log in as the user,
click on Start, Programs...MyApp does not even show up.


"MacDermott" wrote in message
...
I understand that this must be very frustrating for you, but "errors all
over the place" and "it bombs out" don't give us much to go on, either.

Could you be more specific as to exactly what you're doing, and what the
error messages you receive are?


"Karen Hart" wrote in message
k.net...
Help!!!

I have my runtime application installed on many network workstations that
are running XP Operating System, Service Pack 1. I have them:

1. log in as the network and workstation administrator,
2. install my runtime app which I created with the packaging wizard,
3. run the Art2002Sp3-kb834693-client-enu.exe patch,
4. and then log in as the workstation user, who has your basic limited
user
rights to the workstation and network.
5. Click Start, Programs, MyApp.

It runs great! Full functionality! No problems!

The problem starts with workstations that are running XP Operating
System,
Service Pack TWO (with all patches up to date). After following steps
1-4,
they click on Start, Programs, and MyApp does not show up!

I've tried putting the shortcut on all desktops when logged in as
administrator, then logging in as the user and trying to launch MyApp,
but
I
get very wacky results with this. Errors all over the place when I try
to
do anything.

I've tried logging in as the user and trying to install my setup.exe
created
by the packaging wizard, but of course since the user doesn't have
administrative rights to the computer, it bombs out.

I've tried giving the user administrative rights and installing. It
installs, but again, as soon as I try to do the most basic tasks, like
run
a
query, it starts erroring out. (Again, the same basic tasks that are
functioning perfectly on the machines with Service Pack 1).

Thank you in advance for any help,
K. Hart

OK...does your package specify that the install is for all users or just the
current user? If you package is for current user, and you install it under
the machine admin account, it wouldn't be available for all users.

--
Paul Overway
Logico Solutions
http://www.logico-solutions.com


"Karen Hart" wrote in message
nk.net...
Sorry, why don't we just start with the most obvious:
When I install as the machine's administrator, then log in as the user,
click on Start, Programs...MyApp does not even show up.


"MacDermott" wrote in message
...
I understand that this must be very frustrating for you, but "errors all
over the place" and "it bombs out" don't give us much to go on, either.

Could you be more specific as to exactly what you're doing, and what the
error messages you receive are?


"Karen Hart" wrote in message
k.net...
Help!!!

I have my runtime application installed on many network workstations
that
are running XP Operating System, Service Pack 1. I have them:

1. log in as the network and workstation administrator,
2. install my runtime app which I created with the packaging wizard,
3. run the Art2002Sp3-kb834693-client-enu.exe patch,
4. and then log in as the workstation user, who has your basic limited
user
rights to the workstation and network.
5. Click Start, Programs, MyApp.

It runs great! Full functionality! No problems!

The problem starts with workstations that are running XP Operating
System,
Service Pack TWO (with all patches up to date). After following steps
1-4,
they click on Start, Programs, and MyApp does not show up!

I've tried putting the shortcut on all desktops when logged in as
administrator, then logging in as the user and trying to launch MyApp,
but
I
get very wacky results with this. Errors all over the place when I try
to
do anything.

I've tried logging in as the user and trying to install my setup.exe
created
by the packaging wizard, but of course since the user doesn't have
administrative rights to the computer, it bombs out.

I've tried giving the user administrative rights and installing. It
installs, but again, as soon as I try to do the most basic tasks, like
run
a
query, it starts erroring out. (Again, the same basic tasks that are
functioning perfectly on the machines with Service Pack 1).

Thank you in advance for any help,
K. Hart

What do you mean by "My package"? My developer packaging wizard does not
specify anything. As far as I remember, when creating a package using the
packaging wizard, this question is never asked.

If you mean does the workstation ask, it does not ask when installing,
either.


"Paul Overway" wrote in message
...
OK...does your package specify that the install is for all users or just
the current user? If you package is for current user, and you install it
under the machine admin account, it wouldn't be available for all users.

--
Paul Overway
Logico Solutions
http://www.logico-solutions.com


"Karen Hart" wrote in message
nk.net...
Sorry, why don't we just start with the most obvious:
When I install as the machine's administrator, then log in as the user,
click on Start, Programs...MyApp does not even show up.


"MacDermott" wrote in message
...
I understand that this must be very frustrating for you, but "errors all
over the place" and "it bombs out" don't give us much to go on, either.

Could you be more specific as to exactly what you're doing, and what the
error messages you receive are?


"Karen Hart" wrote in message
k.net...
Help!!!

I have my runtime application installed on many network workstations
that
are running XP Operating System, Service Pack 1. I have them:

1. log in as the network and workstation administrator,
2. install my runtime app which I created with the packaging wizard,
3. run the Art2002Sp3-kb834693-client-enu.exe patch,
4. and then log in as the workstation user, who has your basic limited
user
rights to the workstation and network.
5. Click Start, Programs, MyApp.

It runs great! Full functionality! No problems!

The problem starts with workstations that are running XP Operating
System,
Service Pack TWO (with all patches up to date). After following steps
1-4,
they click on Start, Programs, and MyApp does not show up!

I've tried putting the shortcut on all desktops when logged in as
administrator, then logging in as the user and trying to launch MyApp,
but
I
get very wacky results with this. Errors all over the place when I try
to
do anything.

I've tried logging in as the user and trying to install my setup.exe
created
by the packaging wizard, but of course since the user doesn't have
administrative rights to the computer, it bombs out.

I've tried giving the user administrative rights and installing. It
installs, but again, as soon as I try to do the most basic tasks, like
run
a
query, it starts erroring out. (Again, the same basic tasks that are
functioning perfectly on the machines with Service Pack 1).

Thank you in advance for any help,
K. Hart

If I remember correctly, the 2002 PDW ALWAYS installs shortcuts under the
current user. That is why you're not seeing shortcuts for other accounts.

FWIW..if you're really serious about distributing an Access app, you should
look into other options for installer technology. The shortcoming you've
encountered is just one of many.

--
Paul Overway
Logico Solutions
http://www.logico-solutions.com


"Karen Hart" wrote in message
nk.net...
What do you mean by "My package"? My developer packaging wizard does not
specify anything. As far as I remember, when creating a package using the
packaging wizard, this question is never asked.

If you mean does the workstation ask, it does not ask when installing,
either.


"Paul Overway" wrote in message
...
OK...does your package specify that the install is for all users or just
the current user? If you package is for current user, and you install it
under the machine admin account, it wouldn't be available for all users.

--
Paul Overway
Logico Solutions
http://www.logico-solutions.com


"Karen Hart" wrote in message
nk.net...
Sorry, why don't we just start with the most obvious:
When I install as the machine's administrator, then log in as the user,
click on Start, Programs...MyApp does not even show up.


"MacDermott" wrote in message
...
I understand that this must be very frustrating for you, but "errors all
over the place" and "it bombs out" don't give us much to go on, either.

Could you be more specific as to exactly what you're doing, and what
the
error messages you receive are?


"Karen Hart" wrote in message
k.net...
Help!!!

I have my runtime application installed on many network workstations
that
are running XP Operating System, Service Pack 1. I have them:

1. log in as the network and workstation administrator,
2. install my runtime app which I created with the packaging wizard,
3. run the Art2002Sp3-kb834693-client-enu.exe patch,
4. and then log in as the workstation user, who has your basic limited
user
rights to the workstation and network.
5. Click Start, Programs, MyApp.

It runs great! Full functionality! No problems!

The problem starts with workstations that are running XP Operating
System,
Service Pack TWO (with all patches up to date). After following steps
1-4,
they click on Start, Programs, and MyApp does not show up!

I've tried putting the shortcut on all desktops when logged in as
administrator, then logging in as the user and trying to launch MyApp,
but
I
get very wacky results with this. Errors all over the place when I
try to
do anything.

I've tried logging in as the user and trying to install my setup.exe
created
by the packaging wizard, but of course since the user doesn't have
administrative rights to the computer, it bombs out.

I've tried giving the user administrative rights and installing. It
installs, but again, as soon as I try to do the most basic tasks, like
run
a
query, it starts erroring out. (Again, the same basic tasks that are
functioning perfectly on the machines with Service Pack 1).

Thank you in advance for any help,
K. Hart

Does anyone else care to help me? Like an MVP?
Thank you,
Karen

"Paul Overway" wrote in message
...
If I remember correctly, the 2002 PDW ALWAYS installs shortcuts under the
current user. That is why you're not seeing shortcuts for other accounts.

FWIW..if you're really serious about distributing an Access app, you
should look into other options for installer technology. The shortcoming
you've encountered is just one of many.

--
Paul Overway
Logico Solutions
http://www.logico-solutions.com


"Karen Hart" wrote in message
nk.net...
What do you mean by "My package"? My developer packaging wizard does not
specify anything. As far as I remember, when creating a package using
the packaging wizard, this question is never asked.

If you mean does the workstation ask, it does not ask when installing,
either.


"Paul Overway" wrote in message
...
OK...does your package specify that the install is for all users or just
the current user? If you package is for current user, and you install
it under the machine admin account, it wouldn't be available for all
users.

--
Paul Overway
Logico Solutions
http://www.logico-solutions.com


"Karen Hart" wrote in message
nk.net...
Sorry, why don't we just start with the most obvious:
When I install as the machine's administrator, then log in as the user,
click on Start, Programs...MyApp does not even show up.


"MacDermott" wrote in message
...
I understand that this must be very frustrating for you, but "errors
all
over the place" and "it bombs out" don't give us much to go on,
either.

Could you be more specific as to exactly what you're doing, and what
the
error messages you receive are?


"Karen Hart" wrote in message
k.net...
Help!!!

I have my runtime application installed on many network workstations
that
are running XP Operating System, Service Pack 1. I have them:

1. log in as the network and workstation administrator,
2. install my runtime app which I created with the packaging wizard,
3. run the Art2002Sp3-kb834693-client-enu.exe patch,
4. and then log in as the workstation user, who has your basic
limited
user
rights to the workstation and network.
5. Click Start, Programs, MyApp.

It runs great! Full functionality! No problems!

The problem starts with workstations that are running XP Operating
System,
Service Pack TWO (with all patches up to date). After following
steps
1-4,
they click on Start, Programs, and MyApp does not show up!

I've tried putting the shortcut on all desktops when logged in as
administrator, then logging in as the user and trying to launch
MyApp, but
I
get very wacky results with this. Errors all over the place when I
try to
do anything.

I've tried logging in as the user and trying to install my setup.exe
created
by the packaging wizard, but of course since the user doesn't have
administrative rights to the computer, it bombs out.

I've tried giving the user administrative rights and installing. It
installs, but again, as soon as I try to do the most basic tasks,
like run
a
query, it starts erroring out. (Again, the same basic tasks that are
functioning perfectly on the machines with Service Pack 1).

Thank you in advance for any help,
K. Hart

Karen Hart wrote:
Does anyone else care to help me? Like an MVP?
Thank you,
Karen

I believe you have your answer. Some install programs are not "intelligent"
enough to properly handle the policies on an NT, 2000, or XP operating
system and thus have to be installed "as the user who will run it". The PDW
is one such installer.

If the user who needs to run the program doesn't have sufficient authorities
to install programs they will have to be granted those permissions long
enough for you to do the install (logged on as them) and then those
permissions can be changed back afterwards.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

Dear Karen:

Your comment: "Does anyone else care to help me? Like an MVP?" might be
interpreted as a critique of the help you've been offered to this point. Was
that your intention? You don't have to be designated an "MVP" to be an
Access expert, and many knowledgeable and helpful posters here aren't MVPs!


Earlier in the thread, you were asked to describe the error messages you
were getting, but you haven't given us the error numbers or error messages.
To be precise: you mentioned one problem, which wasn't really an error but a
setup issue. Careful descriptions of the errors and/or text of the error
messages and/or error numbers would be helpful!

I'm curious: you say that when you gave the user "Admin" permissions, the
installation seemed to work, then you say that when you tried to run a
query, "it starts erroring out.". Can we assume, then, that the
*installation* problem is solved using this process? Could you describe
exactly what is happening when "it starts erroring out."?

Fred Boer (Definitely NOT an expert!)


"Karen Hart" wrote in message
ink.net...
Does anyone else care to help me? Like an MVP?
Thank you,
Karen

"Paul Overway" wrote in message
...
If I remember correctly, the 2002 PDW ALWAYS installs shortcuts under the
current user. That is why you're not seeing shortcuts for other
accounts.

FWIW..if you're really serious about distributing an Access app, you
should look into other options for installer technology. The shortcoming
you've encountered is just one of many.

--
Paul Overway
Logico Solutions
http://www.logico-solutions.com


"Karen Hart" wrote in message
nk.net...
What do you mean by "My package"? My developer packaging wizard does not
specify anything. As far as I remember, when creating a package using
the packaging wizard, this question is never asked.

If you mean does the workstation ask, it does not ask when installing,
either.


"Paul Overway" wrote in message
...
OK...does your package specify that the install is for all users or
just the current user? If you package is for current user, and you
install it under the machine admin account, it wouldn't be available
for all users.

--
Paul Overway
Logico Solutions
http://www.logico-solutions.com


"Karen Hart" wrote in message
nk.net...
Sorry, why don't we just start with the most obvious:
When I install as the machine's administrator, then log in as the
user, click on Start, Programs...MyApp does not even show up.


"MacDermott" wrote in message
...
I understand that this must be very frustrating for you, but "errors
all
over the place" and "it bombs out" don't give us much to go on,
either.

Could you be more specific as to exactly what you're doing, and what
the
error messages you receive are?


"Karen Hart" wrote in message
k.net...
Help!!!

I have my runtime application installed on many network workstations
that
are running XP Operating System, Service Pack 1. I have them:

1. log in as the network and workstation administrator,
2. install my runtime app which I created with the packaging wizard,
3. run the Art2002Sp3-kb834693-client-enu.exe patch,
4. and then log in as the workstation user, who has your basic
limited
user
rights to the workstation and network.
5. Click Start, Programs, MyApp.

It runs great! Full functionality! No problems!

The problem starts with workstations that are running XP Operating
System,
Service Pack TWO (with all patches up to date). After following
steps
1-4,
they click on Start, Programs, and MyApp does not show up!

I've tried putting the shortcut on all desktops when logged in as
administrator, then logging in as the user and trying to launch
MyApp, but
I
get very wacky results with this. Errors all over the place when I
try to
do anything.

I've tried logging in as the user and trying to install my setup.exe
created
by the packaging wizard, but of course since the user doesn't have
administrative rights to the computer, it bombs out.

I've tried giving the user administrative rights and installing. It
installs, but again, as soon as I try to do the most basic tasks,
like run
a
query, it starts erroring out. (Again, the same basic tasks that
are
functioning perfectly on the machines with Service Pack 1).

Thank you in advance for any help,
K. Hart

Dear Rick:

PMFJI, but I belive the OP mentioned that she tried granting the user
"Admin" permissions and then reset the permissions earlier in the thread. If
I interpret her correctly, in that situation the setup process worked
correctly, but she still had errors. Could it be something as simple as the
references being changed somehow on the machines with Service Pack 2?

Of course, more specifics about the errors would help!

Fred Boer


"Rick Brandt" wrote in message
...
Karen Hart wrote:
Does anyone else care to help me? Like an MVP?
Thank you,
Karen

I believe you have your answer. Some install programs are not
"intelligent"
enough to properly handle the policies on an NT, 2000, or XP operating
system and thus have to be installed "as the user who will run it". The
PDW
is one such installer.

If the user who needs to run the program doesn't have sufficient
authorities
to install programs they will have to be granted those permissions long
enough for you to do the install (logged on as them) and then those
permissions can be changed back afterwards.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com