I created a new form using the xsltform upload tool (excel --> XML)
The form validates with Validator 1.2.3 as well.
It is a very simple form - attached, although the first time I've used
repeat and group inside that. Just testing at this point.
After uploading to Aggregate and then downloading to Collect, I ran into an
error with the upload from Collect 1.2.2 (1023):
(i) Upload Results
Error: Invalid status code on Head request. If you have a web proxy, you
may need to login to your network.
I upgraded the Aggregate server to the latest 1.3. (its not used for
Production data, so I didn't care if the publishers were disabled).
I got the same error. Then I retrieved a different form on the same
Aggregate instance and used that - by contrast, the upload process was
successful.
So.... it must be the xform.
The area of the form I am suspicious about is the binding and calc for the
instance.
Somehow, the form has two blocks, one labelled with a namespace
(orx), the other without (lines 25-30). You should only have one
block.
Namespace treatment within the Javarosa XForms engine and within Aggregate
is non-standard; in general, you should avoid two tags with the same name
but different namespaces.
Mitch
···
On Mon, Feb 4, 2013 at 3:39 PM, James Dailey wrote:
I'm hoping this is an easy issue to fix.
I created a new form using the xsltform upload tool (excel --> XML)
The form validates with Validator 1.2.3 as well.
It is a very simple form - attached, although the first time I've used
repeat and group inside that. Just testing at this point.
After uploading to Aggregate and then downloading to Collect, I ran into
an error with the upload from Collect 1.2.2 (1023):
(i) Upload Results
Error: Invalid status code on Head request. If you have a web proxy,
you may need to login to your network.
I upgraded the Aggregate server to the latest 1.3. (its not used for
Production data, so I didn't care if the publishers were disabled).
I got the same error. Then I retrieved a different form on the same
Aggregate instance and used that - by contrast, the upload process was
successful.
So.... it must be the xform.
The area of the form I am suspicious about is the binding and calc for the
instance.
What version of ODK Collect and ODK Aggregate are you using? If you
aren't using the latest versions please upgrade. Also, what happens if
you go to your Aggregate server home page using the phone's browser?
Does that work?
Yaw
···
--
Need ODK help? Go to http://nafundi.com for custom features, form
design, implementation support, and user training for ODK.
Hi,
this is an old thread, but one of the few describing my problem (invalid status code on Head request). My error was occuring only when sending encrypted forms to aggregate- unencrypted forms worked ok. The solution I found was to ensure that the submission_url has /submission at the end of the url. ie https://YOURAPP.appspot.com/submission
···
On Monday, 4 February 2013 23:39:21 UTC, jpd wrote:
> I'm hoping this is an easy issue to fix.
>
>
> I created a new form using the xsltform upload tool (excel --> XML)
>
> The form validates with Validator 1.2.3 as well.
>
>
> It is a very simple form - attached, although the first time I've used repeat and group inside that. Just testing at this point.
>
>
>
> After uploading to Aggregate and then downloading to Collect, I ran into an error with the upload from Collect 1.2.2 (1023):
>
>
>
> (i) Upload Results
> - Error: Invalid status code on Head request. If you have a web proxy, you may need to login to your network.
>
> I upgraded the Aggregate server to the latest 1.3. (its not used for Production data, so I didn't care if the publishers were disabled).
>
> I got the same error. Then I retrieved a different form on the same Aggregate instance and used that - by contrast, the upload process was successful.
>
>
> So.... it must be the xform.
>
>
> The area of the form I am suspicious about is the binding and calc for the instance.
well, I happen to have a similar problem, the only difference is I am
trying to use encryption as well, Which jpd seemed not to have been using
at the time, however the similar problem persists.
I took a look at my xml file but there were not any duplicate blocks
as Mitch had earlier noticed.
jpd, did you find a solution to yours, if so please guide me through, thanks
Mitch is there anything else you think could be the problem?
Thanks to all of you again.
Cheers.
Ezra
···
On Tuesday, February 5, 2013 4:23:32 AM UTC+3, Mitch wrote:
>
> Somehow, the form has two blocks, one labelled with a namespace
> (orx), the other without (lines 25-30). You should only have one
> block.
>
> Namespace treatment within the Javarosa XForms engine and within Aggregate
> is non-standard; in general, you should avoid two tags with the same name
> but different namespaces.
>
> Mitch
>
> On Mon, Feb 4, 2013 at 3:39 PM, James Dailey wrote:
>
>> I'm hoping this is an easy issue to fix.
>>
>> I created a new form using the xsltform upload tool (excel --> XML)
>> The form validates with Validator 1.2.3 as well.
>> It is a very simple form - attached, although the first time I've used
>> repeat and group inside that. Just testing at this point.
>>
>> After uploading to Aggregate and then downloading to Collect, I ran into
>> an error with the upload from Collect 1.2.2 (1023):
>>
>> (i) Upload Results
>>>
>> - Error: Invalid status code on Head request. If you have a web proxy,
>> you may need to login to your network.
>>
>> I upgraded the Aggregate server to the latest 1.3. (its not used for
>> Production data, so I didn't care if the publishers were disabled).
>>
>> I got the same error. Then I retrieved a different form on the same
>> Aggregate instance and used that - by contrast, the upload process was
>> successful.
>>
>> So.... it must be the xform.
>>
>> The area of the form I am suspicious about is the binding and calc for
>> the instance.
>>
>> --
>> --
>> Post: opendatakit@googlegroups.com
>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> Options: http://groups.google.com/group/opendatakit?hl=en
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "ODK Community" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to opendatakit+unsubscribe@googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
>
>
> --
> Mitch Sundt
> Software Engineer
> University of Washington
> mitchellsundt@gmail.com
Bumping this post since I'm encountering the same problem, and I do not see an obvious solution in this thread. I also get this same error message only when trying to submit a form using encryption to our aggregate server. Forms that do not use encryption do not have any trouble being submitted into aggregate from our device.
At the moment, I'm using a sample form provided on the ODK website to test encryption, and this is the form that is giving me the submission error. I've attached it below. Any insight about this problem is much appreciated!
···
On Wednesday, May 29, 2013 12:48:01 PM UTC-4, Yaw Anokwa wrote:
> Hi Jacob,
>
>
>
> What version of ODK Collect and ODK Aggregate are you using? If you
>
> aren't using the latest versions please upgrade. Also, what happens if
>
> you go to your Aggregate server home page using the phone's browser?
>
> Does that work?
>
>
>
> Yaw
>
> --
>
> Need ODK help? Go to http://nafundi.com for custom features, form
>
> design, implementation support, and user training for ODK.
>
>
>
> On Wed, May 29, 2013 at 8:18 AM, wrote:
>
> >
>
> > Dear Team
>
> >
>
> > I'm using ODK and I have created the xform but when sending data I have received this error
>
> >
>
> >
>
> > Upload Results
>
> > - Error: Invalid status code on Head request. If you have a web proxy, you may need to login to your network.
>
> >
>
> > Any one who know what is the problem and how to resolve it?
>
> >
>
> > Thanks
>
> >
>
> >
>
> > On Tuesday, February 5, 2013 2:39:21 AM UTC+3, jpd wrote:
>
> >> I'm hoping this is an easy issue to fix.
>
> >>
>
> >>
>
> >> I created a new form using the xsltform upload tool (excel --> XML)
>
> >>
>
> >> The form validates with Validator 1.2.3 as well.
>
> >>
>
> >>
>
> >> It is a very simple form - attached, although the first time I've used repeat and group inside that. Just testing at this point.
>
> >>
>
> >>
>
> >>
>
> >> After uploading to Aggregate and then downloading to Collect, I ran into an error with the upload from Collect 1.2.2 (1023):
>
> >>
>
> >>
>
> >>
>
> >> (i) Upload Results
>
> >> - Error: Invalid status code on Head request. If you have a web proxy, you may need to login to your network.
>
> >>
>
> >> I upgraded the Aggregate server to the latest 1.3. (its not used for Production data, so I didn't care if the publishers were disabled).
>
> >>
>
> >> I got the same error. Then I retrieved a different form on the same Aggregate instance and used that - by contrast, the upload process was successful.
>
> >>
>
> >>
>
> >> So.... it must be the xform.
>
> >>
>
> >>
>
> >> The area of the form I am suspicious about is the binding and calc for the instance.
>
> >
>
> > --
>
> > --
>
> > Post: opendatakit@googlegroups.com
>
> > Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>
> > Options: http://groups.google.com/group/opendatakit?hl=en
>
> >
>
> > ---
>
> > You received this message because you are subscribed to the Google Groups "ODK Community" group.
>
> > To unsubscribe from this group and stop receiving emails from it, send an email to opendatakit+unsubscribe@googlegroups.com.
>
> > For more options, visit https://groups.google.com/groups/opt_out.
>
> >
>
> >
On Wednesday, May 29, 2013 12:48:01 PM UTC-4, Yaw Anokwa wrote:
Hi Jacob,
What version of ODK Collect and ODK Aggregate are you using? If you
aren't using the latest versions please upgrade. Also, what happens if
you go to your Aggregate server home page using the phone's browser?
Yes, the URL you supply in ODK Collect is the root URL for the server, and
either a /formsList or /submission is appended when fetching the list of
available form definitions or when submitting data, respectively.
Within a form, if a submission URL attribute is specified, it needs to be
that root URL plus /submission so that it identifies the full URL for the
submission endpoint on the server. Since this is required to be specified
for encrypted forms, this will trip you up if you are not aware of it.
This is also covered on the ODK documentation here:
···
On Thu, Jan 26, 2017 at 1:07 AM, wrote:
On Monday, 4 February 2013 23:39:21 UTC, jpd wrote:
I'm hoping this is an easy issue to fix.
I created a new form using the xsltform upload tool (excel --> XML)
The form validates with Validator 1.2.3 as well.
It is a very simple form - attached, although the first time I've used
repeat and group inside that. Just testing at this point.
After uploading to Aggregate and then downloading to Collect, I ran into
an error with the upload from Collect 1.2.2 (1023):
(i) Upload Results
Error: Invalid status code on Head request. If you have a web proxy,
you may need to login to your network.
I upgraded the Aggregate server to the latest 1.3. (its not used for
Production data, so I didn't care if the publishers were disabled).
I got the same error. Then I retrieved a different form on the same
Aggregate instance and used that - by contrast, the upload process was
successful.
So.... it must be the xform.
The area of the form I am suspicious about is the binding and calc for
the instance.
Hi,
this is an old thread, but one of the few describing my problem (invalid
status code on Head request). My error was occuring only when sending
encrypted forms to aggregate- unencrypted forms worked ok. The solution I
found was to ensure that the submission_url has /submission at the end of
the url. ie https://YOURAPP.appspot.com/submission
···
On Sun, May 12, 2013 at 10:57 PM, Rwakazooba Ezra Aliija < rwakazooba@gmail.com> wrote:
Hello Mitch and jpd,
well, I happen to have a similar problem, the only difference is I am
trying to use encryption as well, Which jpd seemed not to have been using
at the time, however the similar problem persists.
I took a look at my xml file but there were not any duplicate
blocks as Mitch had earlier noticed.
jpd, did you find a solution to yours, if so please guide me through,
thanks
Mitch is there anything else you think could be the problem?
Thanks to all of you again.
Cheers.
Ezra
On Tuesday, February 5, 2013 4:23:32 AM UTC+3, Mitch wrote:
Somehow, the form has two blocks, one labelled with a namespace
(orx), the other without (lines 25-30). You should only have one
block.
Namespace treatment within the Javarosa XForms engine and within
Aggregate is non-standard; in general, you should avoid two tags with the
same name but different namespaces.
I created a new form using the xsltform upload tool (excel --> XML)
The form validates with Validator 1.2.3 as well.
It is a very simple form - attached, although the first time I've used
repeat and group inside that. Just testing at this point.
After uploading to Aggregate and then downloading to Collect, I ran into
an error with the upload from Collect 1.2.2 (1023):
(i) Upload Results
Error: Invalid status code on Head request. If you have a web proxy,
you may need to login to your network.
I upgraded the Aggregate server to the latest 1.3. (its not used for
Production data, so I didn't care if the publishers were disabled).
I got the same error. Then I retrieved a different form on the same
Aggregate instance and used that - by contrast, the upload process was
successful.
So.... it must be the xform.
The area of the form I am suspicious about is the binding and calc for
the instance.
···
On Tue, May 27, 2014 at 6:35 AM, Andrew T. wrote:
Hello,
Bumping this post since I'm encountering the same problem, and I do not
see an obvious solution in this thread. I also get this same error message
only when trying to submit a form using encryption to our aggregate server.
Forms that do not use encryption do not have any trouble being submitted
into aggregate from our device.
At the moment, I'm using a sample form provided on the ODK website to test
encryption, and this is the form that is giving me the submission error.
I've attached it below. Any insight about this problem is much
appreciated!
ADT
On Wednesday, May 29, 2013 12:48:01 PM UTC-4, Yaw Anokwa wrote:
Hi Jacob,
What version of ODK Collect and ODK Aggregate are you using? If you
aren't using the latest versions please upgrade. Also, what happens if
you go to your Aggregate server home page using the phone's browser?
On Sun, May 12, 2013 at 10:57 PM, Rwakazooba Ezra Aliija < rwakazooba@gmail.com> wrote:
Hello Mitch and jpd,
well, I happen to have a similar problem, the only difference is I am
trying to use encryption as well, Which jpd seemed not to have been using
at the time, however the similar problem persists.
I took a look at my xml file but there were not any duplicate
blocks as Mitch had earlier noticed.
jpd, did you find a solution to yours, if so please guide me through,
thanks
Mitch is there anything else you think could be the problem?
Thanks to all of you again.
Cheers.
Ezra
On Tuesday, February 5, 2013 4:23:32 AM UTC+3, Mitch wrote:
Somehow, the form has two blocks, one labelled with a namespace
(orx), the other without (lines 25-30). You should only have one
block.
Namespace treatment within the Javarosa XForms engine and within
Aggregate is non-standard; in general, you should avoid two tags with the
same name but different namespaces.
I created a new form using the xsltform upload tool (excel --> XML)
The form validates with Validator 1.2.3 as well.
It is a very simple form - attached, although the first time I've used
repeat and group inside that. Just testing at this point.
After uploading to Aggregate and then downloading to Collect, I ran
into an error with the upload from Collect 1.2.2 (1023):
(i) Upload Results
Error: Invalid status code on Head request. If you have a web proxy,
you may need to login to your network.
I upgraded the Aggregate server to the latest 1.3. (its not used for
Production data, so I didn't care if the publishers were disabled).
I got the same error. Then I retrieved a different form on the same
Aggregate instance and used that - by contrast, the upload process was
successful.
So.... it must be the xform.
The area of the form I am suspicious about is the binding and calc for
the instance.
Bumping this post since I'm encountering the same problem, and I do not
see an obvious solution in this thread. I also get this same error message
only when trying to submit a form using encryption to our aggregate server.
Forms that do not use encryption do not have any trouble being submitted
into aggregate from our device.
At the moment, I'm using a sample form provided on the ODK website to test
encryption, and this is the form that is giving me the submission error.
I've attached it below. Any insight about this problem is much appreciated!
ADT
On Wednesday, May 29, 2013 12:48:01 PM UTC-4, Yaw Anokwa wrote:
Hi Jacob,
What version of ODK Collect and ODK Aggregate are you using? If you
aren't using the latest versions please upgrade. Also, what happens if
you go to your Aggregate server home page using the phone's browser?
I'm using Aggregate v. 1.4.3 and Collect v. 1.4.3. The form I attached had
a placeholder URL - I'm able to navigate correctly to the Aggregate server
using a web browser on the same device, using the real URL. I've been able
to successfully submit a different form that we are using that does not
utilize encryption - the problem is particular to this encrypted test form.
Any thoughts?
Appreciate the help
ADT
···
On Tue, May 27, 2014 at 12:15 PM, Yaw Anokwa wrote:
Andrew,
And the form that was attached has the URL as
url.to.aggregateserver:8080/ODKAggregate. That's probably not a valid
URL.
Yaw
Need ODK services? http://nafundi.com provides form design, server
setup, professional support, and software development for ODK.
Bumping this post since I'm encountering the same problem, and I do not
see an obvious solution in this thread. I also get this same error
message
only when trying to submit a form using encryption to our aggregate
server.
Forms that do not use encryption do not have any trouble being submitted
into aggregate from our device.
At the moment, I'm using a sample form provided on the ODK website to
test
encryption, and this is the form that is giving me the submission error.
I've attached it below. Any insight about this problem is much
appreciated!
ADT
On Wednesday, May 29, 2013 12:48:01 PM UTC-4, Yaw Anokwa wrote:
Hi Jacob,
What version of ODK Collect and ODK Aggregate are you using? If you
aren't using the latest versions please upgrade. Also, what happens if
you go to your Aggregate server home page using the phone's browser?
Remove the line breaks in the encryption key in the submission tag. e.g.,
(not sure what will happen in the e-mail, but I've removed the 6
carriage-returns in the tag below.
If you are generating this via XLSForm, you may need to construct the
string in notepad, and paste it into XLS, in order to ensure there are no
carriage returns.
···
On Tue, May 27, 2014 at 12:29 PM, Andrew Taylor < andrew.dorman.taylor@gmail.com> wrote:
Mitch and Yaw,
I'm using Aggregate v. 1.4.3 and Collect v. 1.4.3. The form I attached
had a placeholder URL - I'm able to navigate correctly to the Aggregate
server using a web browser on the same device, using the real URL. I've
been able to successfully submit a different form that we are using that
does not utilize encryption - the problem is particular to this encrypted
test form. Any thoughts?
Bumping this post since I'm encountering the same problem, and I do not
see an obvious solution in this thread. I also get this same error
message
only when trying to submit a form using encryption to our aggregate
server.
Forms that do not use encryption do not have any trouble being
submitted
into aggregate from our device.
At the moment, I'm using a sample form provided on the ODK website to
test
encryption, and this is the form that is giving me the submission
error.
I've attached it below. Any insight about this problem is much
appreciated!
ADT
On Wednesday, May 29, 2013 12:48:01 PM UTC-4, Yaw Anokwa wrote:
Hi Jacob,
What version of ODK Collect and ODK Aggregate are you using? If you
aren't using the latest versions please upgrade. Also, what happens
if
you go to your Aggregate server home page using the phone's browser?