x Want to participate? Join the group to interact
Options
  • State Suggested Answer
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 120 subscribers
  • Views 6023 views
  • Users 0 members are here
Browse Forums
Announcements
293
topics
370
replies
Business Object Interface
1k
topics
7k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
7k
replies
General Discussion
1k
topics
3k
replies
Partner Cloud
45
topics
92
replies
Payroll, Time Tracking, and Job Cost
777
topics
1k
replies
Reporting and Analytics
963
topics
3k
replies
Sage CRM for Sage 100
164
topics
357
replies
Technical and Installation
2k
topics
9k
replies
Year-end Forum
89
topics
237
replies
roastbeast

"Logon Failed" error attempting to read Sage 100 ERP 2014 data using ASP.NET & IIS 8

SUGGESTED
Posted By

I have an ASP.NET 4.0 site running on IIS 8. The application pool is set to enable 32bit applications. I have created a 32bit DSN that accesses Sage 100 ERP 2014 data. It successfully returns tables when I test it. 

When I try to read any data from Sage I get this error:

Exception Details: System.Data.Odbc.OdbcException: ERROR [S0000] [ProvideX][ODBC Driver][PVKIO]Logon failed
ERROR [S0000] [ProvideX][ODBC Driver][PVKIO]Logon failed

I have also tried setting the application pool to not allow 32bit applications in combination with a 64bit version of the DSN and I get the same error.

The company I am using is set to allow external access and the user account is a Supervisor.

I have used DSN's to read Sage/MAS data many times in the past and have not had this issue. Is there something different about version 2014 or its driver?

 

Parents Reply Children
  • 0 in reply to gpierce
    SUGGESTED
    Unfortunately I was not able to find a solution in time and was forced to use a SQL Server instance to mirror the Sage data, then pulled from that. You can also used a linked server and query using that as well.
  • 0 in reply to gpierce

    I've got this scenario and the same error after an update last week. Did you ever find a solution?

  • 0 in reply to [email protected]
    jreynolds, if your message is addressed to me then no, I did not find a solution other than the one I referred to in my last post. I honestly don't think that there is a way to get this to work unless an update comes out for the odbc driver that addresses this issue.
  • 0 in reply to roastbeast
    It was for either of you. Do you have any information on setting up a linked server to the Mas database?
  • 0 in reply to [email protected]
    The solution I found may be something that was unique to my scenario. I have my website running on an isolated machine (the webserver), with it's own domain seperate from our internal domain. We punch through our firewall to gain access to the internal domain where the MAS installation is located. I could gain access to the MAS database from the webserver by using the ip address of the internal server where mas is located with a DSN. However, whenever I tried to access the BOI or the database from the actual website, using the standard application pool identity it didn't work. I googled around and found that if I used the same user name AND password, in the application pool identity, it would work. Sure enough, I tried it and it did. For example, my application pool identity could be WebServer/Joe with a password of 123456 and as long as my internal domain network was the same (InternalDomain/Joe with a password of 123456) it would work. Craziest thing I have seen in a while, but it's all up and running. Not sure if this will help in your scenario. Also, I found that queries to MAS not through the BOI, but standard database queries were extremely slow and killing the speed on my site. I ended up doing a nightly copy of the MAS tables I reference in the site over to SQL server on the webserver machine. It was much faster for me.
  • 0 in reply to gpierce
    SUGGESTED
    Thanks! This is what we did and it fixed the problem. We switched the app pool to run under a named account.

*Community Hub is the new name for Sage City