Hi Aamir,
There are some very specific steps that need to be followed to fully replicate a system.
Here is a quick overview:
1. gather the following from the source system:
- site\mods zipped up
- backup of MDB database
- attachments directory (wherever you are storing it - by default its site\attachments)
2. on target system, install SDM and patch to the same level as production
3. restore the MDB database from the backup you took in step 1
4. run sql script to fix the orphaned SQL user (which should be mdbadmin or servicedesk depending on the version of SDM you are using) (your DBA can assist with this part if you are not familiar with it)
4. go into WSP Schema Designer and make a "dummy update" such as adding an "X" to the description field (in the content section on the right) for any table, then go to File > Save, then remove the "X" and go to File > Save and Publish
5. stop SDM services
6. run pdm_publish (this will build the proper schema files)
7. copy mods, and attachments directory that you gathered from step 1, into place on the target system
8. run pdm_configure
You should be good to go with a running replica.
NOW, since you have already done most of these steps, to fix this in your environment, you should be able to just do the following steps:
1. go into WSP Schema Designer and make a "dummy update" such as adding an "X" to the description field (in the content section on the right) for any table, then go to File > Save, then remove the "X" and go to File > Save and Publish
2. stop services
3. run pdm_publish
4. copy the mods in place from the source system
5. run pdm_configure
You should be good to go.
Hope this helps.
Thanks,
Jon I.