Application not launching in 64 bit
I installed Avaya IP Agent on 64 bit machine.This is a 32 bit application and is working fine on 32 bit windows 7.But on 64 bit windows 7, the application ipagent.exe is just running in task manager for few seconds and closing.
On 64 bit if we launch as "runasadmin" it is working.But when I applied any shims it is not working(RunAsInvoker --> not working, RunAsAdmin/HIghest --> is creating new UAC prompt even it is not there previously..)
I gave permissions to its program files to everyone but no use.
5 Comments
[ + ] Show comments
-
THe application is workign if we run the exe with "runasadmin".... But we need to deliver the app to normal users who don't have admin rights..How to achieve this as shims from ACT are not working. - ur00361883 8 years ago
-
Have you tried Procmon to see why it is failing? Please note my answer regarding that permissions may need to be applied to control other services, this cannot be achieved with shims... - Pressanykey 8 years ago
-
Tried... but no use. - ur00361883 8 years ago
-
If you can get it to run as Admin then it must be something with permissions... Normally Procmon is your only real help... - Pressanykey 8 years ago
-
The app is working with user mode on 32 bit with no issues but not with 64 bit.It is working if we run the app in admin mode in 64 bit. - ur00361883 8 years ago
Answers (5)
Please log in to answer
Posted by:
anonymous_9363
8 years ago
You don't seem to be listening.
No-one's here has the faintest clue what this app is trying to do on your 64-bit implementation. How could they?
Run ProcMon, filter out the junk you don't want to see, like your a/v process, Windows Search, etc., then start the app. I can guarantee you'll see either 'NAME NOT FOUND', 'PATH NOT FOUND' or 'ACCESS DENIED'.
No-one's here has the faintest clue what this app is trying to do on your 64-bit implementation. How could they?
Run ProcMon, filter out the junk you don't want to see, like your a/v process, Windows Search, etc., then start the app. I can guarantee you'll see either 'NAME NOT FOUND', 'PATH NOT FOUND' or 'ACCESS DENIED'.
Comments:
-
Thank you very much for your feedback.
You don't seem to be reading completely.
I already mentioned that we didn't find any solution by running procmon for this particular application.
The current topic is not about procmon uses.
If you don't want to provide any solution simple skip this page.Some techie will provide an answer. - ur00361883 8 years ago-
Perhaps you should reconsider who is a "techie" when the information you are providing is obviously insufficient to be able to provide a “techie” answer… Crystal Balls come to mind…
What about the windows event log? What about application event logs? (Being a serious application, logs *must* be present) Are you sure that no other services are involved, that also need to have permissions assigned for a “normal” user… - Pressanykey 8 years ago-
I don't think this forum is that helpful.This is going in a completely wrong direction. Anyone would enter into forums after trying all the options through Event viewer logs, processmon. I would try some other forum because I need some help or suggestions not debate.Many thanks for your precious time. - ur00361883 8 years ago
Posted by:
EdT
8 years ago
Have you considered using the Application Compatibility Toolkit that Microsoft provides ? You run the application as an admin and it lists all the issues you may encounter when running as a standard user. Or do we assume that you have already tried this as it's clearly a tool that any packager would use before posting, in the event that procmon did not give you the required information?
Posted by:
Pressanykey
8 years ago
Hi,
as I don't know the Avaya IP Agent, I did a quick search, asking my friend google.... this is what he told me...
https://support.avaya.com/forums/showthread.php?t=1626
and this...
http://www.iaug.org/p/fo/et/thread=23956
I could not find anything "official" about IP Agent being End Of Life, but it seems this is the case...
Most recommend updating to Avaya One-X Communicator. If you do get it to work (I assume it is not just setting permission for file access, but also being able to control services, as well as TAPI being a problem) you cannot expect any support.
Cheers
Phil
as I don't know the Avaya IP Agent, I did a quick search, asking my friend google.... this is what he told me...
https://support.avaya.com/forums/showthread.php?t=1626
and this...
http://www.iaug.org/p/fo/et/thread=23956
I could not find anything "official" about IP Agent being End Of Life, but it seems this is the case...
Most recommend updating to Avaya One-X Communicator. If you do get it to work (I assume it is not just setting permission for file access, but also being able to control services, as well as TAPI being a problem) you cannot expect any support.
Cheers
Phil
Comments:
-
THe application is workign if we run the exe with "runasadmin".... But we need to deliver the app to normal users who don't have admin rights..How to achieve this as shims from ACT are not working. - ur00361883 8 years ago
Posted by:
tech@chch.org
8 years ago
Try creating a batch script and then run the batch file:
# Change Frameworks to 32bit
Call C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\Ldr64.exe SetWow
#Open the Program
Call "ipagent.exe"
#Must close the program first for this last command to run which sets Frameworks back to 64bit
Call C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\Ldr64.exe Set64
I use this for Cisco Phone Designer
Posted by:
apptopack
8 years ago
Are you virtualizing the application? Your tag has pointed to virtualization. Kindly confirm.
Comments:
-
Yes VIgnesh, I need to virtualiza it. But the problem is with local application itself and I need to remediate it first. - ur00361883 8 years ago
