Stephan Busch

Erstellte Forenantworten

15 Beiträge anzeigen - 1 bis 15 (von insgesamt 23)
1 2
  • Autor
    Beiträge
  • 6. Februar 2025 um 17:03 als Antwort auf: E-Mail-Postfach wird nicht angezeigt #6809
    Stephan Busch
    Participant

    Leider alle Schritte der Doku schon x-mal durchgeprüft…
    Auch mit Neu Anlage und anschließendem Neustart. nach Neustart ist das Postfach nicht mehr da.
    Bei Refresh der Postfächer kommt:

    Keine Verbindung zum Mailserver: failed to connect, no password specified?

    Password stimmt.

    6. Februar 2025 um 15:24 als Antwort auf: E-Mail-Postfach wird nicht angezeigt #6807
    Stephan Busch
    Participant

    Moin,
    leider habe ich das gleiche Problem.
    Wie konnte es für euch gelöst werden?
    Postfach erscheint nicht unter E-Mails und folgende Fehler:
    Server:
    2025-02-06 15:13:42,895 ERROR [com.jdimension.jlawyer.services.EmailService] (default task-35) Refresh token is empty when updating access token for stephan.busch@bb.partners

    client:
    2025-02-06 09:13:43,195 ERROR [com.jdimension.jlawyer.client.mail.EmailInboxPanel] Unable to load mailbox stephan.busch@bb.partners
    java.lang.IllegalStateException: Not connected
    at com.sun.mail.imap.IMAPStore.checkConnected(IMAPStore.java:1983) ~[javax.mail-1.6.2.jar:1.6.2]
    at com.sun.mail.imap.IMAPStore.getFolder(IMAPStore.java:1760) ~[javax.mail-1.6.2.jar:1.6.2]
    at com.jdimension.jlawyer.client.mail.EmailInboxPanel.refreshFolders(EmailInboxPanel.java:1000) ~[j-lawyer-client.jar:?]
    at com.jdimension.jlawyer.client.mail.EmailInboxPanel.<init>(EmailInboxPanel.java:865) ~[j-lawyer-client.jar:?]
    at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[?:?]
    at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:77) ~[?:?]
    at jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[?:?]
    at java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:499) ~[?:?]
    at java.lang.reflect.ReflectAccess.newInstance(ReflectAccess.java:128) ~[?:?]
    at jdk.internal.reflect.ReflectionFactory.newInstance(ReflectionFactory.java:347) ~[?:?]
    at java.lang.Class.newInstance(Class.java:645) ~[?:?]
    at com.jdimension.jlawyer.client.editors.EditorsRegistry.getEditor(EditorsRegistry.java:707) ~[j-lawyer-client.jar:?]
    at com.jdimension.jlawyer.client.SplashThread.lambda$preloadEditors$6(SplashThread.java:1185) ~[j-lawyer-client.jar:?]
    at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:308) ~[?:?]
    at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:773) ~[?:?]
    at java.awt.EventQueue$4.run(EventQueue.java:720) ~[?:?]
    at java.awt.EventQueue$4.run(EventQueue.java:714) ~[?:?]
    at java.security.AccessController.doPrivileged(AccessController.java:399) ~[?:?]
    at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86) ~[?:?]
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:742) ~[?:?]
    at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203) ~[?:?]
    at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124) ~[?:?]
    at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113) ~[?:?]
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109) ~[?:?]
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) ~[?:?]
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:90) ~[?:?]

    15. Januar 2025 um 12:00 als Antwort auf: Nach Server Umzug kein Login mehr möglich #6707
    Stephan Busch
    Participant

    ok sagt mir bedingt etwas….

    Hier die auth.log der letzte versuche. scheinen in ordnung.
    2025-01-14T07:10:10.964290+01:00 bbp systemd-logind[774]: New session 6 of user root.
    2025-01-14T07:10:18.155441+01:00 bbp sshd[1712]: pam_unix(sshd:session): session closed for user root
    2025-01-14T07:10:18.158848+01:00 bbp systemd-logind[774]: Session 6 logged out. Waiting for processes to exit.
    2025-01-14T07:10:18.159338+01:00 bbp systemd-logind[774]: Removed session 6.
    2025-01-14T07:10:20.471374+01:00 bbp (sd-pam): pam_unix(systemd-user:session): session closed for user lawyer

    Hier die Fehler der console.log aus dem j-lawyer verz.

    [0m[31m07:09:39,223 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool — 81) MSC000001: Failed to start service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU“: org.jboss.msc.service.StartException in service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU“: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:199)
    at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:129)
    at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
    at org.wildfly.security.elytron-base@1.19.1.Final//org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:664)
    at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:214)
    at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
    at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
    at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
    at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
    at java.base/java.lang.Thread.run(Thread.java:840)
    at org.jboss.threads@2.4.0.Final//org.jboss.threads.JBossThread.run(JBossThread.java:513)
    Caused by: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    at org.hibernate@5.3.28.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.persistenceException(EntityManagerFactoryBuilderImpl.java:1327)
    at org.hibernate@5.3.28.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:1253)
    at org.hibernate.jipijapa-hibernate5-3@26.1.3.Final//org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
    at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:171)
    … 10 more
    Caused by: org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing table [assistant_config]
    at org.hibernate@5.3.28.Final//org.hibernate.tool.schema.internal.AbstractSchemaValidator.validateTable(AbstractSchemaValidator.java:121)
    at org.hibernate@5.3.28.Final//org.hibernate.tool.schema.internal.GroupedSchemaValidatorImpl.validateTables(GroupedSchemaValidatorImpl.java:42)
    at org.hibernate@5.3.28.Final//org.hibernate.tool.schema.internal.AbstractSchemaValidator.performValidation(AbstractSchemaValidator.java:89)
    at org.hibernate@5.3.28.Final//org.hibernate.tool.schema.internal.AbstractSchemaValidator.doValidation(AbstractSchemaValidator.java:68)
    at org.hibernate@5.3.28.Final//org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.performDatabaseAction(SchemaManagementToolCoordinator.java:191)
    at org.hibernate@5.3.28.Final//org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.process(SchemaManagementToolCoordinator.java:72)
    at org.hibernate@5.3.28.Final//org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:310)
    at org.hibernate@5.3.28.Final//org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:467)
    at org.hibernate@5.3.28.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:1250)
    … 12 more

    [0m[31m07:09:39,239 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation („deploy“) failed – address: ([(„deployment“ => „j-lawyer-server.ear“)]) – failure description: {„WFLYCTL0080: Failed services“ => {
    „jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU\““ => „javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    Caused by: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    Caused by: org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing table [assistant_config]“,
    „jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU\““ => „javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    Caused by: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    Caused by: org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing table [assistant_config]“
    }}
    [0m[0m07:09:39,287 INFO [org.jboss.as.server] (ServerService Thread Pool — 46) WFLYSRV0010: Deployed „j-lawyer-server.ear“ (runtime-name : „j-lawyer-server.ear“)
    [0m[0m07:09:39,318 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
    WFLYCTL0186: Services which failed to start: service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU“: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU“: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    WFLYCTL0448: 455 additional services are down due to their dependencies being missing or failed
    [0m[0m07:09:39,359 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
    [0m[31m07:09:39,362 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 26.1.3.Final (WildFly Core 18.1.2.Final) started (with errors) in 12412ms – Started 3488 of 4151 services (476 services failed or missing dependencies, 383 services are lazy, passive or on-demand) – Server configuration file in use: standalone.xml
    [0m[0m07:09:39,364 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
    [0m[0m07:09:39,364 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
    [0m

    15. Januar 2025 um 12:00 als Antwort auf: Nach Server Umzug kein Login mehr möglich #6708
    Stephan Busch
    Participant

    die console.log aus dem j-lawyer verzeichnis zeigt fehler:

    [0m[31m07:09:39,223 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool — 81) MSC000001: Failed to start service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU“: org.jboss.msc.service.StartException in service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU“: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:199)
    at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:129)
    at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
    at org.wildfly.security.elytron-base@1.19.1.Final//org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:664)
    at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:214)
    at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
    at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
    at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
    at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
    at java.base/java.lang.Thread.run(Thread.java:840)
    at org.jboss.threads@2.4.0.Final//org.jboss.threads.JBossThread.run(JBossThread.java:513)
    Caused by: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    at org.hibernate@5.3.28.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.persistenceException(EntityManagerFactoryBuilderImpl.java:1327)
    at org.hibernate@5.3.28.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:1253)
    at org.hibernate.jipijapa-hibernate5-3@26.1.3.Final//org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
    at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:171)
    … 10 more
    Caused by: org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing table [assistant_config]
    at org.hibernate@5.3.28.Final//org.hibernate.tool.schema.internal.AbstractSchemaValidator.validateTable(AbstractSchemaValidator.java:121)
    at org.hibernate@5.3.28.Final//org.hibernate.tool.schema.internal.GroupedSchemaValidatorImpl.validateTables(GroupedSchemaValidatorImpl.java:42)
    at org.hibernate@5.3.28.Final//org.hibernate.tool.schema.internal.AbstractSchemaValidator.performValidation(AbstractSchemaValidator.java:89)
    at org.hibernate@5.3.28.Final//org.hibernate.tool.schema.internal.AbstractSchemaValidator.doValidation(AbstractSchemaValidator.java:68)
    at org.hibernate@5.3.28.Final//org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.performDatabaseAction(SchemaManagementToolCoordinator.java:191)
    at org.hibernate@5.3.28.Final//org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.process(SchemaManagementToolCoordinator.java:72)
    at org.hibernate@5.3.28.Final//org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:310)
    at org.hibernate@5.3.28.Final//org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:467)
    at org.hibernate@5.3.28.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:1250)
    … 12 more

    [0m[31m07:09:39,239 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation („deploy“) failed – address: ([(„deployment“ => „j-lawyer-server.ear“)]) – failure description: {„WFLYCTL0080: Failed services“ => {
    „jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU\““ => „javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    Caused by: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    Caused by: org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing table [assistant_config]“,
    „jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU\““ => „javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    Caused by: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    Caused by: org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing table [assistant_config]“
    }}
    [0m[0m07:09:39,287 INFO [org.jboss.as.server] (ServerService Thread Pool — 46) WFLYSRV0010: Deployed „j-lawyer-server.ear“ (runtime-name : „j-lawyer-server.ear“)
    [0m[0m07:09:39,318 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
    WFLYCTL0186: Services which failed to start: service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU“: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU“: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    WFLYCTL0448: 455 additional services are down due to their dependencies being missing or failed
    [0m[0m07:09:39,359 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
    [0m[31m07:09:39,362 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 26.1.3.Final (WildFly Core 18.1.2.Final) started (with errors) in 12412ms – Started 3488 of 4151 services (476 services failed or missing dependencies, 383 services are lazy, passive or on-demand) – Server configuration file in use: standalone.xml
    [0m[0m07:09:39,364 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
    [0m[0m07:09:39,364 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
    [0m

    17. November 2024 um 03:38 als Antwort auf: Anzeigenname wird im Sysem nicht wieder gegeben #6539
    Stephan Busch
    Participant

    der mehrwert liegt darin, dass wir zwei instanzen betreiben und ich anhand des anzeigenamens sehen möchte, wer auf welcher instant arbeitet.
    verstehe dassses lange her ist das wir darüber sprachen, aber du hattest mal angedeutet es einbauen zu wollen.
    wäre sehr hilfreich bei uns.

    17. November 2024 um 03:35 als Antwort auf: Individualisierung des Design #6538
    Stephan Busch
    Participant

    Auf dem Desktop wäre schön. Dort wird der name oben rechts angezeigt. leider nciht der Anzeigename.
    und daslogobzw favicon zu öndern wäre auch schon hilfreich.danke

    22. Februar 2024 um 16:50 als Antwort auf: Speichern von Emails – Trennung von Anlagen und E-Mails findet nicht statt #5897
    Stephan Busch
    Participant

    Fehler entdeckt. Mandant hat Bilder in der Mail die 3 bis 4 MB groß sind. Dann sind selbst Mails ohne Anlage recht üppig.

    Danke

    22. Februar 2024 um 01:29 als Antwort auf: Problem beim Anlegen Office 365 Mail #5890
    Stephan Busch
    Participant

    Das Server log gibt folgendes aus:

    2024-02-21 17:04:53,508 WARNING [javax.mail] (default task-2861) expected resource not found: /META-INF/javamail.default.address.map
    2024-02-21 17:04:54,463 INFO [com.jdimension.jlawyer.services.SingletonService] (Timer-7) directory observation is switched off
    2024-02-21 17:05:00,491 INFO [stdout] (default task-2861) DEBUG: setDebug: JavaMail version 1.6.2
    2024-02-21 17:05:00,492 INFO [stdout] (default task-2861) DEBUG: getProvider() returning javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Oracle]
    2024-02-21 17:05:00,492 INFO [stdout] (default task-2861) DEBUG IMAPS: mail.imap.partialfetch: false
    2024-02-21 17:05:00,492 INFO [stdout] (default task-2861) DEBUG IMAPS: mail.imap.ignorebodystructuresize: false
    2024-02-21 17:05:00,492 INFO [stdout] (default task-2861) DEBUG IMAPS: mail.imap.statuscachetimeout: 1000
    2024-02-21 17:05:00,493 INFO [stdout] (default task-2861) DEBUG IMAPS: mail.imap.appendbuffersize: -1
    2024-02-21 17:05:00,493 INFO [stdout] (default task-2861) DEBUG IMAPS: mail.imap.minidletime: 10
    2024-02-21 17:05:00,493 INFO [stdout] (default task-2861) DEBUG IMAPS: enable STARTTLS
    2024-02-21 17:05:00,493 INFO [stdout] (default task-2861) DEBUG IMAPS: enable SASL
    2024-02-21 17:05:00,493 INFO [stdout] (default task-2861) DEBUG IMAPS: SASL mechanisms allowed: XOAUTH2
    2024-02-21 17:05:00,493 INFO [stdout] (default task-2861) DEBUG IMAPS: closeFoldersOnStoreFailure
    2024-02-21 17:05:00,506 INFO [stdout] (default task-2861) DEBUG IMAPS: protocolConnect returning false, host=outlook.office365.com, user=stephan.busch@bb.partners, password=<null>

    die einstellung kann beim test senden, aber nicht empfangen.

    • Diese Antwort wurde vor vor 1 years, 1 months von Stephan Busch bearbeitet.
    2. November 2023 um 13:37 als Antwort auf: Arbeiten mit mehreren Monitoren #5747
    Stephan Busch
    Participant

    Moin,

    du bist witzig. mache ich ja gerne, aber wie ich zwei monitore recorde ist jetzt nciht ganz so einfach.

    das problem besteht weiter fort. ganz uebel, wenn ich in bea ein EB eingeben will und die j-law app im nebenmonitor laeuft, dann geht ein popup fuer den kalender auf dem hauptmonitor auf und ich kann es weder schliessen, noch das datum bearbeiten. auch reagiert dann j-law app nicht mehr. ich kann nur noch ueber task manager die app schliessen neu aufbauen und muss dann das app fenster im hauptfenstere oeffnen damit das popup ueber der app steht. dann kann ich auf das popup zugreifen. sobald app und popup auf unterschiedlichen monitoren aufgerufen werden, tritt das problem auf.

    hauptmonitor = ueber display einstelllungen win 11 der Main Display

    10. Oktober 2023 um 15:30 als Antwort auf: Logik der Tickets #5655
    Stephan Busch
    Participant

    Danke
    Etiketten sind abboniert. keine Anzeige.
    Berechtigung ist auch gegeben, keine Anzeige.
    Wir testen nochmal, eventuell haeben wir was uebersehen.

    10. Oktober 2023 um 15:09 als Antwort auf: Finanzen – Beleg Daten in Dokument uebernehmen #5652
    Stephan Busch
    Participant

    Perfekt Danke

    10. Oktober 2023 um 15:06 als Antwort auf: Arbeiten mit mehreren Monitoren #5651
    Stephan Busch
    Participant

    teilweise klickbar und teilweise nicht.
    nicht klickbar bei Finanzen>Beleg>Rechnung>Datumsauswahl

    10. Oktober 2023 um 15:03 als Antwort auf: Logik der Tickets #5650
    Stephan Busch
    Participant

    Tickets = Etiketten.

    7. Mai 2022 um 15:35 als Antwort auf: kein zugang nach update auf 2.1 #4962
    Stephan Busch
    Participant

    Moin,

    stimmt! Das statement konnte korrigiert werden. Dann ging es.
    nach dem start des jlawyer server ging es nicht. aber nach reboot des servers dann doch!

    Danke Jens wie immer großartige Hilfe.
    LG
    Stephan

    6. Mai 2022 um 21:01 als Antwort auf: kein zugang nach update auf 2.1 #4960
    Stephan Busch
    Participant

    Stement auf Terminal in mysql> ausgeführt:
    ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‚.11′‘ at line 1

    Mysql version 8.0.29

  • Autor
    Beiträge
15 Beiträge anzeigen - 1 bis 15 (von insgesamt 23)
1 2