Reports from 7.5 early adopters?

[Nick Wesselman]

Any reports on bugs / quirks with 7.5 so far? I'm working with a group
now who's on the 6.5 release and is considering an upgrade to at least
7.1, but possibly to 7.5.

[Matt]

Go directly to 7.5 IMO - so far I find it less buggy than 7.0/7.1 -
especially if you intend on implementing navigation manager

might want to check the "7.5 is out" topic.

--
Matt

[Rosey]

I have 6.5 currently - and while I can't upgrade (thanks to the
stagnation in XCMS 6.0 and some remaining dependencies) I am moving
new projects to a 7.5 installation.

At least that was the plan. I have not yet been able to install 7.5
successfully against a SQL Server 2005 backend. I am getting errors
that it can't connect to the IoAdministration database (which doesn't
yet exist ?)) and then after restart the installation bombs.

Waiting for RDPS to call me back and tell me that 2005 isn't "really"
supported in 7.5.

Anyone have any luck running against 2005? Would love to hear how you
got it set up.

> > 7.1, but possibly to 7.5.- Hide quoted text -
>
> - Show quoted text -

[Gavin Cope]

With regards to the SQL 2005 install bombing out. Get a hold of Microsoft Component Checker (http://www.microsoft.com/downloads/details.aspx?FamilyID=8f0a8df6-4a21-4b43-bf53-14332ef092c9&DisplayLang=en ) and run it against your system. I had a similar problem and found one dll missing that the RedDot install did not pick up in it's MDAC check. The other thing of course is to make sure you have the SQL 2005 pre-requisites installed. This can be tricky as there appears to be a difference between the various packages available for download. Grab a copy of the full install for SQL 2005 and install the pre-requisites from that. Bear in mind that if you uninstall what you've currently got and then reinstall the SQL 2005 components again, it will remove some critical MDAC files so you'll need to run the aforementioned component checker to find out which ones and reinstall them.

Cheers,

Gavin

[mikeserulneck]

I received an email from RedDot Product Marketing last night that
lists a few just found quirks:

1. Absence of the tag filtering interface for the Text Editor
that was in 7.1

2. Absence of the redlining preview button in the Tasks dialog

3. Page preview from the Tasks dialog shows the CMS page only
without the foundation page

All three issues have been identified as bugs and fixed in a Hotfix
release that is currently in QA, which is expected to take until the
beginning of next week.

Please be aware of these issues and direct any customers experiencing
them to Product Support. The Product Support team will note the
customer's e-mail address and notify them immediately upon the release
of the Hotfix.

On Mar 1, 6:28 pm, "Nick Wesselman" <nick.youpho...@gmail.com> wrote:

[Geoff Sowrey]

Not so much a report on our own experiences, but we were just informed
by RedDot to probably not upgrade right now and stay with 7.1 Hotfix
5. (We had planned to do an upgrade this Friday.)

So take that for what it's worth.

A shame, since the install had gone so well, and there's a number of
features in 7.5 we were hoping to start using. We'll wait until the
next hotfix, I guess.

Geoff

[Searles, Mike S.]

Did they mention why you should wait to upgrade?  Anything specific to note?

[Geoff Sowrey]

Nothing really specific, no. What they did mention was that there were
some "bugs" that would impede our project working properly. (RedDot
has been VERY good at helping us out with our esoteric requests, so
are also VERY familiar with our project.)

I suspect this was an intelligent move on their part, since if we had
upgraded we'd just be pestering them even more to fix what's wrong. ;)

[Rosey]

Thanks very much for this information. And in fact - you are / were
exactly right. There was a missing .dll file on the CMS box relating
to SQL Server that needed to be dropped into the system32 folder.

As he always does - Nik from RD product support saved the day - he
sent me the missing file (sqlunirl.dll) which I dropped into the
directory - and the install went smooth as silk.

So far no other bugs that I'm seeing - but I'm only 2 days in on a
couple of projects that are pretty vanilla. Export / Import from a
6.5 machine went perfectly as well.

On Mar 5, 5:10 pm, "Gavin Cope" <gavin.c...@gmail.com> wrote:
> With regards to the SQL 2005 install bombing out. Get a hold of Microsoft

> Component Checker (http://www.microsoft.com/downloads/details.aspx?FamilyID=8f0a8df6-4a2...)

> and run it against your system. I had a similar problem and found one dll
> missing that the RedDot install did not pick up in it's MDAC check. The
> other thing of course is to make sure you have the SQL 2005 pre-requisites
> installed. This can be tricky as there appears to be a difference between
> the various packages available for download. Grab a copy of the full install
> for SQL 2005 and install the pre-requisites from that. Bear in mind that if
> you uninstall what you've currently got and then reinstall the SQL 2005
> components again, it will remove some critical MDAC files so you'll need to
> run the aforementioned component checker to find out which ones and
> reinstall them.
>
> Cheers,
>
> Gavin
>

> On 06/03/07, Rosey <mike.rosel...@gmail.com> wrote:
>
>
>
>
>
> > I have 6.5 currently - and while I can't upgrade (thanks to the
> > stagnation in XCMS 6.0 and some remaining dependencies) I am moving
> > new projects to a 7.5 installation.
>
> > At least that was the plan. I have not yet been able to install 7.5
> > successfully against a SQL Server 2005 backend. I am getting errors
> > that it can't connect to the IoAdministration database (which doesn't
> > yet exist ?)) and then after restart the installation bombs.
>
> > Waiting for RDPS to call me back and tell me that 2005 isn't "really"
> > supported in 7.5.
>
> > Anyone have any luck running against 2005? Would love to hear how you
> > got it set up.
>
> > On Mar 3, 9:46 am, "Matt" <mgwat...@gmail.com> wrote:
> > > Go directly to 7.5 IMO - so far I find it less buggy than 7.0/7.1 -
> > > especially if you intend on implementing navigation manager
>
> > > might want to check the "7.5 is out" topic.
>
> > > --
> > > Matt
>
> > > On Mar 1, 6:28 pm, "Nick Wesselman" <nick.youpho...@gmail.com> wrote:
>
> > > > Any reports on bugs / quirks with 7.5 so far? I'm working with a group
> > > > now who's on the 6.5 release and is considering an upgrade to at least
> > > > 7.1, but possibly to 7.5.- Hide quoted text -
>

> > > - Show quoted text -- Hide quoted text -

[Gavin Cope]

Glad to help :) Maybe the install should be doing a check for the existence of this file as that's the same one I had dramas with too.

[TheJonathan]

I'm planning a upgrade from 6.5 to 7.5 this weekend. Has anyone found
that these install issues (a missing DLL) are fixed in "RedDot CMS 7.5
Hotfix 6 - version 7.5.0.33 - upgrade only"?

Thanks!

--Jonathan

On Mar 8, 6:28 pm, "Gavin Cope" <gavin.c...@gmail.com> wrote:
> Glad to help :) Maybe the install should be doing a check for the existence
> of this file as that's the same one I had dramas with too.
>

[michael]

The "missing DLL" is actually a Microsoft DLL, sqlunirl.dll, that is
*supposed* to be part of the SQL 2005 Client Components -- it's a
dependency if sqlsvr.dll or one of the other SQL server libraries.
Sometimes this file is simply missing, for unknown reasons. After
installing MS SQL 2005 Client Components, double check if
"sqlunirl.dll" exists in the "Windows\System32" directory. If not,
you need to find a copy and drop it in. Absense of this file could
cause ambiguous SQL errors during or after installation -- "error 26"
or similar, if memory serves.

[BjP]

Hi guys,

I had the same problem with sqlunirl.dll on an Oracle installation of
RedDot recently.

The file is used to check for the existence of a RedDot database but
is not used on initial installation on Oracle.

This meant I could install RedDot, stick in Up and Away and everything
appeared to work.

On trying to upgrade the CMS version to the most recent, this is when
the install tried to use the sqlunirl.dll file and basically blew away
my install (ie contact your server administrator message in /cms) It
blew away the system tables making either a db recover or reinstall
necessary.

According to the IT support guys, we had a 'standard' install of
Windows with the required MDAC components. I would be interested to
see what version of MDAC this dll is specific to and if there are
perhaps problems at the MDAC component side that dont install this
file.

Definitely check for this file!!!!

Cheers,
Barry

[Gavin Cope]

An addendum to Baz's post. I found that in one SQL 2005 install, the dll was installed by default but we had to uninstall the SQL 2005 client tools. This had the effect of uninstalling the dll which was a core OS file so who knows why it insisted on uninstalling it. Anyway, copying the dll over manually fixed the problem.

Cheers,

Gavin