Forums
This topic is locked
Windows 2003 Server/Service Pack 1 & Dreamweaver?
Posted 06 May 2005 16:54:02
1
has voted
06 May 2005 16:54:02 John Rotondo posted:
Has anyone else had problems with database connections in Dreamweaver after upgrading your Windows 2003 Server to Service Pack 1? I can no longer define connections, and when creating a recordset, I must use Advanced Mode or else I cannot build a recordset. This means that Dreamweaver's great built-in ASP functions like Insert/Update/Delete Record cannot be used.It's definately not a profile config problem. I build about 15 sites on this server using DW MX 2004. I never changed anything in the profiles. The only difference is SP1.
I've tested DWMX on both PC and Mac. They both have the same problem trying to make a database connection with this server. I then tested both client machines with a Windows 2000 server and everything worked just fine. I'm hoping there's someone out there that has seen this problem and knows how to fix or work around it.
Thanks for any insight you may have,
John
Replies
Replied 06 May 2005 18:57:12
06 May 2005 18:57:12 Chris Charlton replied:
What version of DW? Are you using ASP or ASP.NET? Have you surfed Macromedia's Support Knowledgebase to see if Windows 2003 Server SP1 has issues? Are you trying SecureFTP? Have you tried PassiveFTP?
Check this Macrochat out, it's about 45min long, but will show you areas to troublshoot the issue(s) you are experiencing. Butttt, I'd search on Macromedia support site first, you may find a fast answer.
www.dmxzone.com/ShowDetail.asp?NewsId=10096
~ ~ ~ ~ ~ ~ ~
Chris Charlton <i>- DMXzone Manager</i>
<font size=1>[ Studio MX/MX2004 | PHP/ASP | SQL | XHTML/CSS | XML | Actionscript | Web Accessibility | MX Extensibility ]</font id=size1>
Check this Macrochat out, it's about 45min long, but will show you areas to troublshoot the issue(s) you are experiencing. Butttt, I'd search on Macromedia support site first, you may find a fast answer.
www.dmxzone.com/ShowDetail.asp?NewsId=10096
~ ~ ~ ~ ~ ~ ~
Chris Charlton <i>- DMXzone Manager</i>
<font size=1>[ Studio MX/MX2004 | PHP/ASP | SQL | XHTML/CSS | XML | Actionscript | Web Accessibility | MX Extensibility ]</font id=size1>
Replied 06 May 2005 19:15:46
06 May 2005 19:15:46 John Rotondo replied:
Sorry for lack of more specifics. The problem is experienced using both DWMX and DWMX 2004 7.0.1 on both Mac and PC. I'm using ASP exclusively, although the server does have the .NET framework installed. I've extensively searched not only the Macromedia Support Knowledgebase, but the Internet as well. I've found no info at all on this problem. I can't possibly be the only person with SP1/Dreamweaver problems, can I?
I have not tried SecureFTP, but I've tried toggling passiveFTP mode to no positive result. I'm at a loss as to what's wrong, other than Microsoft seems to have busted stuff...
I'll take a look at that Macrochat. Thanks for the link!
John
I have not tried SecureFTP, but I've tried toggling passiveFTP mode to no positive result. I'm at a loss as to what's wrong, other than Microsoft seems to have busted stuff...
I'll take a look at that Macrochat. Thanks for the link!
John
Replied 07 May 2005 16:00:33
07 May 2005 16:00:33 Rene Bandsma replied:
I had the same problem. But I don't know where the error is coming from. In my opinion it is the combination of Dreamweaver MX2004 with Windows XP Service Pack 2. After that I had to install an 'extension fix' for this. I could create a database coneection and the test succeeded. The problem was when I want to make Queries DMX did not find any tables...
<hr><b>DMXZone support manager</b><br><a href="www.kousman.nl">Kousman web resellers</a>
<hr><b>DMXZone support manager</b><br><a href="www.kousman.nl">Kousman web resellers</a>
Replied 08 May 2005 02:42:45
08 May 2005 02:42:45 John Rotondo replied:
The XP problem is different. That is a client side issue (you installed SP2 on the machine that Dreamweaver is on and it stopped working properly). My issue is server-side. I didn't change either of the machines I run Dreamweaver from. I installed Windows 2003 Server Service Pack 1 on the server and that's when the problems started.
I guess it's time to open my wallet for a support instance to Macromedia. Not good at all. I HATE having to pay money for service on what's likely a bug on their side.
I guess it's time to open my wallet for a support instance to Macromedia. Not good at all. I HATE having to pay money for service on what's likely a bug on their side.
Replied 08 May 2005 08:01:25
08 May 2005 08:01:25 Chris Charlton replied:
Everyone should check their Firewalls.
~ ~ ~ ~ ~ ~ ~
Chris Charlton <i>- DMXzone Manager</i>
<font size=1>[ Studio MX/MX2004 | PHP/ASP | SQL | XHTML/CSS | XML | Actionscript | Web Accessibility | MX Extensibility ]</font id=size1>
~ ~ ~ ~ ~ ~ ~
Chris Charlton <i>- DMXzone Manager</i>
<font size=1>[ Studio MX/MX2004 | PHP/ASP | SQL | XHTML/CSS | XML | Actionscript | Web Accessibility | MX Extensibility ]</font id=size1>
Replied 09 May 2005 17:11:35
09 May 2005 17:11:35 John Rotondo replied:
<BLOCKQUOTE id=quote><font size=1 face="Verdana, Arial, Helvetica" id=quote>quote:<hr height=1 noshade id=quote>
Everyone should check their Firewalls.
<hr height=1 noshade id=quote></BLOCKQUOTE id=quote></font id=quote><font face="Verdana, Arial, Helvetica" size=2 id=quote>
What exactly do I check? What additional ports other than 80 does Dreamweaver need open to be able to talk to the database server?
Everyone should check their Firewalls.
<hr height=1 noshade id=quote></BLOCKQUOTE id=quote></font id=quote><font face="Verdana, Arial, Helvetica" size=2 id=quote>
What exactly do I check? What additional ports other than 80 does Dreamweaver need open to be able to talk to the database server?
Replied 09 May 2005 22:20:44
09 May 2005 22:20:44 Chris Charlton replied:
It was a general remark, I've noticed a lot of 3r-party firewalls being used, so it was a general posting about Firewalls being checked to allow DW through.
Replied 17 May 2005 04:29:46
17 May 2005 04:29:46 Martin Galabinski replied:
I've got the same problem. Just installed service pack 1 on win2003 and now I cannot connect to remote testing server. As a work around I've loaded a local odbc connection to the mysql db. I would like to know what is wrong though.
Marty
Thanks,
Marty
Marty
Thanks,
Marty
Replied 17 May 2005 11:05:06
17 May 2005 11:05:06 Lee Diggins replied:
Hi John
SQL Server runs on port 1433. Dreamweaver MX 2004 is on the exceptions list for the firewall.
My laptop is Server 2003 SP1 and I've not had any problems at all. Our Dev server has also been SP1'd and again no issues
Sharing Knowledge Saves Valuable Time!!!
~ ~ ~ ~ ~ ~
<b>Lee Diggins</b> - <i>DMXzone Manager</i>
<font size="1">[ Studio MX/MX2004 | ASP -> VBScript/PerlScript/JavaScript | SQL | CSS ]</font>
SQL Server runs on port 1433. Dreamweaver MX 2004 is on the exceptions list for the firewall.
My laptop is Server 2003 SP1 and I've not had any problems at all. Our Dev server has also been SP1'd and again no issues
Sharing Knowledge Saves Valuable Time!!!
~ ~ ~ ~ ~ ~
<b>Lee Diggins</b> - <i>DMXzone Manager</i>
<font size="1">[ Studio MX/MX2004 | ASP -> VBScript/PerlScript/JavaScript | SQL | CSS ]</font>
Replied 17 May 2005 14:29:05
17 May 2005 14:29:05 John Rotondo replied:
After dealing with Macromedia that confirmed this is a problem, I have a solution. It IS the same problem as the WinXP Hotfix. I had to install the hotfix extension on both my Mac and PC, and then all connections worked properly again. Follow the directions at this URL:
www.macromedia.com/cfusion/knowledgebase/index.cfm?id=tn_19515#aspnet_db
Good luck!
www.macromedia.com/cfusion/knowledgebase/index.cfm?id=tn_19515#aspnet_db
Good luck!