(877) 456-7632 info@msxgroup.com
Message Boards
Sign up Latest Topics
 
 
 


Reply
  Author   Comment  
fuadbinazeez

Registered:
Posts: 2
Reply with quote  #1 
Hello All,

While connecting forecaster (SP3) from windows 8 user machine , it shows an message as below:

Connection test unsuccessful. 

Ideally this error will show once the user id is not mapped in  forecaster DB/ server.
We already ensured the db mapping, pre requisite installation at client machine. User is able to connect the application from any other machines with same OS. So i suspect it's an issue in Windows OS side for the particular machine.

We uninstalled the Antivirus and firewall was disabled.

Please let me know if any resolution available for this burning issue.

Regards
Fuad
Rob.Diaz

Moderator
Registered:
Posts: 88
Reply with quote  #2 
Hi Fuad,

If the connection test is failing, the issue is related to connectivity to the server. Typically, this will be due to missing pre-requisites or an inability to connect to the database server. 

Is this a 64-bit Windows 8 machine?  Please ensure that you have followed the instructions in this post: http://boards.msxgroup.com/post/installing-microsoft-forecaster-7-0-on-64bit-operating-systems-4920746?pid=1281019959#post1281019959

I'd suggest re-installing the pre-requisites from the above link even if you've done it before, to make sure all components have been updated. If that doesn't work immediately, you will need to try to connect to the SQL Server via another tool like SQL Management Studio or even Excel -- any tool that uses the SQL Server Native Client to connect.

When the pre-requisites are installed properly, Forecaster's connection to the database server is usually very simple and straightforward.  There are rare instances where an IP address, DCHP or DNS issue can cause problems.

Rob Diaz
MSX Group
Microsoft Forecaster Support

__________________
Rob Diaz
MSX Group
http://www.msxgroup.com
fuadbinazeez

Registered:
Posts: 2
Reply with quote  #3 
Hi Rob Diaz,

Thanks for your reply. I already verified the inline KB link.

As suggested , i have re-installed pre requisites such as sqlncli  & SQLServer2005_XMO .

As verified the machine, it having an DCS application which using SQL native client . So there might be a chance of conflicts.
Suspected that native client needs some patch updates.

Regards
Fuad Ahmed
Rob.Diaz

Moderator
Registered:
Posts: 88
Reply with quote  #4 
Well, most sqlncli applications can be installed side-by-side. So if Forecaster cannot connect to the server but something else can connect to the same server and database, the issue may be different. 

What version of SQL Server are you attempting to connect to?  If it is 2008 or 2012, you could try installing the 2008/2012 versions of the sqlncli, SMO and CLR types (I've got a link here for the 2008 versions:  http://boards.msxgroup.com/post/microsoft-forecaster-7-sp5-has-a-prerequisite-change-6438531?pid=1278818573#post1278818573

The kb article referenced here specifically relates to Forecaster SP5, but the SQL 2008 bits are the same either way. 

I think the key issue is to confirm connectivity from this particular workstation to that server, though.  Windows 8 is fine with Forecaster 7 SP3, and you said other workstations configured this way are working properly, so I suspect the issue is a specific configuration difference on this workstation.  Unfortunately, the only good way to resolve situations like this are trial-and-error.

__________________
Rob Diaz
MSX Group
http://www.msxgroup.com
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.