web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Creating a Test environment

(0) ShareShare
ReportReport
Posted on by 12

Dear All,

I am building a test environment exact copy of live GP2013 R2.  I have done the following.

1) SQL server cloned exact copy of live SQL and name of the instance and IP address changed

2) New terminal server build (with same configuration of old terminal)

3) ODBC pointing to the new SQL test created on terminal

4) GP 2013 installed pointing to Test SQL server

5) Ran utilities on the new terminal 

Did I miss anything on the above.  When I went to Reporting tool setup - its showing the live SQL server and not test SQL server.  I tried to change but its not recognizing the new test SQL server.  When I login to GP there were 2 ODBC one which is connected to live SQL and one which I created to the test server.  I am not sure how the live server ODBC got in on the new terminal server.  So I removed that ODBC and kept my new ODBC  but when I login to GP the new ODBC is not showing up.  Can anyone help on this. 

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Tom Cruse Profile Picture
    1,477 on at

    Hey Babu,

    When you say that you cloned the SQL install, what do you mean? Did you do a clean install of SQL? what does the Reporting Services Configuration manager point to? Is there an active instance of the new SSRS?

    Trying to understand where the issue is. Is it Reporting Services or is the reporting services location URL location in GP set to the wrong URL. You can change that directly in GP. Can you access the new test environments SSRS site from the browser outside of GP?

    Again, just not exactly sure where the problem sits.

  • babubaskaran@outlook.com Profile Picture
    12 on at

    Hi Tom,

    Yes its new install of SQL but its just copy(clone) of the live SQL environment.  In this way I have a test environment which is exact copy of live environment.  Reporting service pointing to live SQL server.  I tried to change it GP but its says not valid.  I haven't tried SSRS site pointing to new SQL since its not even show up on GP.  Hope I am not confusing you :-) thanks in advance. 

  • Verified answer
    Tom Cruse Profile Picture
    1,477 on at

    :) Friday's are always confusing.

    So what I think you're saying is that you took a backup and restore of Live and dropped in into a Test Environment and now you can't change the SSRS URL in GP???

    On your new SQL Box navigate to Reporting Services Configuration Manager, login  and click on Web Service URL and find out where SSRS is point too. If you set it up with the default named instance then it should be something like http://<sqlserver>/ReportServer , this shouldn't be pointing to your live instance but instead whatever that Test server is?  I'm thinking this might be the problem, might not be but it's a place to start to at least verify that SSRS is active and running on your test server.

    2015_2D00_10_2D00_30_5F00_13_2D00_37_2D00_48.jpg

  • babubaskaran@outlook.com Profile Picture
    12 on at

    Thanks Tom I will check that and let you know.  What about I am not seeing the new ODBC when I luanch GP even I entered the sqlserver odbc name on dex.ini file.

  • Verified answer
    Tom Cruse Profile Picture
    1,477 on at

    Check your current ODBC System DSN's, what platform did you create the new one under? Is it 64 bit? Try creating it as a 32bit Data Source. I have the same problem when I create a 64bit ODBC vs. a 32bit ODBC, the 64bit doesn't show up in my drop-downs to select.

  • babubaskaran@outlook.com Profile Picture
    12 on at

    Hi Tom,

    I checked this and its pointing to Live server and not the test.  What will I do now, will I go to advanced and change the IP address.   Reg. ODBC i have set up 32 bit ODBC only.

  • Suggested answer
    Tom Cruse Profile Picture
    1,477 on at

    Ok let's try this as a test, create a new 32 bit odbc and call it 32 bit and map it to the test server.

    Then create a 64 bit odbc and call it 64 bit and map it to the test server.

    Now start up GP and see which one of these Shows up, either 32bit will show or 64bit will show as a selection. That way you'll know which one to create as the permanent one.

    I might be wrong but I'm guessing this might be the problem and I wouldnt hardcode the server in the dex.ini, I beleive you said you did that.

  • babubaskaran@outlook.com Profile Picture
    12 on at

    Hi Tom I will try this and let you know

  • Verified answer
    babubaskaran@outlook.com Profile Picture
    12 on at

    Hi Tom,

    Good news and thanks.  I did the following and all worked well so far.

    1) New ODBC 32 bit created and GP picked up (the old one I selected SQL server and not native 10.0)

    2) IP address changed reporting configuration manager and in web service URL tab and database tab both were pointing to live server

    3) Ran utilities and were able to login to all companies and no issues

    4) The live SSRS was pointing to test SQL so I changed the data source manually and its work fine.  (This might have happened when I ran utilities first time where the ODBC was pointing to live server)

    5) Deployed 2 companies on test SSRS and its work fine.

    So all look ok for the moment, let me know whether I have to check anything else which might affect live server (I just worried about this).  All this happened because of cloning the live SQL server instead of restoring the database alone to new SQL server.

  • Tom Cruse Profile Picture
    1,477 on at

    Hey that's great news Babu!

    It sounds like you've tested everything out thoroughly. As long as the test server logs into test SQL instance and transactions update there and not PROD and as long as SSRS works then I think you're good to go. I can't think of anything else.

    The only thing last thing to check would be if there were any customizations made where a stored proc had the actual server hardcoded in the procedure, I highly doubt this but I've seen it happen. As long as you don't have PROD or TEST setup as linked servers then at the very most the procedures will just fail.

    Congrats

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans