404 not found on deploy

Status
Not open for further replies.

SWSDEV

Forum User
Joined
Feb 23, 2008
Messages
256
Reaction score
0
I'm now deploying on a 64bit windows server 2008 box

Why is the following config giving me a 404? I have confirmed the files are there and the IIS server is set up properly.

<?xml version="1.0" encoding="utf-8"?>
<Graphical_Application_Designer_Project>
<Version>1.0</Version>
<Files>
<File path="GetAgentPhone.comp" type="component" />
<File path="Main.flow" type="callflow" pbx_callflow_name="CellsAgent" activation_extension="855" activation_extension_debug="856" />
<File path="MenuOptions.comp" type="component" />
</Files>
<Variables>
<ArrayOfVariable xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" />
</Variables>
<PbxServer>10.123.86.3</PbxServer>
<PbxConfigurationPort>5485</PbxConfigurationPort>
<PbxDeploymentUri>http://10.123.86.3:5484/VAD_Deploy.aspx</PbxDeploymentUri>
<PbxDownloadDebugFilesUri>http://10.123.86.3:5484/VAD_DownloadDebugInfoFile.aspx</PbxDownloadDebugFilesUri>
<PbxGetDebugFileNamesUri>http://10.123.86.3:5484/VAD_GetDebugInfoFileNames.aspx</PbxGetDebugFileNamesUri>
<NextCallflowActivationExtension>854</NextCallflowActivationExtension>
<DebugBuildSuccessful>True</DebugBuildSuccessful>
<ReleaseBuildSuccessful>True</ReleaseBuildSuccessful>
<DebugBuildNumber>80</DebugBuildNumber>
<ReleaseBuildNumber>80</ReleaseBuildNumber>
<ChangedSinceLastDebugBuild>True</ChangedSinceLastDebugBuild>
<LastDeployedConfiguration>Debug Build</LastDeployedConfiguration>
</Graphical_Application_Designer_Project>
 
I discovered the problem but not the solution.

In the file VAD_Deploy.aspx.cs you guys are reading the session variable Request.QueryString["projectname"]

When I go to the url for vad_deploy.aspx manually in a browser, the error comes up for OBJECT REFERENCE NOT SET TO AN INSTANCE OF AN OBJECT.

I confirmed that this is the problem.

What would make the VAD not pass the projectname in the query string?
 
Hi,

I'm a bit confused. A 404 error should happen if the page can not be located. An error like not sending the projectname in the querystring should report a 500 error (internal server error).

Can you try browsing manually to http://10.123.86.3:5484/VAD_Deploy.aspx?projectname=PROJECTNAME and see what happens?
 
Either that or there is more than one problem here. Because it was a 404 error I checked if all the files existed, and they did. When I manually ran the .aspx page I got the object error, but I just realized it probably errored when I checked it in the browser because I wasn't specifying anything in the querystring.

So just forget about that part. The main problem is the 404 error is happening but the file exists.

I checked the url and received:

ERROR: projectname is invalid
 
Ok, I got this to work in the browser

http://10.123.86.3:5484/VAD_Deploy.aspx?projectname=CellsAgent_Debug

I forgot the "_Debug" before.
 
So, could you finally deploy the project? Or are you still getting the 404 error from the VAD?
 
Still getting the 404 from the VAD.
 
This is very strange...
Just to be absolutely sure about what's going on, can you trace with WireShark a manual request to http://10.123.86.3:5484/VAD_Deploy.aspx?projectname=CellsAgent_80_Debug? And another request using the VAD? I would like to see what is the difference between both requests...
 
Do you want a raw data dump?
 
Yes, the dump from wireshark, so we can open it here and see the difference.
 
Status
Not open for further replies.