Hi,
I need to deploy code unit to web service and access it in my ASP.NET application. Issue is my Database is Native Database and not SQL Server and because of this event though all I did when i try to access web service it gives me error...
- <s:Envelope xmlns:s="
http://schemas.xmlsoap.org/soap/envelope/">
- <s:Body>
- <s:Fault>
<faultcode xmlns:a="urn:microsoft-dynamics-schemas/error">a:Microsoft.Dynamics.Nav.Types.Exceptions.NavNCLChangeListenerConnectionFailedException</faultcode>
<faultstring xml:lang="en-US">The Microsoft Dynamics NAV Server cannot connect the Change Listener to SQL Server due to the following error: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)</faultstring>
- <detail>
<string xmlns="
http://schemas.microsoft.com/2003/10/Serialization/">The Microsoft Dynamics NAV Server cannot connect the Change Listener to SQL Server due to the following error: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)</string>
</detail>
</s:Fault>
</s:Body>
</s:Envelope>
Can you tell me how to publish web service with native database? I can't switch over to SQL Server.
Hope to have quick update.
Thanks,
Bhavin Gajjar
Comments
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
In this case how do i call my code unit in to asp.net application?
Is there any alternative do this?
Job I have to perform is call code unit in asp.net page to insert data in to table. OR Provide me way so that I get input from ASP.NET page and insert into NAV DB. Database is Native Database and not SQL Server.
Thanks,
Bhavin
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
Has anyone worked with it? I am stuck on that too.
refer viewtopic.php?f=32&t=35730
Thanks,
Bhavin
I have got 50% success by using CFront.dll
Please refer viewtopic.php?f=32&t=35730
Thanks,
Bhavin
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
Yes, You are correct. But in case of NATIVE Database there is no support for Webservice yet. It works gr8 with SQL Server database but in my case I have Native database.
My Client not want to migrate with SQL Server Database so I have to do CFront.dll call and good thing is I did it finally.
I'll post it on my blog soon.
Thanks,
Bhavin Gajjar
I don't think we will ever see native database support for the service tier (incl. web services)
Group Program Manager, Client
Microsoft Dynamics NAV
http://blogs.msdn.com/freddyk
The information in this post is provided "AS IS" with no warranties, and confers no rights. This post does not represent the thoughts, intentions, plans or strategies of my employer. It is solely my opinion.
Well, You are true. But finally Client is king and we are service provider. He don't want to buy SQL Server and because of that I have worked on CFront.dll calling in ASP.NET as of now. I am trying hands on MSMQ and develop webservice to call CodeUnit so that we get benefit of NAV BL on native database.
Thanks,
Bhavin
Group Program Manager, Client
Microsoft Dynamics NAV
http://blogs.msdn.com/freddyk
The information in this post is provided "AS IS" with no warranties, and confers no rights. This post does not represent the thoughts, intentions, plans or strategies of my employer. It is solely my opinion.
Sometimes though that can be completely the wrong attitude, and what you call a service may in fact be a diss-service to your client.
Take a read of my blog about this:
The most powerful tool that a Dynamics NAV consultant can use
Ultimately there is a very good chance that the client will switch to SQL at some time. SO if you really want to provide a service to them, you will look at the cost of moving to SQL; then look at the cost ot write all this code, and the cost to keep supporting it; and the cost of the next upgrade; then add in all the oher benefits of moving to SQL.; if the client is about to start this integration job, then consider what else they might use from SQL and in the end you may find that its actually cheaper to use Web services on SQL than developing a hack.
You should never take the attitude that the customer is king, and just do anything they want. Allways present them with the options and let them make an informed decision.