Answered by:
Cannt get application from http server. Error 4605F3-00000725-00000001

Question
-
I install appv from MDOP 2010.
My config is
server:
Win Server 2008 R2; SQL Express 2008; App Virt managment server 4.5 sp1; IIS 7.5 on one Virtual PC
Clietn : Win7 86x Ent.
I create test package of application. Specify deployment on http 192.168.0.103 path /content
On IIS server - I specify Mime type for OCD and SFT ext.
Create virt directory for /content folder.
On app V managment server - import my pakage.
On client I install appv 4.6 client and add http://192.168.0.103/content as server.
When I try to update applications - got next error
application virtualization client could not update ....
Incorect Function.
Error 4605F3-00000725-00000001
Have no idia what to do.
If anyone can help... Please!
Thursday, March 25, 2010 1:19 PM
Answers
-
Hello,
WEll, if you need HTTP and publishing - read this article;
http://blogs.msdn.com/johnsheehan/archive/2009/03/24/http-publishing-in-app-v-part-1.aspx
/Znack- Marked as answer by Maxim Ternovenko Friday, March 26, 2010 10:53 AM
Friday, March 26, 2010 9:50 AM
All replies
-
Hello,
Try setting it up as a publishing server instead using the RTSP protocol./Znack
Thursday, March 25, 2010 5:54 PM -
First of all - thx for reply!
I will try it now.
But any way - I need to deliver apps over internet with use only 443 port (I use 80 for simplicity in testing env).
So I will need HTTP\HTTPS , no meter if RTSP will work for me.
I think that my problem in IIS settings. But I cannt find where is my problem.
Mime type for OSD=text\plain and SFT = application\softgrid, permission to everyone, Directory Browsing enabled.
May be I missed smth....
Friday, March 26, 2010 9:14 AM -
Hello,
WEll, if you need HTTP and publishing - read this article;
http://blogs.msdn.com/johnsheehan/archive/2009/03/24/http-publishing-in-app-v-part-1.aspx
/Znack- Marked as answer by Maxim Ternovenko Friday, March 26, 2010 10:53 AM
Friday, March 26, 2010 9:50 AM -
Thx! It helps me to find out what is my issue.
There were bad reqwest ot IIS server and bad manifest file.
Its working now!
Many thx for your answer.
Friday, March 26, 2010 10:54 AM