I try to install optisystem 7 or 10 on my computer after the 7 days evaluation finished, so i made windows formatting and install new windows although the program can't be run and each time says that the license is not available ,can any one help me to solve that problem
It is possible that your PC has been registered in their database as having been used to run a trial version before, and hence no further trial period is granted for that particular PC. You may also have been sent a trial code to your email address, so that you can not active a new trial using the same email address. I guess you can try to install the product on a different machine or get a new trial code sent to a different email address.
In essence the software is probably working as expected with regards to the trial period, but you didn't get to finish your testing phase within the time limit.
Related
I do laptop provisioning at home and something I use at the end is the DJOIN.exe command so the laptops will be ready for use when connecting on our offices' network.
Typically if I want to do an offline domain join, I will use:
DJOIN /REQUESTODJ /LOADFILE .\[filename] /WINDOWSPATH C:\windows /LOCALOS
On most laptop models this will execute fine and allow users to login to their Windows accounts once they're on the office network. I'm working with a new model today (thanks supply chain issues!) and even though it is also running Windows 10, I am getting the error message:
/LOCALOS specified but the current OS does not support domain join functionality.
The request is not supported.
Doing a google search for that exact message shows there are no results and most of the other results aren't for offline joining specifically as they include steps on the DC side of things -- which don't apply here since it's an offline join. I tried it without the /LOCALOS flag just to see what happens and it gave me:
/REQUESTODJ only operates on an offline (not running) Windows image
by default. The path supplied [C:\windows] is the current running Windows
installation. To override the default behavior and target the currently
running local operating system also specify /LOCALOS.
The parameter is incorrect.
Has anyone else encountered this and know why/how this happens and how to get past it? I didn't see any hints generated in Event Viewer; hoping to avoid a bunch of tickets down the line asking for domain joins once they've reached the office 😅
MAJOR facepalm here.
Just posting this so there's a reference for others, but this batch of laptops have Windows HOME installed on them, not Pro. Per this page with Home vs Pro features, Active Directory / Domain Joining is not supported on Windows Home. Either install Pro on the laptops or return them and purchase a batch with Pro on them.
I have a problem that i have a difficult time explaining, which makes any online search very hard. Here is my dilema.
I'm migrating a VM. The purpose of this machine is to compile send out daily/weekly/monthly reports. I know there are other ways (like Power BI) but this is the situation we are in right now. The older machine has win10 pro and office 365 installed while the new has win10 enterprise version and office 2016 installed. This machine runs 24/7 in the background running specific tasks (via system scheduler app) at given times, that is it's a Virtual machine and has done so without issues since it was created. The reason for the migration is because we need to domain change and bring the machine under a new corporate policy and we don't want to do this on a live server.
We've set it the VM's the same way, same programs and same settings. Everything seams to be running smooth expect for this one thing, and here is the problem i have a hard time to explain or figure out:
MS Access will update the tables and the computer will run the tasks as set but it will not export the data to pdf unless i have a remote desktop connection open. Will not export the pdf's otherwise. MS Access uses a autoexec macro where the pdf export is set with ExportWithFormatting. This works without issues on the old server.
We thought this to be a permission or user specific issue at first but even re-creating the tasks did not work and changing paths. Otherwise also i expect we would have problems with tables updating, specially since it works when you have an active remote desktop conn running.
I'm lost and therefore hoping this community will be able to help or guide me to a solution.
I believe that we found the reason for this. It was caused by windows easy print and the printer drivers of the machine. It worked for some reason differently between the servers. after reinstalling the printer drivers and a few restarts it started working. It exports now from access again.
This is at least solved.
I have installed SPSS statistics 22 on my Win7 Home 64-bit SP 1 and it will not run. I am on an HP Pavilion dv7 with tons of RAM and disk.
Authorized copy (not network) standalone install with the 20-character authentication key.
I've been with IBM's ECuRep support for SPSS and still the software will not run (not that they were really any help). I'm working on this problem for 3 weeks now.
The error on startup:
Attempt to connect to a remote server failed inet:Local Computer: 0
I have purchased the software twice from two separate vendors, neither have been any help. Looking for ANY advice that may help. This is the student Version 22 standard Grad Pack.
The only thing I can think of that might cause this is a misconfigured firewall. Although Statistics would be running entirely on the one machine, it may use communications between the frontend and backend processes that are being intercepted and blocked.
I had the same problem, and called IBM support. They said it could be because SPSS was not installed with admin rights, recommended to remove and delete files under program files then reinstall. That did not help.
Then a friend told me he had a similar problem but the 32 bit version worked for him, so I tried. It worked once then it died again.
Finally, I installed version 21 64 bit. That worked.
I have created an account at Microsoft Windows Dev Center - Hardware and signed the Windows Error Reporting Agreement.
Then, I have introduced an null-pointer dereference to release signed driver that I used on my test computer and sent the BSoD report to Microsoft.
I have used the Microsoft Ecosystem Metadata Exchange to map my driver name and created the product groups.
From what I have read on the internet these should be all the requirements to get the report to display in the dashboard. The report was supposedly updated twice since the mapping took place.
I have mailed the wer as well and got "In general it will take 5 days." and later, when I explained that already two weeks have passed I got "Sorry for that let me work with WER team." and I haven't heard anything since then.
Is there some extra requirement I have missed?
Apparently looks like that's all one have to do in order to receive the report.
Today my dashboard was updated with some real error that had 4 hits (reported from 4 different machines).
I have not received the report for null-pointer dereference. I guess the problem has happen on more than one machine to actually show up.
The LAN which has about a half dozen windows xp professional pcs and one windows 7 professional pc.
A jet/access '97 database file is acting as the database.
The method of acccess is via dao (DAO350.dll) and the front end app is written in vb6.
When an instance is created it immediately opens a global database object which it keeps open for the duration of its lifetime.
The windows 7 machine was acting as the fileserver for the last few months without any glitches.
Within the last week what's happened is that instances of the app will work for a while (say 30 mins) on the xp machines and then will fail on database operations, reporting connection errors (eg disk or network error or unable to find such and such a table.
Instances on the windows 7 machine work normally.
Moving the database file to one of the xp machines has the effect that the app works fine on ALL the xp machines but the error occurs on the windows 7 machine instead.
Just before the problem became apparent a newer version of the app was installed.
Uninstalling and installing the previous version did not solve the problem.
No other network changes that I know of were made although I am not entirely sure about this as the hardware guy did apparently visit about the same time the problems arose, perhaps even to do something concerning online backing up of data. (There is data storage on more than one computer) Apparently he did not go near the win 7 machine.
Finally I know not very much about networks so please forgive me if the information I provide here is superfluous or deficient.
I have tried turning off antivirus on the win 7 machine, restarting etc but nothing seems to work.
It is planned to move our database from jet to sql server express in the future.
I need some suggestions as to the possible causes of this so that I can investigate it further. Any suggestions would be gretly appreciated
UPDATE 08/02/2011
The issue has been resolved by the hardware guy who visited the client today. The problem was that on this particular LAN the IP addresses were allocated dynamically except for the Win 7 machine which had a static IP address.
The static address happened to lie within the range from which the dynamic addresses were being selected. This wasn't a problem until last week when a dynamic address was generated that matched the static one and gave rise to the problems I described above.
Thanks to everyone for their input and thanks for not closing the question.
Having smart knowledgeable people to call on is a great help when you're under pressure from an unhappy customer and the gaps in your own knowledge mean that you can't confidently state that your software is definitely not to blame.
I'd try:
Validate that same DAO and ODBC-drivers is used on both xp- and vista machines.
Is LAN single broadcast domain? If not, rewire. (If routers required make
sure WINS is working)
Upgrade to ms-sql. It could be just a day of well worth work, ;-)
regards,
//t