dbTalk Databases Forums  

Migrate to SQL - no SQL server?!

microsoft.public.sqlserver.olap microsoft.public.sqlserver.olap


Discuss Migrate to SQL - no SQL server?! in the microsoft.public.sqlserver.olap forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Corinthian
 
Posts: n/a

Default Migrate to SQL - no SQL server?! - 12-04-2004 , 12:54 PM






I am either the only one experiencing this problem or it is so simple I'm
the only one who can't figure it out <sigh>. Hopefully someone can help me
jump the final hurdle.

New installation for MS Project 2k3SP1 with SQL 2kSP3a. Installation has
SQL on one system with Sharepoint & ProjectServer running on the other.

While on the SQL server attempting to migrate the AS database to SQL the
wizard asks for the SQL server name... and no matter what returns "Cannot
connect to SQL server." I have tried everything I can think of...
<servername>, localhost, <ip_address> ... everything return the same
message.

Can anyone shed some light on this? ... PLEASE!

TIA,

Corin



Reply With Quote
  #2  
Old   
Jéjé
 
Posts: n/a

Default Re: Migrate to SQL - no SQL server?! - 12-04-2004 , 04:32 PM






do you have any named instance of SQL Server?
like: myserver\ProjectInstance

so try to put this name.


"Corinthian" <corinthian (AT) ns (DOT) mindspring.com> a écrit dans le message de news:
41b20866$0$91010$39cecf19 (AT) news (DOT) twtelecom.net...
Quote:
I am either the only one experiencing this problem or it is so simple I'm
the only one who can't figure it out <sigh>. Hopefully someone can help
me
jump the final hurdle.

New installation for MS Project 2k3SP1 with SQL 2kSP3a. Installation has
SQL on one system with Sharepoint & ProjectServer running on the other.

While on the SQL server attempting to migrate the AS database to SQL the
wizard asks for the SQL server name... and no matter what returns "Cannot
connect to SQL server." I have tried everything I can think of...
servername>, localhost, <ip_address> ... everything return the same
message.

Can anyone shed some light on this? ... PLEASE!

TIA,

Corin





Reply With Quote
  #3  
Old   
Corinthian
 
Posts: n/a

Default Re: Migrate to SQL - no SQL server?! - 12-05-2004 , 09:54 AM



Good thought... the SQL server only has the default/single instance.

As I am out of idea and short on time. I'll see if I can get anywhere
working that angle.

I appreciate the brain storming. Any other thoughts...

Corin


"Jéjé" <willgart (AT) BBBhotmailAAA (DOT) com> wrote

Quote:
do you have any named instance of SQL Server?
like: myserver\ProjectInstance

so try to put this name.



Reply With Quote
  #4  
Old   
Jéjé
 
Posts: n/a

Default Re: Migrate to SQL - no SQL server?! - 12-05-2004 , 11:37 AM



well...

when I've this type of problems.
I create an Alias using the SQL Server client network utility.
also, this help me to force the usage of the TCP/IP or Namedpipe protocol.

"Corinthian" <corinthian (AT) notmindspring (DOT) com> a écrit dans le message de news:
eWOI0Lu2EHA.1264 (AT) TK2MSFTNGP12 (DOT) phx.gbl...
Quote:
Good thought... the SQL server only has the default/single instance.

As I am out of idea and short on time. I'll see if I can get anywhere
working that angle.

I appreciate the brain storming. Any other thoughts...

Corin


"Jéjé" <willgart (AT) BBBhotmailAAA (DOT) com> wrote in message
news:Ozz1WEl2EHA.1564 (AT) TK2MSFTNGP09 (DOT) phx.gbl...
do you have any named instance of SQL Server?
like: myserver\ProjectInstance

so try to put this name.





Reply With Quote
  #5  
Old   
Corin Hain
 
Posts: n/a

Default Re: Migrate to SQL - no SQL server?! - 12-06-2004 , 03:07 AM



Took your idea a step further for a workaround that worked...

.... loaded Analysis Services on an alternate system and was able to migrate
the services from an external system?

Still don't understand why but problem solved.

There were numerous KB articles about this issue if you has not completely
upgraded the SQL6.5 server, however this install was never 6.5 straight to
2000 and the SP were installed and verified by the version checker. ???
<sigh>

Thanks for the assist...

Corin


"Jéjé" <willgart (AT) BBBhotmailAAA (DOT) com> wrote

Quote:
well...

when I've this type of problems.
I create an Alias using the SQL Server client network utility.
also, this help me to force the usage of the TCP/IP or Namedpipe protocol.




Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.