Error 26

Have a Server 2005 network that we added two new computers to. The new computers are windows 7 and Primary is set up as a Raid1 with it's own network of server 2012. Computer2 was connected to Primary and a new reporting program functioned correctly. Once installed into the 2005 server, computer2 and another computer already in the network will not run the reporting system and return error 26.

I have already enabled sqlbrowser.exe, sqlserver.exe, and placed exceptions for ports 1433 and 1434 into both firewalls to ensure it isn't those issues.

Any other comments/tips that would clear this issue, besides it being a connection string in the program. The program was written solely for this Company and I am working with that code writer to see if any code issues.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Barry CunneyCommented:
What is reporting the error 26 - where are you seeing this error?
How does the reporting system connect to SQL Server - ODBC?
Where/How is the connection to SQL Server configured?
Is the SQL Server that the reporting system should connect to a named instance of SQL Server?
ddflavinAuthor Commented:
Seeing the error in a custom program called cashreg. It does the cash register reports using the reporting service.

it using the microsoft reporting service

it is configured in a connection string in the program for the program itself. Once computer is connected through server 2005.

and yes a named instance.
Barry CunneyCommented:
Is it possible to trap/extract the full error text in the custom program? - if we obtained the full text it may then be possible to fully confirm that it is SQL Server that is firing the error and this could help narrow down where we need to trace

When you mention Microsoft Reporting Service, is this SQL Server Reporting Services(SSRS)?

Is it possible to post up the connection string?

There is for example an error which can be returned by SQL server and could be the relevant error in your case
"SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified"

The following is a blog about this error

So if this is the same 'Error 26' that is occurring in your scenario, the first thing to verify would be the exact name/spelling of your  named SQL Server instance and what is specified in the connection string.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ddflavinAuthor Commented:
thanks for your help.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.