sql 2005 beta 3

Question

Post reply

sql 2005 beta 3

Yoav S.

SSC Eights!

Points: 914
More actions
March 22, 2005 at 5:41 am

#87865

Hi all,
When I am trying to create a new Maintplan in sql2005 Beta3 I get this error:
TITLE: SQL Server Management Studio
----------------------------------------
Exception has been thrown by the target of an invocation. (mscorlib)
----------------------------------------
ADDITIONAL INFORMATION:
An OLE DB error 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.) occurred while enumerating packages. A SQL statement was issued and failed.
I looked in the even viewer and saw this message:
The prelogin packet used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor of the client library.
the only option when creating a Maintplan is to use Win auth and not sql auth.
thanks for any idea.
yoav.

Viewing 11 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply

D1rtyD0g Ten Centuries Points: 1045 More actions · Answer 1

Hi there!!

Unfortunately I don't have an answer to your question, but I have one for you...

Where did you get Beta 3?? I am under the impression that it's still to be released??

Thanks!!

Yoav S. SSC Eights! Points: 914 More actions · Answer 2

got it from MS, who else?

when attending a user group meeting.

D1rtyD0g Ten Centuries Points: 1045 More actions · Answer 3

Lucky fish!!!

Any idea where I can download it from??

MS doesn't have it...

Yoav S. SSC Eights! Points: 914 More actions · Answer 4

No, sorry.

But if you are near Tel-aviv in the next week there is another group meeting..

Adam Machanic SSCoach Points: 15370 More actions · Answer 5

FYI, Beta 3 is not released yet. What you have is probably the October CTP, which was labelled "Beta 3". Subsequent CTPs, due to the confusion that one caused, were labelled "Community Technical Preview".

--
Adam Machanic
whoisactive

Yoav S. SSC Eights! Points: 914 More actions · Answer 6

Yes I know thanks,

But can any one tell me about that error message?

Adam Machanic SSCoach Points: 15370 More actions · Answer 7

You'll probably have much better luck in the 2005 newsgroups:

http://www.aspfaq.com/sql2005/show.asp?id=1

--
Adam Machanic
whoisactive

Mike Metcalf SSCrazy Eights Points: 8763 More actions · Answer 8

the latest CTP releases are all branded beta3 on the splash screens so that's probably where the confusion is comming from.

Yoav S. SSC Eights! Points: 914 More actions · Answer 9

Got an answer from Ms beta newsgroup

"This is a known issue and will be addressed in IDW15 / Beta 3.

The workaround is to create a signed certificate (used for Server and Client

authorization) and install it on both the client and server. You can use

this link as a guide although it is for SQL 2000 and you do not need to set

anything to Force Encryption.

http://support.microsoft.com/default.aspx?scid=kb;en-us;276553&sd=tech "

Dan-265171 SSC Rookie Points: 37 More actions · Answer 10

Hello Yoav,

I've had the same error on SQL2005 9.0.1.1399(clusterd) running on MS2003 cluster.

Did you run the Surface Area Configuration after installing SQL2005?

In my case the sqlserveragent was failing to start (notice that you have to connect to virtual server, not local host! in MSSAC)

Fixing this was immpossible, tried almost everething for 3 days and then decided we build the cluster again. This time before installing SQL2005 we dedicated 4 disks for data/log/backup/quorum (both nodes same config), sql2005 setup wants to install something on these disks so they have to be present prior to installing. The problem was that the software was installed on 1 node of the cluster but not on the other so they couldn't communicate somehow..

Hope this helps

Danny