On 2/26/07, C.jay Martin <[EMAIL PROTECTED]> wrote: > > Looking up, I'm still pretty sure it's the same problem, at least to the > root. It's the exact same error, and more specifically, a refresh works > just fine. > > 1) The database backend is SQL Server. This is required by the IT dept > here. The bindings are system-wide. > > 2) I tried adding "console" before single, it didn't do anything > helpful. > > 3) I tried psexec -l cmd.exe and running mongrel_rails. It worked > perfectly and showed no errors. > > RE: Permissions: I gave the folder full permissions for all users, and > it didn't help. > > Worst of all, the error seems to be "sometimes" now that I disabled > pagination. I -think- it might be a login-limit to the scheduler user > on the database. I'm communicating with the DB Admin regarding that > now. If it -is- that, the error could use to be more clear. If it's > -not- that, then I'll still be stuck at square one. > >
Ok, post you progress on this subject or contact me off the list in any case. Maybe you could provide more inside information and I could recreate the scenario here to get into the issue. Regards, -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
