Installed Gemini to local machine using Setup.msi and had no problems.
Ran SetupDB.msi and got this error for several stored procs…
Msg 4104, Level 16, State 1, Procedure gemini_getlut_1, Line 18
Multi-part identifier 'b.username' could not be bound.
Msg 104, Level 16, State 1, Procedure gemini_getlut_1, Line 18
ORDER BY items must appear in the select list if the statement contains
a UNION operator.
Contacted support via email at 2:07pm, received reply at 2:15pm (awesome support). Support said they do not support SQL Server 2005 yet, but that other customers had modified the install scripts to work. They did not say what changes those customers had made. So I opened the Create_Procs.sql script in Deploy\Step1_SQL_Database.
I edited the following stored procs…
- gemini_getlut_1
- gemini_getissueupdatedata
- gemini_getlutentries
- gemini_getxplutentries
I changed the order by clause for the union all to "username" instead of "b.username", i.e.
union all
select a.userid, b.firstname + N' ' + b.surname as username from projectresource a, users b
where a.projid=@projid and b.userid=a.userid and a.isactive = 'y'
order by b.username
Became...
union all
select a.userid, b.firstname + N' ' + b.surname as username from projectresource a, users b
where a.projid=@projid and b.userid=a.userid and a.isactive = 'y'
order by username
Ran the script file and everything installed correctly.
Logged in using admin/admin and created a new user with admin privileges.
To move to my build machine, I backed up the database and restored it on the target server. Installed the executables (setup.msi) to the target machine and edited the web.config to point to the new server. Also pointed web.config to SMTP server for e-mail.
Sorry for the incomplete sentences and any grammatical mistakes. I was just recording my steps in OneNote as I was working through the process and I am posting them unedited.
No comments:
Post a Comment