-
We have identified this as a problem where DBXL is installed on a machine that is not a member of a domain. We are investigating workarounds.
-
I have sent you an updated installstate file from a working XP Professional install modified slightly to reflect your machinename. This should allow you to avoid the error you are seeing and run the uninstall.
Please follow the below steps:1) View the IIS properties for QdabraWebService. Make sure the ASP.NET ...
-
The error about the App pool can be ignored, as IIS 5.1 does not support application pools.
Under \inetpub\wwwroot\QdabraWebService\install\, you should find a file named Qdabra.DBXL.Install.InstallState.
Please email this file to Support@qdabra.com
-
In IIS manager, look under 'Web Service Extensions' and check if WebDAV is allowed or prohibited. Toggle the setting and try editing the form template again.
-
That scenario should work.
Are you attempting to open the url from the same machine running DBXL or a separate client? And what OS are you running on the client and server?
-
It sounds like you are using the 'Open' on the attached XSN in DAT.
Download the template locally, edit the local copy and then upload the template using DAT.
-
You will need to give the ASPNET account permissions to the DBXL database. Give the ASPNET account sysadmin permission. This assumes the database is on the local machine.
-
The queryXml parameter to GetColumnsForRows2b is a string. You will need to encode the xml into a string (replacement of < with &lt; > with &gt; etc...) or use the DOM apis to set the node text value which will encode the value for you.
-
The referenced kb article in the IIS error suggests using aspnet_regiis -ga <WindowsUserAccount>. Where WindowsUserAccount is the account running, which should be ASPNET in your case.
http://support.microsoft.com/?kbid=267904.
-
Please check the Qdabra eventlog and post the content of any error messages.
Thanks,
Jim