Hi Rupert,
in the netzmuehle.solrindex.ref file i have following values:
#Thu Feb 09 17:38:21 CET 2012
Description=short description (http\://www.example.org)
Synchronized=true
Server-Name=default
Name=SolrIndex for netzmuehle
Index-Archive=netzmuehle.solrindex.zip
Directory=netzmuehle-2012.02.09
Index-Name=netzmuehle
State=ACTIVE
Archive=netzmuehle.solrindex.zip
In the bundles tab the index is marked as active but in my configuration
tab the index is still missing. I can only add a new keyword linking
engine but the existing one is shown shown.
Could there be a problem with writing grants on a special directory?
Best,
Martin
Hi Martin
Can you please try to reproduce this with the log level to debug and
provide the loggings and the index configuration.
For the logs the best would be to
1. delete all previous log files in "{stanbol-home}/sling/logs" and
2. adding the "-l DEBUG" option when starting Stanbol to also get
debug level loggings
Regarding the index configuration there are also some additional files
in the persistent store of the ManagedSolrServerBundle.
To locate this files you need to
1. use the Bundles tab of the Apache Felix Web Console
(http://{host}/system/console/bundles)
2. searching for "org.apache.stanbol.commons.solr.managed" to get the
Bundle ID (the number in the first column)
3. go to
{stanbol-home}/sling/felix/bundle{id}/data/.config/index-config/{server-pid}/
{id} ... the bundle ID as provided in step 2
{server-pid} ... there should be only a single directory. If there are
several this can already indicate an issue.
Within this directory there should be a "netzmuele.solrindex.ref" with
the configuration and state of this index.
best would be to create an archive of the whole /index-config
directory. Even better would be to create one before you start the
Stanbol Server and one afterwards when the problem occurs.
best
Rupert
On Fri, Feb 10, 2012 at 12:45 PM, Netzmühle Internetagentur OG
<[email protected]> wrote:
Hi Rupert,
yesterday everything was fine while using my own index. Then i stopped the
service and after starting it today again know i have the problem that my
index doesn't work.
In the Configuration Tab the Keyword Linking Engine was not registered
anymore and when i try to add a new keyword linking engine than stanbol
can't enhance my texts.
In the bundles tab the netzmuehle index is still active.
Best,
Martin
On Wed, Feb 8, 2012 at 7:04 PM, Netzmühle Internetagentur OG
<[email protected]> wrote:
Can you please re-install Stanbol (just delete everything other than
the launcher jar within the {stanbol-home})
When i delete everything without the launcher how can i re-install
stanbol?
Is this another option instead of checking out the svn version and using
mvn
clean install?
Yes. The first time you start the launcher jar stanbol is initialized
with the default configuration. So deleting all files - other than the
lauchner jar - does have the same effect.
Calling
mvn clean
svn up
mvn install
is only required if you want to upgrade to the current Stanbol version.
best
Rupert
and than restart stanbol with DEBUG level logging
jar -jar {laincher} -l DEBUG
1) copy the netzmuele.solrindex.zip to the data files directory
2) install the netzmuele bundle
3) try to make a query to
http://192.168.1.5:8080/entityhub/site/netzmuele/find
and provide the log (best as attachment to an JIRA issue)
This should help to track down the issue you are facing
best
Rupert
best,
Martin
Hi
That's strange. On the one hand the bundle should be "Active" and not
"Resolved" (Aufgelöst). So this might be the cause for that issue. On
the other hand the fact that there is a ReferencedSite /netzmuehle
indicates that the Bundle was at least "Active" at some time.
You can try to remove and install/start it again. If you do not enable
"Start Bundle" in the Install dialog you will need to start the bundle
manually after installing.
It would be also interesting to know if can you access the Solr
RESTful API for "netzmuehle" under
http://192.168.1.5:8080/solr/default/netzmuehle/select?q=*:*
best
Rupert
On Wed, Feb 8, 2012 at 3:36 PM, Netzmühle Internetagentur OG
<[email protected]> wrote:
Hi
the netzmuehle.solrindex.zip file ic also in the datafiles directory
and
i
tried to intstall the *.jar file as bundle but the result is still
the
error
message with yard index problem.
In the bundle section the Netzmuehle Index is registered with this
information (the status is "Aufgelöst" and when i can't start it):
Apache Stanbol Data:
netzmuehleorg.apache.stanbol.data.site.netzmuehle
<http://192.168.1.5:8080/system/console/bundles/139>
Symbolischer Name org.apache.stanbol.data.site.netzmuehle
Version 1.0.0
Bundle Location
inputstream:org.apache.stanbol.data.site.netzmuehle-1.0.0.jar
Letzte Bundle Status Änderung Wed Feb 08 15:27:21 CET 2012
Vendor Apache Stanbol (Incubating)
Beschreibung Bundle created for import of the referenced site
netzmuehle
into the Apache Stanbol Entityhub
Start Level 20
Exportierte Packages
org.apache.stanbol.data.site.netzmuehle,version=1.0.0
Importierte Packages None
Manifest Headers Bnd-LastModified: 1328263984870
Bundle-Category: Stanbol Data
Bundle-Description: Bundle created for import of the referenced site
netzmuehle into the Apache Stanbol Entityhub
Bundle-ManifestVersion: 2
Bundle-Name: Apache Stanbol Data: netzmuehle
Bundle-SymbolicName: org.apache.stanbol.data.site.netzmuehle
Bundle-Vendor: Apache Stanbol (Incubating)
Bundle-Version: 1.0.0
Created-By: 1.6.0_29 (Apple Inc.)
Export-Package: org.apache.stanbol.data.site.netzmuehle;
version="1.0.0"
Install-Path: org/apache/stanbol/data/site/netzmuehle
Manifest-Version: 1
Tool: Bnd-1.43.0
Hi
On Wed, Feb 8, 2012 at 3:05 PM, Netzmühle Internetagentur OG
<[email protected]> wrote:
Hi Rupert,
thx for your check list. When i tried number 6 i got following
message.
The
zip file for the index is available unter
{stanbol-home}/sling/datafiles
namely as org.apache.stanbol.data.site.netzmuehle-1.0.0.jar
The "org.apache.stanbol.data.site.netzmuehle-1.0.0.jar" needs to be
installed as bundle.
You need to copy the netzmuehle.solrindex.zip file to
"{stanbol-home}/sling/datafiles" instead.
Doing so should solve this. Note that the file should be
automatically
detected. The index should be available 5-10sec (assuming a size
<50MByte) later.
best
Rupert
error -<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1"/>
<title>Error 500 Unable to initialize the Cache with Yard
netzmuehleIndex!
This is usually caused by Errors while reading the Cache
Configuration
from
the Yard.</title>
</head>
<body><h2>HTTP ERROR 500</h2>
<p>Problem accessing /entityhub/site/netzmuehle/find. Reason:
<pre> Unable to initialize the Cache with Yard
netzmuehleIndex!
This is
usually caused by Errors while reading the Cache Configuration from
the
Yard.</pre></p><h3>Caused
by:</h3><pre>java.lang.IllegalStateException:
Unable to initialize the Cache with Yard netzmuehleIndex! This is
usually
caused by Errors while reading the Cache Configuration from the
Yard.
at
org.apache.stanbol.entityhub.core.site.CacheImpl.getCacheYard(CacheImpl.java:214)
at
org.apache.stanbol.entityhub.core.site.CacheImpl.findRepresentation(CacheImpl.java:331)
at
org.apache.stanbol.entityhub.core.impl.ReferencedSiteImpl.findEntities(ReferencedSiteImpl.java:282)
at
org.apache.stanbol.entityhub.jersey.resource.ReferencedSiteRootResource.executeLDPathQuery(ReferencedSiteRootResource.java:470)
at
org.apache.stanbol.entityhub.jersey.resource.ReferencedSiteRootResource.executeQuery(ReferencedSiteRootResource.java:412)
at
org.apache.stanbol.entityhub.jersey.resource.ReferencedSiteRootResource.findEntity(ReferencedSiteRootResource.java:356)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1465)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1396)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1345)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1335)
at
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416)
at
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:537)
at
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:699)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
org.apache.felix.http.base.internal.handler.ServletHandler.doHandle(ServletHandler.java:96)
at
org.apache.felix.http.base.internal.handler.ServletHandler.handle(ServletHandler.java:79)
at
org.apache.felix.http.base.internal.dispatch.ServletPipeline.handle(ServletPipeline.java:42)
at
org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:49)
at
org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33)
at
org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:78)
at
org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:47)
at
org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33)
at
org.apache.stanbol.commons.httpqueryheaders.impl.QueryHeadersFilter.doFilter(QueryHeadersFilter.java:75)
at
org.apache.felix.http.base.internal.handler.FilterHandler.doHandle(FilterHandler.java:88)
at
org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:76)
at
org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:47)
at
org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33)
at
org.apache.felix.http.base.internal.dispatch.FilterPipeline.dispatch(FilterPipeline.java:48)
at
org.apache.felix.http.base.internal.dispatch.Dispatcher.dispatch(Dispatcher.java:39)
at
org.apache.felix.http.base.internal.DispatcherServlet.service(DispatcherServlet.java:67)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390)
at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
at
org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:943)
at
org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756)
at
org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
at
org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
at
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
Caused by:
org.apache.stanbol.entityhub.servicesapi.yard.YardException:
The
SolrIndex 'netzmuehle' for SolrYard 'netzmuehle Index' is currently
not
active!
at
org.apache.stanbol.entityhub.yard.solr.impl.SolrYard.getServer(SolrYard.java:512)
at
org.apache.stanbol.entityhub.yard.solr.impl.SolrYard.getRepresentation(SolrYard.java:849)
at
org.apache.stanbol.entityhub.core.site.CacheUtils.loadBaseMappings(CacheUtils.java:54)
at
org.apache.stanbol.entityhub.core.site.CacheImpl.initWithCacheYard(CacheImpl.java:114)
at
org.apache.stanbol.entityhub.core.site.CacheImpl.getCacheYard(CacheImpl.java:210)
... 55 more
</pre>
<h3>Caused
by:</h3><pre>org.apache.stanbol.entityhub.servicesapi.yard.YardException:
The SolrIndex 'netzmuehle' for SolrYard 'netzmuehle Index' is
currently
not
active!
at
org.apache.stanbol.entityhub.yard.solr.impl.SolrYard.getServer(SolrYard.java:512)
at
org.apache.stanbol.entityhub.yard.solr.impl.SolrYard.getRepresentation(SolrYard.java:849)
at
org.apache.stanbol.entityhub.core.site.CacheUtils.loadBaseMappings(CacheUtils.java:54)
at
org.apache.stanbol.entityhub.core.site.CacheImpl.initWithCacheYard(CacheImpl.java:114)
at
org.apache.stanbol.entityhub.core.site.CacheImpl.getCacheYard(CacheImpl.java:210)
at
org.apache.stanbol.entityhub.core.site.CacheImpl.findRepresentation(CacheImpl.java:331)
at
org.apache.stanbol.entityhub.core.impl.ReferencedSiteImpl.findEntities(ReferencedSiteImpl.java:282)
at
org.apache.stanbol.entityhub.jersey.resource.ReferencedSiteRootResource.executeLDPathQuery(ReferencedSiteRootResource.java:470)
at
org.apache.stanbol.entityhub.jersey.resource.ReferencedSiteRootResource.executeQuery(ReferencedSiteRootResource.java:412)
at
org.apache.stanbol.entityhub.jersey.resource.ReferencedSiteRootResource.findEntity(ReferencedSiteRootResource.java:356)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1465)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1396)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1345)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1335)
at
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416)
at
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:537)
at
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:699)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
org.apache.felix.http.base.internal.handler.ServletHandler.doHandle(ServletHandler.java:96)
at
org.apache.felix.http.base.internal.handler.ServletHandler.handle(ServletHandler.java:79)
at
org.apache.felix.http.base.internal.dispatch.ServletPipeline.handle(ServletPipeline.java:42)
at
org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:49)
at
org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33)
at
org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:78)
at
org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:47)
at
org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33)
at
org.apache.stanbol.commons.httpqueryheaders.impl.QueryHeadersFilter.doFilter(QueryHeadersFilter.java:75)
at
org.apache.felix.http.base.internal.handler.FilterHandler.doHandle(FilterHandler.java:88)
at
org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:76)
at
org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:47)
at
org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33)
at
org.apache.felix.http.base.internal.dispatch.FilterPipeline.dispatch(FilterPipeline.java:48)
at
org.apache.felix.http.base.internal.dispatch.Dispatcher.dispatch(Dispatcher.java:39)
at
org.apache.felix.http.base.internal.DispatcherServlet.service(DispatcherServlet.java:67)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390)
at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
at
org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:943)
at
org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756)
at
org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
at
org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
at
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
</pre>
best
Martin
Hi Martin
Are you sure that there are no errors? The web interface usually
shows
the text "Invalid Query" in case of an error. The full stack trace
can
be found in the logs ({stanbol-home}/sling/logs/error.log).
Regardless of that this are the steps I usually perform to check
the
status of a "index" in case of problems.
1) go to RESTful API tab of "http//localhost:8080/entityhub"
2) check the the ReferencedSite for the new index present
3) Click on the link or directly go to
"http//localhost:8080/entityhub/site/{index}"
4) send "curl -H "Accept: application/rdf+xml"
"http://localhost:8080/entityhub/site/{index}"; or click to link at
the
bottom of the section "Referenced Site Metadata"
5) check for the triple
http://localhost:8080/entityhub/site/{index},
http://www.iks-project.eu/ontology/rick/model/localMode,
"true"^^xsd:boolean
6) Go to http://localhost:8080/entityhub/site/{index}/find and
search
for an term you know that is part of the index. Do not forget to
change the language and the field if necessary.
if:
2 fails -> this means the the configuration of the
ReferencedSite
was
not loaded -> this typically indicates that you have not
installed
the
bundle provided in the "indexing/dist" folder
4 fails -> this means that the configuration of the
ReferencedSite
was
not successful -> this is very unlikely and there should
be
some
errors in the log ({stanbol-home}/sling/log/error.log)
5 states that localMode= false : This means that the local index
was
not yet initialized -> this typically indicated that you
have
not
yet
copied the "{index}.solrindex.zip" file provided in the
"indexing/dist" folder to "{stanbol-home}/sling/datafiles"
6 fails: this is very unlikely if 1-5 where successful. See the
Errors
in the logs
6 does not return the expected data: This indicates that some
expected
information where not indexed correctly. You should try to go to
"http://localhost:8080/solr/default/{index}/select?q=*:*"; and
check
against the data returned by Solr
If steps 1-6 are successful, than a "KeywordLinkingEngine"
configured
for {index} should work just fine.
I hope this helps
best
Rupert
2012/2/7 "Netzmühle Internetagentur - Dipl.-Ing. (FH) Martin
Mayrhofer-Reinhartshuber"<[email protected]>:
Hello Rupert,
i tried to create a new index for the Keyword Linking Engine
following
the
online instructions. My Index is based on the Good Relations
Schemas.
It seemed that everything was alright until i tried to activate
the
engine.
I registered the engine in the felix console and the Default
Engine
Chain
recognized a new engine but when i tried to enhance an text i got
no
results
(and also no errors).
Is there a generell problem or did i something wrong during the
build
process of the index.
Best regards,
Martin Mayrhofer
--
Lernen Sie das sensationell neue Online-Shop-Konzept speziell
für kreative Jungunternehmer und erfolgreiche Lifestyle-Marken
kennen.
Mehr Informationen unter: www.neoshopia.eu
Netzmühle Internetagentur OG
Franz-Josef-Straße 24
5020 Salzburg
Österreich
Mobil: +43 676 / 66 05 919
Tel.: +43 662 / 21 66 99
Fax: +43 662 / 870 127-15
E-Mail: [email protected]
Web: www.netzmuehle.at
www.arzt-webdesign.com
www.neoshopia.eu
FB: www.facebook.com/netzmuehle
UID: ATU66097216
Firmenbuch: FN 355392 k
--
Lernen Sie das sensationell neue Online-Shop-Konzept speziell
für kreative Jungunternehmer und erfolgreiche Lifestyle-Marken
kennen.
Mehr Informationen unter: www.neoshopia.eu
Netzmühle Internetagentur OG
Franz-Josef-Straße 24
5020 Salzburg
Österreich
Tel.: +43 662 / 21 66 99
Fax: +43 662 / 870 127-15
E-Mail: [email protected]
Web: www.netzmuehle.at
www.arzt-webdesign.com
www.neoshopia.eu
FB: www.facebook.com/netzmuehle
UID: ATU66097216
Firmenbuch: FN 355392 k
--
Lernen Sie das sensationell neue Online-Shop-Konzept speziell
für kreative Jungunternehmer und erfolgreiche Lifestyle-Marken
kennen.
Mehr Informationen unter: www.neoshopia.eu
Netzmühle Internetagentur OG
Franz-Josef-Straße 24
5020 Salzburg
Österreich
Tel.: +43 662 / 21 66 99
Fax: +43 662 / 870 127-15
E-Mail: [email protected]
Web: www.netzmuehle.at
www.arzt-webdesign.com
www.neoshopia.eu
FB: www.facebook.com/netzmuehle
UID: ATU66097216
Firmenbuch: FN 355392 k
--
Lernen Sie das sensationell neue Online-Shop-Konzept speziell
für kreative Jungunternehmer und erfolgreiche Lifestyle-Marken kennen.
Mehr Informationen unter: www.neoshopia.eu
Netzmühle Internetagentur OG
Franz-Josef-Straße 24
5020 Salzburg
Österreich
Tel.: +43 662 / 21 66 99
Fax: +43 662 / 870 127-15
E-Mail: [email protected]
Web: www.netzmuehle.at
www.arzt-webdesign.com
www.neoshopia.eu
FB: www.facebook.com/netzmuehle
UID: ATU66097216
Firmenbuch: FN 355392 k
--
Lernen Sie das sensationell neue Online-Shop-Konzept speziell
für kreative Jungunternehmer und erfolgreiche Lifestyle-Marken kennen.
Mehr Informationen unter: www.neoshopia.eu
Netzmühle Internetagentur OG
Franz-Josef-Straße 24
5020 Salzburg
Österreich
Tel.: +43 662 / 21 66 99
Fax: +43 662 / 870 127-15
E-Mail: [email protected]
Web: www.netzmuehle.at
www.arzt-webdesign.com
www.neoshopia.eu
FB: www.facebook.com/netzmuehle
UID: ATU66097216
Firmenbuch: FN 355392 k
--
Lernen Sie das sensationell neue Online-Shop-Konzept speziell
für kreative Jungunternehmer und erfolgreiche Lifestyle-Marken kennen.
Mehr Informationen unter: www.neoshopia.eu
Netzmühle Internetagentur OG
Franz-Josef-Straße 24
5020 Salzburg
Österreich
Tel.: +43 662 / 21 66 99
Fax: +43 662 / 870 127-15
E-Mail: [email protected]
Web: www.netzmuehle.at
www.arzt-webdesign.com
www.neoshopia.eu
FB: www.facebook.com/netzmuehle
UID: ATU66097216
Firmenbuch: FN 355392 k
--
Lernen Sie das sensationell neue Online-Shop-Konzept speziell
für kreative Jungunternehmer und erfolgreiche Lifestyle-Marken kennen.
Mehr Informationen unter: www.neoshopia.eu
Netzmühle Internetagentur OG
Franz-Josef-Straße 24
5020 Salzburg
Österreich
Tel.: +43 662 / 21 66 99
Fax: +43 662 / 870 127-15
E-Mail: [email protected]
Web: www.netzmuehle.at
www.arzt-webdesign.com
www.neoshopia.eu
FB: www.facebook.com/netzmuehle
UID: ATU66097216
Firmenbuch: FN 355392 k
