SMS 2003 Installation- issue with SQL server database tables creation

The issue is discussed in:
https://www.experts-exchange.com/questions/21726638/SMS-2003-Setup-problem.html

It seems that SMS 2003 SP2 is required to run on SQL Server 2005.

Hi,

1.The best way you have to manually create that database and try to install through the Enterprise manager I have also do through the manually in past.
2. If you face the problem in the manual creation then check the NTFS file permission or which user you used for create database you have have local system rights
3. You can also use the Sql enterprise manager for the troubleshooting.

any further issue tell me i m waiting /....

Hi,

After installation of SMS Server 2003 while configure the server it is giving the Error

Fatal Error:

Systems Management Server Setup Cannot continue because of the following error:

Setup Cannot create the required database tables.Contact your SQL Adiminisrator.

Kindly please help me regarding this.


Thangs&Regards

SMS 2003 SP2 is required for the SMS site database system role to run on Microsoft SQL Server 2005.

Check the links below.
http://www.microsoft.com/technet/prodtechnol/sms/smssp2/supconfig/0bdafa4a-71b3-4ed6-94bb-42a9f3986951.mspx?mfr=true

Database requirements for SMS 2003 service pack 1 are:
     Microsoft SQL Server™ 7.0 Standard Edition or Enterprise Edition with SP3 or later
     SQL Server 2000 Standard Edition or Enterprise Edition with SP3a or later
http://www.microsoft.com/smserver/evaluation/sysreqs/default.mspx
 
Database requirements for SMS 2003 service pack 2 are:
     Microsoft SQL Server 7.0 SP3 or later, SQL Server 2000 SP3a or later,
or SQL Server 2005 (Yukon) can be used to host the SMS database for SMS 2003 SP2.
http://www.microsoft.com/smserver/evaluation/2003/sp2.mspx

regards
D.E.

Hi,

Hi the which you are getting is may be due to the NTFS file permission on the drive and when you install the SMS 2003 then also try to check that sqk is on or off and I would also suggest you you can easily create that database through the Sql Enterprise manager manually.

Another way.....
download this file monitor tool File mon from the following URL

How to use :
1. Again installation process start.
2. and start filemon tool its catch all the internal activity of the server that time
3. And read the logs
4. Where you find that not found and other missing file then check that files position
5. If you do not understand then send me the with attachement i will analysis.

http://www.sysinternals.com/Utilities/Filemon.html

Hi Paawan,

Can you please also include the service pack of SMS 2003 ?

Are you installing SMS 2003 with SP1 server then it not support SQL Server 2005. Only SMS 2003 SP2  Supports ??

http://www.microsoft.com/smserver/evaluation/sysreqs/default.mspx

hi
We have Exchange server in our network.we installed another exchange server as a ADC in the same domain.Recently i moved all users mail boxes from 1st server to 2nd server.Mail boxes were moved successfully into 2nd server.now i configured in all users outlook express server settings i selected as 2nd server.But we could not able to recieve external mails,sending mails is ok.While enter the sending and recieveing i am getting this error.

Task ' Microsoft Exchange Server ' reported error ( 0x8004010F ) : 'The operation failed. An object could not be found'.

Pls. kindly tell me how to fix this problem.

Thanks&Regards

Hi,
Solution :

First of all, you don't require a connector between the two exchange servers which are under the same administrative group and routing group. users from both servers will be able to exchange emails between them without creating  aditional connector, unless you placed the new server under different routing group.
regarding to the error you are recieving , please refer to the following MS article which explains the solution for your

problem:
http://support.microsoft.com/kb/905813/en-us

Navigate to;
C:\Documents and Settings\%username%\Local Settings\ApplicationData\Microsoft\Outlook

Here remove all oab-files. Then start Outlook and see if it still happens.

Deleting all of the OAB files really should not be done until we understand what the nature of the problem is.  0X8004010F is a very generic error and means  MAPI_E_NOT_FOUND.
What type of profile are you using? Cached, online, etc?

This can happen if the information store they are now residing on is not associated with a Default Offline Address List. There are keys that get populates on the server side and the clients will rely on this information
so they can find the Offline Address List.

See if the new information store has an offline address list associated with it. This can be done from the properties of the Exchange Server's Mailbox Store Tab. You can also create a new profile on another system to see if this works. Some times this data gets cached and we are unable to look in the correct locations.

3..If  you tried to delete the outlook profile and recreate it.  First try using this profile update utility for Cross Admin Group / Site migrations.  
http://support.microsoft.com/kb/873214/en-us

Now, it seems that something wrong happened in your installation, what I prefer you to do is the following:

1. Migrate all the mailboxes from your new exchange server to the old exchange server.
2. Transfer any public folders or system folders data that are hosted by the new exchange server to the old exchange server, or you can remove the public and system folder replica for the new exchange server.
3. Uninstall exchange server 2003 from the new exchange server.
4. Use ADSIEDIT utility to make sure that the new exchange server was removed successfully from your exchange organization.
5. Reinstall exchange server on the new server, and this time, run setup only from the CD, and install exchange server under the current exchange organization.
6. After the successful installation of exchange, move your mailbox to the new exchange server and test mail connectivity between the two servers, you should not face any problem.
7. Transfer another few mailboxes to the new exchange server, then test the mail connectivity as well.
8. Move the other mailboxes to the new exchange server.

Hi bpatlen -

Yes you are right and I have already tell about this see my comment

Hi Mr. Paawan,

I have also advise about this see my reply :
------------------------------------------------------
Are you installing SMS 2003 with SP1 server then it not support SQL Server 2005. Only SMS 2003 SP2  Supports ??

http://www.microsoft.com/smserver/evaluation/sysreqs/default.mspx
-------------------------------------------------------

And also delshani tell about this see his reply.


So we want to explaination about this what wrong with our response.

Regarding SMS 2003 in this topic thread, ONLY SMS 2003 with SP2 can be installed on a Win server with SQL 2005 already running. However, until recently, this was only available in beta (RC2) but has now been released by Microsoft as product #271-02150. Unfortunately, it's not possible to slipstream SP2 onto SMS SP1 so doing this on a production machine really wasn't an option. Previously, the only way to get to SMS SP2 on SQL 2005 was via the upgrade path beginning with SQL 2000 not 2005. Then perform all the SMS upgrades to get it to the SP2 level and only then are you able to upgrade SQL 2000 to 2005. I should be receiving the latest SMS SP2 disk shortly and will see how well it installs on my SQL 2005 as it should without problems. Therefore, this should all be moot now that Microsoft has released the integrated SMS 2003 SP2 product to market making installs on SQL 2005 the preferred configuration.

B Patlen

Thanks Patlen. Will wait for reply.