Forums
This topic is locked
pureaspupload problem HELP!
26 Aug 2006 21:02:00 J Moran posted:
I recently installed DW8 on my Win XP pro machine. I did a fresh install, all extensions deleted and DWMX2004 removed before installation. I also update my PureUpload219_1.mxp with the new version PureUpload222.mxp (along with the update for the bundle).I installed PureUpload222.mxp and all previously working pages (in MX 2004) do not work properly; in the behavior panel, the "Update record" server behavior goes goes missing. When I uninstall (delete) the PAU2.22 behavior using the extension manager, then the update record behaviors shows up again.
I reinstalled the PAU2.22 extension and now neither recordsets in bindings show up as well as the update record behavior. I then started getting an error "JavaScript error while loading Recordset.htm:
invalid quantifier ?.
I disabled the PAU2.22 extension once again and all is well...
In short, DW8 works as advertised as long as I don't use pureaspupload.
I am working on a hot project for a client and hope to get some idea how to fix this problem soon...I am dead in the water...Please help!
Notes on 11/18/2006
After almost 3 months there is still no resolution and no resonse to my multiple follow-up emails on this subject. This softtware has casued us hours and hours of rework and other problems. Sad customer support. Based on the number of hits to this article, I am not alone. anyone out there with solutions or similar problems please let me know jmoranfl @ hotmail.com
Edited by - Jmoranfl on 27 Aug 2006 01:57:44
Edited by - Jmoranfl on 27 Aug 2006 01:58:09
Edited by - Jmoranfl on 18 Nov 2006 22:57:19
Replies
Replied 28 Aug 2006 09:52:14
28 Aug 2006 09:52:14 Patrick Woldberg replied:
Can you send me the ASP-page to
--------------------------------------------------
Patrick Woldberg
Web Developer at Dynamic Zones
Administrator at DMXzone.com, FLzone.net, FWzone.net and DNzone.com
--------------------------------------------------
--------------------------------------------------
Patrick Woldberg
Web Developer at Dynamic Zones
Administrator at DMXzone.com, FLzone.net, FWzone.net and DNzone.com
--------------------------------------------------
Replied 14 Feb 2007 20:19:26
14 Feb 2007 20:19:26 Peter Borcherds replied:
<BLOCKQUOTE id=quote><font size=1 face="Verdana, Arial, Helvetica" id=quote>quote:<hr height=1 noshade id=quote>
Can you send me the ASP-page to
--------------------------------------------------
Patrick Woldberg
Web Developer at Dynamic Zones
Administrator at DMXzone.com, FLzone.net, FWzone.net and DNzone.com
--------------------------------------------------
<hr height=1 noshade id=quote></BLOCKQUOTE id=quote></font id=quote><font face="Verdana, Arial, Helvetica" size=2 id=quote>
Any resolution on this yet? I am getting this problem now, but with Pure ASP Upload 3
DWMX2004 / IIS5.1 / Win XP Pro / VBScript / ASP / PHP / MSAccess 2000 / SQL Server 2000 / mySQL
www.palizdesign.com
Can you send me the ASP-page to
--------------------------------------------------
Patrick Woldberg
Web Developer at Dynamic Zones
Administrator at DMXzone.com, FLzone.net, FWzone.net and DNzone.com
--------------------------------------------------
<hr height=1 noshade id=quote></BLOCKQUOTE id=quote></font id=quote><font face="Verdana, Arial, Helvetica" size=2 id=quote>
Any resolution on this yet? I am getting this problem now, but with Pure ASP Upload 3
DWMX2004 / IIS5.1 / Win XP Pro / VBScript / ASP / PHP / MSAccess 2000 / SQL Server 2000 / mySQL
www.palizdesign.com
Replied 01 Mar 2007 22:28:01
01 Mar 2007 22:28:01 chris desborough replied:
Hi J,
Had a similar problem as well after installing DW 8.0.2 updater with missing items in the behaviours panel (like Insert, Update etc..). Had to follow the below advice from Adobe but left my version of DW at 8.0.1. All was well after that. I actually un-installed DW, re-installed and applied the DW 8.0.1 updater.
With regard to the first problem you were encountering, please refer to some recommendations below.
1. Exit from Dreamweaver if necessary.
2. Open Windows Explorer by right-clicking the main Start button and selecting Explore.
3. In Windows Explorer, browse to the following folder (this example assumes Dreamweaver 8):
C:\Documents and Settings\[username]\Application Data\Macromedia\Dreamweaver 8
Note: To see this folder, you may need to make the following change in Windows Explorer:
Tools > Folder Options > View > Advanced Settings section> Files and Folders section > Hidden Files and Folders > turn on "Show hidden files and folders".
4. Re-name this folder to an arbitrary name, such as "OLD Dreamweaver 8." Once the user configuration folder has been renamed, Dreamweaver will no longer be able to find it and Dreamweaver will automatically create a new user configuration folder with the default settings.
5. Launch Dreamweaver and see if the problem still occurs.
6. If the problem is resolved after re-creating the user configuration folder, you can delete your old user configuration folder, but save any files you may have customized and try to transfer them over to the newly created user configuration folder. See Backing up and restoring Dreamweaver settings (TechNote 18736). Note that these customized files may be the source of the problem. If the problem is reintroduced after copying old files back in, go through steps 1-5 again to get a clean user configuration folder, then transfer customized files one at a time, testing for the problem after each file is transferred, to identify the problem file.
Note: If you have Dreamweaver extensions installed, it is not recommended to move existing user configuration subfolders back into the new user configuration folder since extensions can write files to various subfolders in the Dreamweaver user configuration folder. Instead, extension users should start from the new user configuration folder and reinstall extensions using the Extension Manager installer one at a time. Test each extension individually after installing it, so that you can identify any problematic extensions.
Optional step
If the steps above don't solve the problem, then go back through the steps above again, but insert the following step after step4:
WARNING: If you edit the Windows Registry incorrectly, you can cause serious problems that may require you to reinstall your operating system. Adobe does not guarantee that problems that you cause by editing the registry incorrectly can be resolved. Edit the registry at your own risk.
5. Backup the Dreamweaver user configuration registry key, delete it, and then restart Dreamweaver to see if it fixes the problem. To do this choose Start button > Run > type in "regedit". In the Registry Editor, find the following key (this example uses Dreamweaver 8):
HKEY_CURRENT_USER\Software\Macromedia\Dreamweaver 8
Select the Dreamweaver 8 folder and choose File > Export (so that it is backed up), and then delete it (Edit > Delete).
Had a similar problem as well after installing DW 8.0.2 updater with missing items in the behaviours panel (like Insert, Update etc..). Had to follow the below advice from Adobe but left my version of DW at 8.0.1. All was well after that. I actually un-installed DW, re-installed and applied the DW 8.0.1 updater.
With regard to the first problem you were encountering, please refer to some recommendations below.
1. Exit from Dreamweaver if necessary.
2. Open Windows Explorer by right-clicking the main Start button and selecting Explore.
3. In Windows Explorer, browse to the following folder (this example assumes Dreamweaver 8):
C:\Documents and Settings\[username]\Application Data\Macromedia\Dreamweaver 8
Note: To see this folder, you may need to make the following change in Windows Explorer:
Tools > Folder Options > View > Advanced Settings section> Files and Folders section > Hidden Files and Folders > turn on "Show hidden files and folders".
4. Re-name this folder to an arbitrary name, such as "OLD Dreamweaver 8." Once the user configuration folder has been renamed, Dreamweaver will no longer be able to find it and Dreamweaver will automatically create a new user configuration folder with the default settings.
5. Launch Dreamweaver and see if the problem still occurs.
6. If the problem is resolved after re-creating the user configuration folder, you can delete your old user configuration folder, but save any files you may have customized and try to transfer them over to the newly created user configuration folder. See Backing up and restoring Dreamweaver settings (TechNote 18736). Note that these customized files may be the source of the problem. If the problem is reintroduced after copying old files back in, go through steps 1-5 again to get a clean user configuration folder, then transfer customized files one at a time, testing for the problem after each file is transferred, to identify the problem file.
Note: If you have Dreamweaver extensions installed, it is not recommended to move existing user configuration subfolders back into the new user configuration folder since extensions can write files to various subfolders in the Dreamweaver user configuration folder. Instead, extension users should start from the new user configuration folder and reinstall extensions using the Extension Manager installer one at a time. Test each extension individually after installing it, so that you can identify any problematic extensions.
Optional step
If the steps above don't solve the problem, then go back through the steps above again, but insert the following step after step4:
WARNING: If you edit the Windows Registry incorrectly, you can cause serious problems that may require you to reinstall your operating system. Adobe does not guarantee that problems that you cause by editing the registry incorrectly can be resolved. Edit the registry at your own risk.
5. Backup the Dreamweaver user configuration registry key, delete it, and then restart Dreamweaver to see if it fixes the problem. To do this choose Start button > Run > type in "regedit". In the Registry Editor, find the following key (this example uses Dreamweaver 8):
HKEY_CURRENT_USER\Software\Macromedia\Dreamweaver 8
Select the Dreamweaver 8 folder and choose File > Export (so that it is backed up), and then delete it (Edit > Delete).
Replied 21 Mar 2007 08:54:05
21 Mar 2007 08:54:05 Maria Talasz replied:
Chris,
I just wanted to thank you for this solution. It was really becoming a serious issue for me where I had to create a different XP user for myself after a couple of months each time DW8 started to crash (use it a lot).
I heard about a memory leak in DW8/XP that fills up certain regions of te system until it can't function anymore but had no idea where to look.
This fixed it and I am able to continue working!
Great,
Thanks again.
Maria
Replied 28 Mar 2007 12:36:27
28 Mar 2007 12:36:27 Mike McEachern replied:
Thanks very much for this fix. Seems to be no errors popping up so far. And I didn't have to go as far as the registry. Beautiful!
Cheers pal!
Cheers pal!
Replied 02 Apr 2008 21:33:27
02 Apr 2008 21:33:27 Paul Sloman replied:
I have this problem on a Dreamweaver CS3 installation. I have just followed all the instructions above, deleted the configuration folder and the registry. I then redownloaded all the most up to date versions of the extensions Pure ASP Upload, Pure ASP Upload Add On and Smart Image Processor. As soon as I use the Pure ASP Upload extension the Upload behavior disappears, meaning I cannot apply the 'Delete before upload' behavior.
I also get the message:
JavaScript error while loading Recordset.htm:
invalid quantifier ?
Any help would be very much appreciated as this is stopping me in my tracks!
Thanks,
Paul
I also get the message:
JavaScript error while loading Recordset.htm:
invalid quantifier ?
Any help would be very much appreciated as this is stopping me in my tracks!
Thanks,
Paul
Replied 13 May 2008 17:45:31
13 May 2008 17:45:31 Dani Perez replied:
Same error.
I can't use ASP Upload 3, since I have the same error as described above...
<img src="www.trisistema.com/public/hostingforo/error.jpg" border=0>
Not happy, if you ask me...
I'd really appreciate a solution, because all that stuff of deleting cache files, user configurations etc... doesn't seem to work.
I'm very very very disapointed of upgrading from aspupload 2... very disapointed.
I can't use ASP Upload 3, since I have the same error as described above...
<img src="www.trisistema.com/public/hostingforo/error.jpg" border=0>
Not happy, if you ask me...
I'd really appreciate a solution, because all that stuff of deleting cache files, user configurations etc... doesn't seem to work.
I'm very very very disapointed of upgrading from aspupload 2... very disapointed.
Replied 05 Jul 2008 22:55:20
05 Jul 2008 22:55:20 Elizabeth Martinez replied:
same problem here.
Javascript error while loading recordset.htm invalid quantifier ?
using dreamweaver CS3, PU Upload 3 and WIndows XP
Javascript error while loading recordset.htm invalid quantifier ?
using dreamweaver CS3, PU Upload 3 and WIndows XP
Replied 03 Dec 2008 01:04:55
03 Dec 2008 01:04:55 Peter Wiseman replied:
Why still no fix for this problem DMX?
It's your extension causing the problem - the only remidy is to delete the Dreamweaver config and start again WITHOUT pure upload.
Not very satisfactory really after TWO years of requests.
It's your extension causing the problem - the only remidy is to delete the Dreamweaver config and start again WITHOUT pure upload.
Not very satisfactory really after TWO years of requests.