Re: WebDNA 6 and OS X Tiger

This WebDNA talk-list message is from

2005

It keeps the original formatting. numero = 63217
interpreted = N
texte = UPDATE:It works.Not sure how but somehow in BOTH my attempts on this (with 2 differentmachines) I failed to notice that the real reason the admin client wasn'tresponding was due to a lack of a DNS PTR record pointing to the IP numberof the machines. The installs started grabbing an IP from a DHCP server butone of the first things I would do was set the IPs manually.Turns out that I was off by 1 number as compared to my PTR file (blush).Sooooo this means (After countless hours and much testing) that Craig'sworkaround is indeed working for me using Tiger and Webstar V.I would also believe that if SMSI were to follow the same procedure themystery of what security settings Tiger doesn't like could be found in acomparison from the before and after.In any case, thanks Craig and hopefully I wont be posting in a day or twowith a "shouldn't have spoken too soon" message:-)AlexOn 10/16/05 8:23 PM, "Alex McCombie" wrote:> Craig,> Any anyone else.> I tried the solution below and while it had the desired effect of launching> WebDNA at startup it effectively disabled the ability for Webstar's Admin> Client to connect to the admin server.> > I am not sure why this happens but it is consistent across a couple of> machines and installs. :-(> > Bummer.> > For the life of me no matter how many permission I fix beyond that (first> with webstar and then wit disk utility) my client will NOT connect again> until I deal with a clean system install. I am sure there is something> somewhere but damn if I can find it.> > So are there ANY other options on the table? I am sitting here with 2 brand> new Macs and unable to get WebDNA to run (at least past the first restart).> > SMSI? > > 10.4 and DNA 6 and Webstar 5.4> > > > > > > 2005/07/10 12:11:52 Craig Forest Re: WebDNA 6 and OS X Tiger> > Hey Daryl,> > I'm not sure if you or anybody else has found the answer to this =20> problem yet but I found a way to make it work and I figured I would =20> share it. What I did was after I updated the server software to 10.4 =20=> > I found that I had to manually boot webcatalog on startup. I also =20> found however that there is the startup script still in the startup =20> items located in /System/Library/StartupItems/WebCatalog. Obviously =20> it doesn't work otherwise webcatalog would have booted up so what I =20> tried doing was moving the startup item into /Library/StartupItems =20> and starting up again. When I restarted it took an extra long time =20> to fully boot up, once I had boot up and logged back into the server =20> however it came up with an alert window saying that WebCatalogs =20> startup script wasn't the proper permissions and asked me if I wanted =20=> > to correct them. I clicked "Correct Permissions" and I'm not sure if =20=> > it asks to restart or not since this was a while ago, but either way, =20=> > once the system restarted I moved the startup item out of /Library/=20> StartupItems, and moved it back into /System/Library/StartupItems/ =20> and rebooted one more time. This time I didn't log in as anybody and =20=> > left the server at the login screen to insure that I could do a =20> proper test, I used another machine to try out a webcatalog site and =20> sure enough it worked which obviously meant that webcatalog was =20> booting up on startup once again.> > Basically the problem with it is permissions. I don't know if there =20> is a stream lined way to go about fixing the problem or not, but I =20> was surprised that Tiger server detected the problem and wanted to =20> fix it when I transfered it to the other StartupItems folder. Once =20> it fixes it, move it back where it belongs and all is good as new.> > Hope this helps> > --> Craig Forest> ColdWave Networks> http://coldwave.net> cforest@coldwave.net> > > > -------------------------------------------------------------> This message is sent to you because you are subscribed to> the mailing list .> To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to> > Web Archive of this list is at: http://webdna.smithmicro.com/-- Alex J McCombie Adventure Skies Interactive (ASI)Owner Box 124888/892.6379 MartVille, NY 13111Alex@Adventureskies.comInterface Designer WebDNA Programmer Database Designer-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

Re: WebDNA 6 and OS X Tiger ( Craig Forest 2005)
Re: WebDNA 6 and OS X Tiger ( Alex McCombie 2005)
Re: WebDNA 6 and OS X Tiger ( Rob 2005)
Re: WebDNA 6 and OS X Tiger ( Alex McCombie 2005)
Re: WebDNA 6 and OS X Tiger ( Alex McCombie 2005)
Re: WebDNA 6 and OS X Tiger ( Craig Forest 2005)
Re: WebDNA 6 and OS X Tiger ( Jim Lanford 2005)
WebDNA 6 and OS X Tiger ( Daryl Mitchell 2005)

UPDATE:It works.Not sure how but somehow in BOTH my attempts on this (with 2 differentmachines) I failed to notice that the real reason the admin client wasn'tresponding was due to a lack of a DNS PTR record pointing to the IP numberof the machines. The installs started grabbing an IP from a DHCP server butone of the first things I would do was set the IPs manually.Turns out that I was off by 1 number as compared to my PTR file (blush).Sooooo this means (After countless hours and much testing) that Craig'sworkaround is indeed working for me using Tiger and Webstar V.I would also believe that if SMSI were to follow the same procedure themystery of what security settings Tiger doesn't like could be found in acomparison from the before and after.In any case, thanks Craig and hopefully I wont be posting in a day or twowith a "shouldn't have spoken too soon" message:-)AlexOn 10/16/05 8:23 PM, "Alex McCombie" wrote:> Craig,> Any anyone else.> I tried the solution below and while it had the desired effect of launching> WebDNA at startup it effectively disabled the ability for Webstar's Admin> Client to connect to the admin server.> > I am not sure why this happens but it is consistent across a couple of> machines and installs. :-(> > Bummer.> > For the life of me no matter how many permission I fix beyond that (first> with webstar and then wit disk utility) my client will NOT connect again> until I deal with a clean system install. I am sure there is something> somewhere but damn if I can find it.> > So are there ANY other options on the table? I am sitting here with 2 brand> new Macs and unable to get WebDNA to run (at least past the first restart).> > SMSI? > > 10.4 and DNA 6 and Webstar 5.4> > > > > > > 2005/07/10 12:11:52 Craig Forest Re: WebDNA 6 and OS X Tiger> > Hey Daryl,> > I'm not sure if you or anybody else has found the answer to this =20> problem yet but I found a way to make it work and I figured I would =20> share it. What I did was after I updated the server software to 10.4 =20=> > I found that I had to manually boot webcatalog on startup. I also =20> found however that there is the startup script still in the startup =20> items located in /System/Library/StartupItems/WebCatalog. Obviously =20> it doesn't work otherwise webcatalog would have booted up so what I =20> tried doing was moving the startup item into /Library/StartupItems =20> and starting up again. When I restarted it took an extra long time =20> to fully boot up, once I had boot up and logged back into the server =20> however it came up with an alert window saying that WebCatalogs =20> startup script wasn't the proper permissions and asked me if I wanted =20=> > to correct them. I clicked "Correct Permissions" and I'm not sure if =20=> > it asks to restart or not since this was a while ago, but either way, =20=> > once the system restarted I moved the startup item out of /Library/=20> StartupItems, and moved it back into /System/Library/StartupItems/ =20> and rebooted one more time. This time I didn't log in as anybody and =20=> > left the server at the login screen to insure that I could do a =20> proper test, I used another machine to try out a webcatalog site and =20> sure enough it worked which obviously meant that webcatalog was =20> booting up on startup once again.> > Basically the problem with it is permissions. I don't know if there =20> is a stream lined way to go about fixing the problem or not, but I =20> was surprised that Tiger server detected the problem and wanted to =20> fix it when I transfered it to the other StartupItems folder. Once =20> it fixes it, move it back where it belongs and all is good as new.> > Hope this helps> > --> Craig Forest> ColdWave Networks> http://coldwave.net> cforest@coldwave.net> > > > -------------------------------------------------------------> This message is sent to you because you are subscribed to> the mailing list .> To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to> > Web Archive of this list is at: http://webdna.smithmicro.com/-- Alex J McCombie Adventure Skies Interactive (ASI)Owner Box 124888/892.6379 MartVille, NY 13111Alex@Adventureskies.comInterface Designer WebDNA Programmer Database Designer-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Alex McCombie

DOWNLOAD WEBDNA NOW!

Re: WebDNA 6 and OS X Tiger

2005

Top Articles:

Related Readings: