Re: Sharepoint Migration issues

I checked the identity on the application pools on the existing server and
the new server. They were all set for "network services". As Todd did with
his server, I added a domain user to the identity tab and then gave that user
admin access to the sql box. I still received the same error when I tried to
connnect to the configuration database. There were no failures reported in
the security log on the SQl server. I have done some troubleshooting with
the 50070 error, but I'll keep poking along. Thanks for your help, and if
you have any other ideas, please let me know-

"Todd Klindt [MVP]" wrote:

The 50070 errors are the WSS equivalent of the "Check Engine Soon" light on
your car. There are just short of a million things that trigger that error,
it's as generic as they come. In my environment I have a couple of servers
that fire those off twice a second or so continuously, but the servers work
fine, and can obviously access the databases just fine. There are a couple
of KB articles that talk about how to troubleshoot 50070 errors. It's worth
your time to walk through them, but don't get fixated on that particular
error.

If your SQL server is not the same as your IIS server (I think your case
it's not) I've always run the IIS AppPool under an identity that access to
the SQL server. A domain user, not a built in account on the IIS server.
Can you try running your App Pool's as a Windows user that has admin access
on the SQL box and see if that helps? Make sure to reset them all after you
change the identity. Did you crank up the failure reporting on the SQL box?
Any failures in the Security log?

tk
"Jason" <4f7cdf1c-1850253564@xxxxxxxxxxxxxx> wrote in message
news:3C633CDB-7217-4A48-95D6-EC073876EC57@xxxxxxxxxxxxxxxx
Well it's nice to know that i have the right idea on this. On my WSS
server,
the event viewer states: #50070: Unable to connect to the database
DATABASE_NAME on SERVER_NAME. Check the database connection information
and
make sure that the database server is running. The server is running, so
i
dont know how muc that helps us. I am unable to find errors on the SQL
server. I have not changed any passwords lately. I checked the identy
on
the application pools and they are both set to network service. I checked
the local folders and they appear to have the same rights. Can you tell
me
which other services I should check? And by the way i appreciate your
help-

When I try to connnect to the configuration database, I check the audition
on the WSS server which states: #50070: Unable to connect to the database
Intra_Sharepoint_Config on MG-APP. Check the database connection
information
and make sure that the database server is running. I am unable to find
errors on the SQL server.
I have not changed any passwords lately. I checked the identy on the
application pools and they are both set to network service. Can you tell
me
which services I should check?

"Todd Klindt [MVP]" wrote:

It sounds like your methods are pretty sound. Nothing really jumps out
as
wrong. Not sure if that's good or bad. :)

If you haven't already crank up all the failure auditing on your SQL and
WSS
servers and try to connect to your Config database. Can you verify that
all
the accounts and services on the new WSS server are running as the same
users that currently work on the old server? Have you changed any
passwords
lately?

As for the STSADM restore failing, the old and new versions of WSS must
be
EXACTLY the same, right down to each and every hotfix. STSADM is very
picky
about that. If you plan and pointing to the same SQL I wouldn't go down
this road just yet though. Let's see if we can figure out why SQL is
being
fussy first.

tk
"Jason" <4f7cdf1c-1850253564@xxxxxxxxxxxxxx> wrote in message
news:F3B216F3-41AF-47C3-A6A1-7EFDC5CC5437@xxxxxxxxxxxxxxxx
I appologize what may seem like a mundane issue, but I have exhausted
all
resources on this issue:

I am trying to migrate the front end of WSS 2003 server to a different
server. Both servers are windows 2003 with updated patches. The
backend
database is on a SQL 2000 that will not be migrated to a different
server.
I
believe I need to basically install WSS on my new server. I want to
setup
as
a server farm and connect to the exisiting configuration and content
database. Once I have the new server running, I believe I can
disconnect
the
old server from the sharepoint databases and then my migration would be
complete. (Please correct me if this is not a good idea). So I
started
the
process by creating a new virtual server on my new server. From the
sharepoint Configuration page, I am at the page where it prompts me to
connect to the configuration database. I type in the name of my
configuration database and the server name in which it resides. I
make
sure
to have the "connect to existing configuration database" checkbox is
checked.
I also have the "Use Windows authenticaion" radio button selected since
that
is what I used on the existing server.


When I try to do that, I receive an error message:
[DBNETLIB][ConnectionOpen
(Connect()).]SQL Server does not exist or access denied. (Error code:
17).


I have verified the account that is used by application pool does have
the
required permissions to the SQL Server database by using this article
as a
reference: http://support.microsoft.com/?kbid=823287

I have tried the following tip from an another KB:
----------------------------------------------------
"This is due to SharePoint Portal Server and Windows SharePoint
Services
implementation of .NET Code Access Security (CAS). A solution that
addresses the aforementioned error is cited below:
. Locate and open the wss_minimaltrust.config file (NOTE: If you've
gone with the default SharePoint or WSS install, this file is located
at <INSTALL_DRIVE>:\Program Files\Common Files\Microsoft Shared\Server
Extensions\60\Config)
. Add the following element to the SecurityClasses section of this
config file:
<SecurityClass Name="SqlClientPermission"
Description="System.Data.SqlClient.SqlClientPermission, System.Data,
Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
/>
. In the PermissionSet section of this configuration file, add the
following:

<IPermission class="SqlClientPermission" version="1"
Unrestricted="true" /> "

--------------------------------------------------------------------

And that method does not fix my issue.


I have tried other methods for migration. For example:
I have also tried to migrate using the stsadm tool. I created a backup
of
the current site by using front page and then I tried to do a restore
on
the
new site, but I received an error saying "your backup is from a
different
version of windows sharepoint services and cannot be restored to a
server
running the current version" I have verified that they are the same
version
of sharepoint installed so I am confused on why I am receiving this
message.

So in summary, I am sure you can see I am pretty stuck on what
direction I
need to go to resolve this issue. I appreciate any help that anyone
could
provide.






.

Loading