|
|
 Posted 8/5/2008 3:40:42 PM |
|
|
Forum Member
Group: Forum Members
Last Login: 9/12/2008 3:37:35 PM
Posts: 2,
Visits: 7
|
|
Hey all -
I'm hoping somebody out there can help - been waiting for a call back from tech support but haven't received one yet, hope they aren't too insanely busy!
So here's the deal. I have a Newsgator server in NY running a down level version of the software - we are upgrading to new hardware, the new Newsgator and SQL 2005 at a location in Colorado. I backed up the current database and copied it Colorado, restored it to the new SQL database and that seemed all fine. So I then go to do the install and it wants to upgrade the database version 1.4.2.185 to 3.0.0.679, but it fails with the following:
Problem creating procedures: ambiguous column name 'CreateDate'. Ambiguous column name 'GroupID'
So I'm stuck - anybody out there have a solution?
thank you!!
Lirria
|
|
|
|
| Posted 8/6/2008 1:54:46 PM |
|
|
NewsGator
Group: Administrators
Last Login: 12/26/2009 10:29:18 AM
Posts: 2,263,
Visits: 54,150
|
|
Hi Lirria,
You've actually posted in our TopStyle forum (it's an HTML, xHTML and CSS editor), but it sounds like you are talking about NewsGator Enterprise Server.
The NGES Support guys don't hang out here since we don't offer forum support to enterprise customers. However, if you can give me the name of the support guy you normally work with, I'll make sure someone contacts you!
Jonathon McDougall
NewsGator Support
|
|
|
|
| Posted 8/6/2008 1:59:53 PM |
|
|
NewsGator
Group: Administrators
Last Login: 12/26/2009 10:29:18 AM
Posts: 2,263,
Visits: 54,150
|
|
Also, what company do you work for  It'll help us look into your case
Jonathon McDougall
NewsGator Support
|
|
|
|
| Posted 8/6/2008 5:01:07 PM |
|
|
Forum Member
Group: Forum Members
Last Login: 3/1/2009 4:36:25 AM
Posts: 86,
Visits: 524
|
|
| This is unlikely to be problems with the migration of the database and its tables. It is a common error when handling db selections where joins are used. Where the join is to be made on fields where those field names are the same in both tables, the sql can reply with this error. e.g. Problematic SELECT thisfield
FROM table1
JOIN table2
ON table1.thisfield = table2.thisfield e.g. Better SELECT thisfield=t1.thisfield
FROM table1 t1
JOIN table2 t2
ON t1.thisfield = t2.thisfield Louise
|
|
|
|
| Posted 8/7/2008 10:47:06 AM |
|
|
Forum Member
Group: Forum Members
Last Login: 9/12/2008 3:37:35 PM
Posts: 2,
Visits: 7
|
|
| sorry about posting in the wrong place - I keep doing that unfortunately - I get in too much of a hurry. Any way - it actually was a problem with the build.07.Procedures.sql file - there were 4 characters missing from one line (who know g. in front of 2 different words would make such a differece) But we added that in (yes it should have been in there from all the upgrades but it wasn't) So it's all fixed now. Thank you! Lirria
|
|
|
|