Re: Sharepoint Migration issues

Hello Ada,

Well I appreciate your suggestions, unfortunately the error message still
appears. Here is what I did:

1. Yes, I have installed WSS as a server farm environment
2. I set the domain user for the sharepoint timer service
3. Yes, the domain user is in the admistrators group on the sql server.
4. Yes, I use the domain user to log into the WSS server. I imported some
data from the config database into excel without any problems while using
that domain user account.

Method 1
============
I tested it with creating a new WSS application pool and I received the same
error: " The IIS application pool user name is invalid. "

Method 2
===========
1. I am using the same domain user on my new server and the current WSS
server. The current server hosts the WSS site and also the sql database.
I'm buiding a new server with WSS on it, but the sql databsae will stay on
the existing server.

----------
Lastly, in response to your last statement about connecting a new content
database. I guess I don't want to do that because i would have to manually
add the content that is on the existing database. I'm not sure what is
stored in the configuration database, but I was hoping that I could just
create a new configuration database and then I would add the proper
permissions or whatever manually if it wouldn't be too much work.

Well, once again, i appreciate all of your time and thought you have put
into this. I'll be leaving at 4:30pm today (central) so I will probably not
respond to any other messages you post until Monday.

Have a great day,

Jason

"Ada Pan [MSFT]" wrote:

Hello Jason,

Some things I would like to confirm with you:

1. Have you installed WSS as a Server Farm environment?
2. Have you set the domain user as the log on account for SharePoint Timer
Service? You can check in Services.msc - SharePoint Timer Service - Log On
tab.
3. Have you added the domain user into the Administrators group on the SQL
Server box?
4. Have you ever used the domain account to log on to the new WSS server?
If so, have you ever successfully imported the data from that SQL Server
box when you log on to the new WSS server using the domain account?

If all the answers to the questions above are YES but the problem still
persists, we may need to try another strategy.

Method 1
========

1. Add the domain account (UserA) into the Administrators group on both the
new WSS box and the SQL Server box.
2. Use the domain account (UserA) to log on to the new WSS box, and then
create a new WSS Application Pool
3. Then, test if this issue recurs.

Method 2
========

1. Add the domain account (UserB) that you use to run the old WSS box into
Administrators group on the new WSS box.
2. Use the domain account (UserB) to log on to the new WSS box, and then
create a new WSS Application Pool
3. Then, test if this issue recurs.

Answer to your question: Do I need to connect to the existing configuration
database? What would happen if I created a new one, but connected to my
existing content database?

- Yes, you are required to connect to the existing configuration database
as you use an existing database.

- If you want to create a new content database, however, you may need to
perform some extra actions to add the existing database to the newly
created content database. The whole process is somewhat complex. For the
detailed information, you can reference " Managing the Configuration
Database " and " Managing Content Databases " sections in the WSS
Administrator's Guide, which you can download from the following web site:

http://www.microsoft.com/downloads/details.aspx?familyid=A637EFF6-8224-4B19-
A6A4-3E33FA13D230&displaylang=en

Hope this helps.

Regards,

Ada Pan

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights
.

Relevant Pages

  • Re: SharePoint Services 3.0 unable to display content
    ... When connecting to the original configuration database, ... The virtual server that is referenced here is not in the config database. ... I am 100% about the WSS. ... Microsoft Windows SharePoint Services 2.0 ...
    (microsoft.public.sharepoint.windowsservices)
  • Restore WSS sites after disaster
    ... I lost the system disk of a server with a couple of WSS ... The database files files were located on a different disk. ... It seems that in order to restore a WSS site (with stsadm -o restore etc. ...
    (microsoft.public.sharepoint.windowsservices)
  • RE: EventID1000: #50070:Unable to Connect to Database - WSS 2.0
    ... Microsoft Support Engineer by contacting Microsoft Customer Support ... Subject: EventID1000: #50070:Unable to Connect to Database - WSS 2.0 ... lot work for server that has lots of virtual servers/sites. ...
    (microsoft.public.sharepoint.windowsservices)
  • Deploy New Server Farm, then Migrate Content Databases Question
    ... I've attempted to perform a test migration of one of my WSS 2.0 "sites" to WSS 3.0 using the method described in the "Deploy a new server farm, then migrate content databases" section of the online docs. ... In "creating a web application for each virtual server that was in the old environment", should I create the content database with using the same name as the content database in the old environment or with a new name? ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Separate Intranet and Extranet Servers?
    ... WSS will not make a great FTP replacement, ... SharePoint server. ... I also don't want partners to be able to view other ...
    (microsoft.public.sharepoint.windowsservices)
Loading