There is no datasource with name

trying to connect using the same u/p in SQL Mgt Studio connects just fine but Lucee claims

there is no datasource with name

of course it is there so…

Lucee 5.3.6.53-RC Windows Server 2016 version 1607

Where is the datasource defined?

in the server admin so not in the code.

@Bill_Foresman, Did you check again the DS name what you’ve to used in your code is correct?

copy and paste plus caps lock

@Bill_Foresman, Could you please add an error stack trace or screenshot? If possible.

lucee.runtime.exp.ApplicationException: there is no datasource with name [pm_webcollect] at lucee.runtime.tag.Admin.doGetDatasource(Admin.java:3841) at lucee.runtime.tag.Admin._doStartTag(Admin.java:619) at lucee.runtime.tag.Admin.doStartTag(Admin.java:353) at services_datasource_create_cfm1334$cf.call(/admin/services.datasource.create.cfm:38) at lucee.runtime.PageContextImpl._doInclude(PageContextImpl.java:945) at lucee.runtime.PageContextImpl._doInclude(PageContextImpl.java:837) at lucee.runtime.PageContextImpl.doInclude(PageContextImpl.java:818) at services_datasource_cfm414$cf.call(/admin/services.datasource.cfm:108) at lucee.runtime.PageContextImpl._doInclude(PageContextImpl.java:945) at lucee.runtime.PageContextImpl._doInclude(PageContextImpl.java:837) at lucee.runtime.PageContextImpl.doInclude(PageContextImpl.java:818) at web_cfm$cf.call(/admin/web.cfm:467) at lucee.runtime.PageContextImpl._doInclude(PageContextImpl.java:945) at lucee.runtime.PageContextImpl._doInclude(PageContextImpl.java:837) at lucee.runtime.listener.ModernAppListener._onRequest(ModernAppListener.java:216) at lucee.runtime.listener.MixedAppListener.onRequest(MixedAppListener.java:42) at lucee.runtime.PageContextImpl.execute(PageContextImpl.java:2416) at lucee.runtime.PageContextImpl._execute(PageContextImpl.java:2406) at lucee.runtime.PageContextImpl.executeCFML(PageContextImpl.java:2381) at lucee.runtime.engine.Request.exe(Request.java:43) at lucee.runtime.engine.CFMLEngineImpl._service(CFMLEngineImpl.java:1127) at lucee.runtime.engine.CFMLEngineImpl.serviceCFML(CFMLEngineImpl.java:1073) at lucee.loader.engine.CFMLEngineWrapper.serviceCFML(CFMLEngineWrapper.java:97) at lucee.loader.servlet.CFMLServlet.service(CFMLServlet.java:51) at javax.servlet.http.HttpServlet.service(HttpServlet.java:741) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:541) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) at mod_cfml.core.invoke(core.java:161) at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:690) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:373) at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1590) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.base/java.lang.Thread.run(Unknown Source)

is there anything I can check to verify the installation was completed correctly? Just clicked next next and next but no errors. Admin functions so I suppose all is good…

@Bill_Foresman, I think your Datasource having ‘#’ symbol on Datasource name. If we use # in the name means, at that time the error will be thrown by lucee.

This post was flagged by the community and is temporarily hidden.

This post was flagged by the community and is temporarily hidden.

So any criticism of non-working software is labeled SPAM?

and I’m NOT using # in the datasource name

If you have defined the datasource in the server admin you should be able to VERIFY that its working correctly from that interface.

Can you send through a screenshot of the configuration?

@cfmitrah is referring to this scenario:
https://luceeserver.atlassian.net/browse/LDEV-2887

Can you re-edit the datasource in the admin?

of course I want it to verify - total fail!~

and STOP marking criticism as SPAM because it’s def NOT spam. This software should work just fine on a basic install and it does not.

As a developer you know that being able to reproduce and understand a problem is the key to resolving a problem.

If you don’t want to have you posts marked as SPAM, provide some constructive detail.

  • How does it fail?
  • is there a stack trace
  • what version of Lucee
  • what version of java
  • what database are you using
  • which database extension version are you using

You know, actionable detail, please re-read your posts before posting.

Ask yourself, how would you respond to your post, if you think you would respond by asking for further information, the add those details.

2 Likes

With all due respect, we developers all have good times but also bad times. We are a community providing help for free. We always want to help, because everyone of us had similar situations with a vast number of software. There are lots of big websites out there just doing that: Community contribution with software and programming problems.

Now we developers are here, taking our time, reading your posts to help you with your issues, not ours. If you are facing an issue, please don’t forget that. We are taking our time to help you. So please, I beg you to keep this in mind, and keep this negative energy out of our good flow of helping each other. What we as a community can sincerly expect is not to spread this energy here. If your threads get flagged, it has a reason. Other communities would have banned your account right away.

If you’re sending negativity, please consider that people in our community will also consider not taking our time helping you.

3 Likes

My comments regarding the software are well deserved considering this is the 3RD server in a row that the install failed and required “hacking” to correct. My comments are NOT directed to other developers nor those here that do not participate in the development of Lucee. How can server application software be written and repeatedly have installation issues?

On the latest version, there’s half a page devoted to MANUALLY getting it to install correctly. WHEN was Windows 2016 released? Exactly!

Lucee is an open source engine, not a commercial product. It is managed by a tiny team of developers (in contrast to most other actively developed open source projects) and, as many other open source projects, may require a bit of fiddling to get it working exactly how you want in your exact environment.

If this is unacceptable to you, might I suggest you look to commercially available engines instead.

Complaining about your experience while offering very little in the way of actionable information for those of us who want to help you doesn’t do anybody any good. Most of us feel and understand your frustration… I’m sure we’ve all been there a time or ten in our careers… and we’d very much like to help you succeed with an install of Lucee that you are happy with. However, in order to do that we’ll need additional information… including screen shots and other information as has been requested from you. Failure to provide us with the information we need makes helping you that much more difficult already… adding complaints that offer no actionable information further hampers the process.

If you would like help getting everything working as you would like, then provide us with the information we need to assist you. If you would rather simply complain about an open source (free) piece of software managed by a dedicated but small team of developers because it fails to meet your expectations… you’re welcome to do so… but it will not help you and will, ultimately, lead those of us who may be able to help you to simply ignore you altogether instead of wasting our time.

HTH

– Denny

5 Likes